| ID | Description |
|---|---|
WFM-69435 | Fixed an issue that could occur after an employee submitted a time away from work request with a comment. In some cases, if the comment contained an invalid character, the request got temporarily stuck in the Pending state and their manager couldn’t approve the request. |
WFM-72776 | Fixed an issue that could occur in the Assign Pay Adjustment Rule in Pay Setup > Pay Policy. In some cases, the value entered in the Bank minutes multiplier field wasn't applied correctly if an employee's pay group was changed in an open pay period with an offset. |
WFM-73005 | Fixed an issue that could occur in Profile, in the Balances section of the Personal tab. In some cases, Dayforce failed to show data in the Expiring Transactions tab. |
WFM-74063 | Fixed an issue that could occur in Timesheets when using the Tracer functionality. In some cases, Dayforce showed the final output of applied pay rules without a detailed breakdown of changes. This issue could occur if the pay group didn’t have a start of the week set. Now, if a pay group doesn’t have a start of the week set, Dayforce falls back to the start of the week set for location, and then Site Setup, as expected. |
WFM-74194 WFM-75294 | Fixed an issue where, in rare cases, an overtime premium didn't get processed to payroll in a regular pay cycle or as a retro payment. |
WFM-74406 | Fixed an issue in Plan that could occur when you generated a forecast log. In some cases, the CSV file didn’t show data in the Last Year Reference Day column. |
WFM-74411 | Fixed an issue that could occur in Scheduling Plan > Shift Setup in the Shift Rotation tab when you added a new shift rotation. In some cases, the application didn’t let you change the default date that was populated in the Effective From field. |
WFM-74756 | Fixed an issue that could occur with multi-segment schedules that were set up to be auto-paid. In some cases, only a portion of the schedule was paid in Timesheet. |
WFM-75233 WFM-78457 | Fixed an issue that could occur in the Shift Premium Calendar Rule when the following options were selected:
In rare cases, incorrect premium hours were assigned to a non-worked premium that crossed two workdays. For example, this could be a non-worked shift that started on a day that’s ineligible for premiums and ended on a day that was considered eligible for the premium calculation. The incorrect hours for this shift were allocated to the portion of the premium that fell before the day divide. |
WFM-75958 | Fixed an issue where, in some cases, the pay details in Timesheet didn't match the schedule costs shown in Schedules for a time away from work entry. |
WFM-77328 | Fixed an issue that could occur with the Award Entitlements to Employees background job. In some cases, when the job was run for terminated employees, it failed with an error. |
WFM-77742 | Fixed an issue that could after the Raw Punch Import failed. In some cases, if you fixed the issue that caused the import to fail and tried to run it again for the same date, the application unexpectedly rejected the import again. |