Timekeeping
Timekeeping release notes pertain to timekeeping and costing features.
| Version | Type | Description | ID |
|---|---|---|---|
| 19.0.2.0 | CORR | Critical: The error that occurred when all the Pay codes were selected in the Context dialog box in the Timekeeping screen has been fixed. | OPS-19177 |
| 19.0.3.0 | ENH | Critical: Two new options, Each Regular Work Day Except Holidays and Each Regular Day Off Except Holidays have been added to the Time Frame drop-down list in the OPS Timekeeping Alert Rules screen. These options consider regular work and off days that are not holidays. | OPS-19745 |
| 19.0.3.0 | ENH | Improved the appearance of the Re-cost Employee dialog box in the Weekly Timekeeping Summary screen. | OPS-20016 |
| 19.0.3.0 | ENH | Critical: A menu option, Re-cost Employee has been added to the Weekly Timekeeping Summary and Weekly Timekeeping Activity Summary screens. If clicked, users can choose to generate costing for the Entire Pay Period or Selected Dates. | OPS-20017 |
| 19.0.3.0 | ENH | Improved the loading of data in the Prior Pay Adjustments screen. | OPS-20141 |
| 19.0.6.0 | CORR | Blocker: The issue of the Accrual rule being costed based on the year when the rule was processed rather than on the accrual year of the vacation that is being advanced has been fixed. | OPS-21172 |
| 19.0.6.0 | CORR | The issue of the Weekly Pay Rule not being applied properly when an employee works in two different divisions during the week has been fixed. The system now calculates weekly costs for all active employees regardless of division changes. | OPS-21069 |
| 19.0.6.0 | ENH | The context property, has been added to address the setting of the Employee Day Type for February 29 during non-leap years. The property provides the options: Day Before and Day After (default). If applied to a Birthday Holiday on a non-leap year, and Day Before is selected, the date is February 28, and when Day After is selected, the date is March 1. | OPS-21009 This task is related to OPS-19309. |
| 19.0.7.0 | CORR | The issue of the selected field or drop-down list showing the values of the last selected record instead of those of the newly selected rule in the Pay Rules screen has been fixed. | OPS-19595 |
| 19.0.7.0 | CORR | The SQL query on Work Status Group now includes a reference to the TkPay Rule. | OPS-21574 |
| 19.0.7.0 | CORR | Critical: An issue where Max time was not considered while calculating timekeeping has been fixed. | OPS-21786 |
| 19.0.7.0 | ENH | When applying Extra Pay rules to filter the work to be paid, the system now also checks the PassRunType Group. The UpdatePayRuleRuncategoryGroup upgrade utility must be run to apply this change. | OPS-21055 |
| 19.0.9.0 | CORR | Blocker: A new property, , was added. If selected, PassWork will not always cost first and work order can be configurable. Default setting is false. | OPS-22347 |
| 19.0.10.1 | ENH | A new Timekeeping pay rule calculation mode (Calc Mode) was added: Published Costed Value. The sum of the published work costed value is paid towards the pay code defined in the pay rule. If an absence rules uses the PCV Calc Mode, then a Compose Pay Code Group must also be defined for the pay rule. | OPS-22629 |
| 19.0.11.0 | CORR | An occasional issue in the Timekeeping screen where new records could not be manually added or updated has been fixed. | OPS-22990 |
| 19.0.11.0 | CORR | An issue in the Timekeeping screens where the FLSA button was not consistently available for non-Admin users has been fixed. | OPS-23137 |
| 19.0.16.0 | CORR | An issue in Timekeeping where, when using a period of Week Period, the Piece Overtime rule did not apply the correct FromTime and ToTime has been fixed. | OPS-24460 |
| 19.0.17.0 | CORR | Critical: An issue where the Timekeeping Freeze button disappeared after it was used and the screen was refreshed/reopened from the Weekly Timekeeping Summary screen has been fixed. (Workaround was to log out and then log in to the Client Shell.) | OPS-24780 |
| 19.0.18.0 | CORR | An issue where LaborAcct information was shown incorrectly for some accounts because the carriage return character was included in the description field has been fixed. Now, carriage return characters are replaced with a space and LaborAcct information appears on one line. | OPS-25263 |
19.0.20.0 |
CORR | An issue in the Prior Pay Adjustments screen where rowset assert errors occurred and prevented content from being shown has been fixed. | OPS-25645 |
19.0.20.0 |
CORR | An issue in the Prior Pay Adjustments screen where an SqlCommand::ExecDirect Failed error appeared due to an issue with Labor Cost Allocations has been fixed. | OPS-25789 |
19.0.20.0 |
CORR | An issue where recosting historical days resulted in a rowset error about the RunCategoryId field has been fixed. | OPS-25779 |
19.0.23.0 |
CORR | Critical: An issue on the Timekeeping screen where Absence options weren't listed as expected for pay codes and payroll codes with a required absence type was fixed. | OPS-27467 |
19.0.23.0 |
CORR | Fixed an issue where accrual generation would fail when a manual balance already exists. | OPS-26856 |
19.0.23.0 |
CORR | Fixed a Line Costing calculation error resulting in duplicate or overlapping report times. | OPS-27562 |
| 19.0.23.0 | CORR |
Fixed an issue where the line costing start time was incorrect for mid-trip relief starts. Improved the user interface of the line costing window by adding agency name, sign up period name, and run validity dates. |
OPS-27366 |
| 19.0.23.0 | ENH | A new property was added: OPSTimekeepingPiece Intervening Ignore MaxPieceTime. If selected, MaxPieceTime is ignored when processing Piece Intervening Rules. | OPS-27704 |
19.0.23.0 |
CORR | Fixed an issue that would cause the system to throw an error when viewing accrual records on the Weekly Timekeeping Summary screen. | OPS-27909 |
| 19.0.23.0 | CORR | An issue where line costing did not calculate as expected was fixed. | OPS-27351 |
19.0.24.0 |
ENH | For clarity, updated the description of the property to: "If selected, upon generating accruals for a calendar year, the system does not retain accrual balance records for the previous year." | OPS-26855 |
19.0.25.0 |
CORR | An issue in the Timekeeping screen where it was not obvious that the Shift field was mandatory was fixed. When the property is selected and no Shift is defined, an error message now appears. | OPS-25593 |
19.0.24.0 |
ENH | An issue where Timekeeping did not consider overtime pay codes when costing absences was fixed. | OPS-28576 |
19.0.25.0 |
CORR | Blocker: Validation was added to address an issue where an Exception error appeared when saving a pay record. If the property is cleared, Shift now has a default value of 0. | OPS-28965 |
19.0.25.0 |
CORR | Critical: An issue where shifts were applied to pay codes where the Apply Shift option was cleared was fixed. | OPS-28877 |