Unable to Configure HCM Workflow Approvals Based on Job Conditions Without Hardcoding

Summary:

We are working on a requirement in Oracle HCM Cloud where workflow approvals need to be triggered based on specific job codes. The scenario is as follows:

When a Line Manager initiates an HCM transaction (e.g., Position Change) for employees holding certain job codes (e.g., Job1, Job3, Job5, Job6), the approval should be routed to a specific application role.

To ensure maintainability, we do not want to hardcode job names or codes in the approval configuration.

We are exploring options to dynamically manage this, possibly through:

Value sets

Extensible flexfields (EFFs)

Other configurable methods that can allow for scalable and maintainable logic in the approval rules.