Associated jobs

Associated jobs are roles linked together and treated as equivalent for scheduling. You can assign one or more associate jobs to a job to streamline shift management. This feature is useful when job titles imported from the HR system do not directly align with the functional positions used in scheduling.

See Adding an associated job.

Associated jobs follow a parent-child structure. A parent job links to one or more child jobs. If an employee qualifies for either the parent job or any of its child jobs, you can assign them to shifts for any of those roles.

When you assign an employee to an unassigned shift, the shift job is updated to match the employee’s qualification, provided the employee qualifies for the current job or any associated job. If the employee is unqualified, the shift remains unassigned and retains its original job value, unless the employee’s qualification triggers an update.

Each associated job includes a rank that determines its priority during replacement. The job with the lowest rank number is selected when an employee qualifies for multiple associated jobs. For example, if Junior Clerk (rank 2) and Senior Clerk (rank 1) are associated with Clerk, and the employee qualifies for both, the shift is updated to Senior Clerk. However, you can modify this behavior using the configuration key UPDATE_TO_ASSOCIATED_PREFERRED_JOB_WHEN_ASSIGN, which determines whether an employee's preferred job or their top-ranked associated job is used when assigning them to an unassigned shift with a parent job.

See the Infor Workforce Management User and Administration Library (Multi-tenant) and select Administrator > Scheduling configuration keys.

To ensure data integrity and prevent scheduling issues, these validation rules are applied when you save associated jobs:
  • A Child Job cannot be added if it is already defined as a Parent Job.

    This prevents multi-level hierarchies where a job has its own associated jobs and is also linked as a child elsewhere.

  • A Parent Job cannot be used if it is already defined as a Child Job under another parent.

    This avoids circular references and ensures each job maintains a clear role in the hierarchy.

  • A Child Job cannot be linked to more than one Parent Job.

    This prevents redundant associations and ensures that each child job belongs to only one parent.

If any of these conditions are not met, an error message is displayed. These validations help prevent misaligned shifts, incorrect coverage, and display errors in the MVS screens.

Note: After configuring associated jobs, you must unload the application cache to ensure that validations and filters reflect the updated job associations.