Floating employees to another shift

By floating shifts, you can move employees from one shift to another. You can move employees from a unit with surplus staff coverage to a unit with staffing needs.

Employees can be assigned to float to any team regardless of their security for that team. This feature is available in Central Staffing and Advanced Schedule View.

To enable this option, you must set the SKIP_EMPLOYEE_TEAM_VALIDATION registry parameter to True and update the Field Parameters in Field UI Configuration. When this option is enabled, you can successfully float to teams you do not have access to, without encountering any validation errors. If SKIP_EMPLOYEE_TEAM_VALIDATION is set to False, the float will fail and these messages are displayed:
  • For single float: User has invalid team permission on shift(s): Day(MM/DD/YYYY)
  • For mass float: User has invalid team permission on shift(s): Day(MM/DD/YYYY), 7D8(MM/DD/YYYY)

See the information about SKIP_EMPLOYEE_TEAM_VALIDATION in the Infor Workforce Management Registry Parameter Reference Guide.

During the floating process, the shift job gets updated based on the Associated Job and the employee’s qualifications, similar to assigning an employee to an unassigned shift.

See the information about Associated Jobs in the Infor Workforce Management MVS Implementation and Administration Guide.

In ASV, when an employee is floated to a new shift, the shift job displayed in the Float Wizard determines the job of the newly created shift. Employees are floated to these new shifts without any qualification soft stop.

When floating an employee to an existing unassigned shift, the behavior is determined by the FLOAT_USE_ASSOCIATED_JOBS registry parameter. By default, this parameter is set to false for upgrading customers and true for new customers.
  • If the parameter is set to True, the associated jobs are considered during the floating process, and the shift job updates based on the employee's qualifications and job hierarchy.
  • If the parameter is set to False, the shift job remains unchanged, regardless of the employee's qualifications.

For example, if Bob is qualified for Job C and is floated to a shift originally associated with Job A, B, or C, the shift job is updated to Job C when the parameter is set to true. If the parameter is set to false, the shift job remains as Job A, B, or C. Additionally, when job hierarchy is a factor, such as when Job B is ranked higher than Job C, and an employee is qualified for multiple jobs like Job B and Job C, the shift is updated to the higher-ranked job (Job B) if the parameter is true. The job ranking is considered only when an employee holds multiple qualifications.

No qualification soft stops occur during the floating process. The Float To row in the confirmation model displays the updated job for each scenario. The employee's preferred job is also shown in this row when they are floated to another unit's shift.

For partial floats, only the assigned portion of the shift updates to the new job, and any remaining unassigned portion retains its original job.

Finally, when relief shifts are created following a floating process, they inherit the job of the original floated-from shift.