Improved the error message shown when a delegated user doesn’t have the appropriate org rights to create a work assignment. | ||||||||||
Fixed an issue with Data Mapping 2.0 where using the following mapping objects in data mapping rules didn’t update employee records as expected:
Previously, Dayforce applied data mapping for these fields based on what the current data qualified for. Now, Dayforce applies data mapping for these fields based on what the latest data qualifies for. Example: Holiday Group 1 and Holiday Group 2 Consider the following two data mapping rules:
If a user submits a form or imports data such that an employee’s current status has Holiday Group 1 and their future status has Holiday Group 2, this is how Dayforce behaves:
Example: Pre-Start Status to Active Status A manager submits the New Hire form for an employee who currently has a Pre-Start employment status. The New Hire form will make them Active on a date in the future. This triggers a data mapping rule with the following values:
After the form and mapping rule run, the employee has the following saved to their employee record:
| ||||||||||
In Org Setup > Jobs and Job Assignments, in new jobs, updated the Union drop-down list so that it now shows only active unions, as expected. | ||||||||||
Improved the performance of Data Mapping 2.0 so that now, it takes less time to run. | ||||||||||