Article Links
Timeline
When will this be released?
Release Date: 05/29/2025 from 05:30 pm PST.
Is there downtime for this release?
No.
Functional Bugs Resolved
| Scenario When Issue Encountered | Issue Resolved |
|---|---|
| The amount override was set, which prevented the calculation from being applied to all element-related PC Calculation Methods. This was the cause of SF 01112300 for CFPUA. | We stopped populating the amount overrides in this scenario. This ensures that the value from the calculation would be honored. |
| When payroll batches were being reset, the related leave lines weren’t going back to their original state. When attempting to reprocess payroll, those transactions weren't picked up. This was the cause of the leave line issue for Palos Verdes Library District. | With this change, we are now correctly updating the leave lines to their original state. When payroll gets reprocessed, those leave lines are now pulled into payroll. |
| When Payroll is closed and auto processes are run to close pay, UPDTB runs with the Trial value of NULL. This causes additional ACH files to be created when it shouldn’t. This was the cause of SF Case 01116005 for City of Athens. | We have modified the default Trial value and set it to No. |
| When entering deductions or earnings for an employee, if you entered a start or end date using a two-digit year (like 01/01/25), the system would incorrectly set the year to 0001 instead of 2025. As a result, the deduction or earning would appear as "Inactive," and you wouldn’t see it on the page. Because the date was so far in the past, it also wouldn’t generate any entries in the audit log, leading to further confusion. | We have updated these screens to show an error message, indicating that the entered date is invalid. |
| The Colorado Quarterly File was inaccurate. This caused manual work arounds for filing them for Q1. This issue impacted Durango. | We’ve updated the Colorado Quarterly File. “S” record modified in the following ways:
“A” record modified in the following ways:
|
| Payroll batches were loading very slowly because they were trying to load the profile picture of the employee into each pay header. This Issue was identified by City of West Fargo and City of Victoria. | Modified the page to only load the thumb nail of the person’s profile picture. If the thumbnail was not available, or the picture was taking too long to load after a certain period of time, it would only show the employee’s initials. The performance on the page will be significantly better. |