Timekeeping

Release notes for timekeeping and costing features.

Version Type Description ID
21.1.0.0 CORR Vacation and holiday pay can now be combined when holidays occur in a future vacation period. A new Field, Holiday Advance Pay, was added in the Pay Rules ancillary data screen. This allows agencies to pay for holidays before they occur (but only if they occur in a future vacation pay period).

Related tasks: OPS-24390, OPS-24900

 OPS-24390
21.1.0.0 CORR An issue where multiple prior pay entries were created for absence changes and some values were added together has been fixed. OPS-24245
21.1.0.0 CORR An issue where square brackets were no longer respected in some calculation formulas has been fixed. OPS-24439
21.1.0.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
21.1.0.0 ENH A new property was added: OPS > Timekeeping > Piece Intervening Ignore Absence. If selected, Absences are ignored when processing Piece Intervening Rules. The property is cleared by default. OPS-24493
21.1.0.0 ENH A new property was added OPS > Timekeeping > Cost Order Settings > Absences Consider in Work Order - Tiebreaker. This changes the work absence cost order.
  • Absence first. The absence pay is not reduced by overlapping work hours. This is the default setting.
  • Work first. The absence pay is reduced by the overlapping work hours. Note that hours are not reduced by partial bid work performed after the absence/overlapping work.

There is an upgrade utility for this property.

 OPS-24661
21.1.0.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
21.1.0.0 ENH Critical: Piece only was added as an option in Pay Rules. When selected, the piece rule is invoked for each piece of work, even when the work is multi-pieces of completed work. OPS-23989
21.1.0.0 ENH Vacation and holiday pay can now be combined when holidays occur in a future vacation period. A new Field, Holiday Advance Pay, was added in the Pay Rules ancillary data screen. This allows agencies to pay for holidays before they occur (but only if they occur in a future vacation pay period).

Related tasks: OPS-24390, OPS-24900

 OPS-24900
21.1.0.0 ENH Two new fields were added to the OPS Timekeeping Alert Rules screen:
  • From Day defines the number of previous work days from the current date to check against the alert rule.
  • To Date defines the number of future work days from the current date to check against the alert rule. Note that all timekeeping alert rules check the current date.

    From Date and To Date allow additional dates to be checked.

 OPS-21534
21.2.0.0 CORR Costing logic was updated. The Load Supply field now uses UserLong1 from TKWork instead of UserLong1 from TKExtraWork. OPS-25129
21.2.0.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
21.2.0.0 ENH A new property was added: OPS > Timekeeping > Weekly Timekeeping Summary > Show Bid Unit Match Any Day Of Pay Week.

If selected, pay week information is shown for employees with a matching bid unit on any day in the pay summary period.

If cleared, pay information is shown for employees whose bid unit matches on the Start Date defined in the screen Context.

This property is used for the Weekly Timekeeping Summary and Weekly Timekeeping Activity Summary screens.

 OPS-24973
21.3.1.0 ENH OPS now supports costing by zone segment.

When setting up PayRules, the following fields must be defined: Calculate Mode: CustomCostingxxx, Custom: Custom Load (should be defined as Pay), and Overtime: Compose Pay Code Group (as defined in the Pay Accessory Groups screen; the system uses the paycode work, piece, shift).

See your Trapeze representative for more information.

 OPS-25308
21.2.0.0 ENH The OPS > Timekeeping > Cost by Line property was updated to OPS > Timekeeping > Cost by Segment. If selected, FX run platform time is costed by segment type (No, Line, or Zone).
New properties were added:
  • OPS > Work > Fixed Route > Zone Field in Nodes Table. If selected, the Zone field is defined in Nodes table.
  • OPS > Work > Fixed Route > Remove Trips And Blocks Zone Segment After Import. If selected, in order to reduce data storage, system will remove trips and blocks zone segment after import.
An OPS Zone Pay Mapping screen was added. Fields on this screen are Zone Id, Pay Code, and Zone Pay Code.

New tables were added to the database: OPSZonePayMapping, OPSZones, OPSZoneSegment.

 OPS-25176
21.3.1.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
21.3.1.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
21.4.1.0 CORR An issue in Timekeeping where a column ambiguously defined error message appeared when using the Prior Pay Adjustment screen was fixed. OPS-25789
21.4.1.0 CORR An issue in Timekeeping where From Time and To Time weren't updated as expected when the Piece Absence rule pay time was reduced by overtime has been fixed. OPS-25814
21.4.1.0 CORR An issue in Timekeeping where the generic Piece Absence rule using the calculation mode ACT didn't always stamp the From Time and To Time in the Weekly Timekeeping Summary screen was fixed. OPS-25801
21.4.1.0 CORR An issue where piece overtime pay had an incorrect FromTime/ToTime was fixed. OPS-25990
21.5.0.0 CORR An issue where OPS Timekeeping Alert Rules were not recognizing inherited bid units when the OPS/Timekeeping/Inherit Bid Unit/Vacation Relief property was selected was fixed. OPS-26125
21.8.0.0 CORR Fixed an issue where, when the OPS > Timekeeping > Freezing > Skip Calculate Timekeeping for Frozen Employee Dates was enabled, attempting to re-cost or calculate timekeeping for employees with frozen timekeeping records resulted in an error. OPS-26698
21.8.0.0 CORR Fixed an issue that caused extra pay for PASS runs to not be calculated correctly. OPS-26764
21.9.0.0 ENH The Comments field in the Pay Rules screen (Admin) now allows 4000 characters, up from 254. OPS-26760
21.9.0.0 ENH Piece Absence and Piece Overtime Absence pay rules now support Loop Level 1. If set to 1, these pay rules do not trigger. OPS-26787
21.10.0.0 ENH Fixed an issue where the Audit timestamp for a rule in OPS Timekeeping Alert Rules would not update as expected after creating, editing, or deleting a formula under that rule. OPS-26965
21.10.0.0 CORR Fixed an issue where attempting to view timekeeping for an operator with an FMLA (Family Medical Leave Act) absence by selecting Show Timekeeping > Selected Dates would result in an error: ("Rowset: Invalid column 'AbsenceTypeId'…"). OPS-27062
21.10.0.0 CORR Fixed an issue with costing an absence pay rule when shifts are enabled in Timekeeping that would result in an error: ("Rowset: Invalid column 'Shift'..."). OPS-27105
21.11.0.0 CORR Fixed an issue that would cause an error when extra pay was assigned to an employee in the paratransit division and that employee was costed in the Weekly Timekeeping Summary screen. OPS-27196
21.11.0.0 CORR Fixed an issue where costing overtime in Timekeeping would result in inconsistent deductions when multiple entries had the same From Time or Pay Time. OPS-27211
21.15.0.0 CORR Fixed an issue where accrual generation would fail when a manual balance already exists. OPS-26856
21.16.0.0 CORR Fixed an issue affecting the generation of accrual balances for different types of time. The issue was caused by the OPS > Accruals > Single Accrual Balance Record property, which was enabled by default and did not retain the previous year’s accrual balances when generating accruals for a new calendar year. This property’s description has been updated to clarify its functionality and it is recommended to disable it unless required. OPS-26855
21.16.0.0 CORR

Fixed a bug where absence accrual usage was showing an invalid amount when there was not a single day off record spanning the entire period

Corrected the calculation of designated usage by ignoring the default days off when true day off records exist.

 OPS-27814
21.16.0.0 CORR

Fixed an issue where the FLSA process would fail due to a primary key violation when processing pay records for certain employees and dates.

Updated the NextId function to avoid conflicts with existing pay IDs.

 OPS-27884
21.16.0.0 CORR Fixed a null date error when selecting accruals to show on the Weekly Timekeeping Summary screen. OPS-27909
21.16.0.0 CORR Fixed an issue in Timekeeping where the custom shift costing was adding a shift to a meal paycode when it was not supposed to, resulting in incorrect timekeeping calculations. OPS-28097
21.16.0.0 CORR Fixed an issue in Timekeeping where the custom shift costing was incorrectly applying a shift to a meal paycode that did not require it. The issue was affecting some operators who had a different number of hours than expected. OPS-28122
21.18.0.0 CORR Fixed a bug that caused some employees to receive wrong timekeeping alerts in OPS. OPS-28366
21.19.0.0 CORR

Fixed an issue with Piece Overtime absence rules that could cause it to incorrectly deduct the wrong paycode.

Improved the logic for reducing the paycode that contributes to overtime for the same absence type.

 OPS-28576
21.19.0.0 CORR Fixed several issues related to the Cost Allocation dialog in OPS, including rowset errors, attribute column updates, date range validation, and unwanted record creation. OPS-28623
21.20.0.0 CORR Critical: An issue where when setting the property OPS > Shift > Work Shift Method to Actual Time the pay code was not divided into the proper shift band was fixed. OPS-28800
21.21.0.0 CORR Critical: An issue where shifts were applied to pay codes where the Apply Shift option was cleared was fixed. OPS-28877
21.21.0.0 CORR An issue in the Timekeeping screen where it was not obvious that the Shift field was mandatory was fixed. When the OPS > Shift > Apply Shift Processing property is selected and no Shift is defined, an error message now appears. OPS-25593
21.21.0.0 CORR An issue where a shift expansion occurred even when Pay Codes did not have Apply Shift enabled was fixed.

The OPS > Timekeeping > Populate Pay Time Fields without enable apply shift property was updated to OPS > Timekeeping > Populate Pay Time Fields Without Applying Shift Processing. If selected, the system populates the Timekeeping Pay From Time and To Time fields when the associated Pay Code definition has Apply Shift cleared and the OPS > Shift > Apply Shift Processing property is cleared.

The description of the OPS > Shift > Apply Shift Processing property was updated to “If selected, shifts apply in Timekeeping. Timekeeping Pay From Time and To Time fields will be populated when the associated Pay Code definition has Apply Shift selected. To populate the Timekeeping Pay From Time and To Time fields without using shifts, see the OPS/Timekeeping/Populate Pay Time Fields Without Applying Shift Processing property.”

 OPS-28661
21.21.0.0 CORR Blocker: Validation was added to address an issue where an Exception error appeared when saving a pay record. If the OPS > Shift > Apply Shift Processing property is cleared, Shift now has a default value of 0. OPS-28965
21.22.0.0 ENH In PayRules, the Include Activity Group and Exclude Activity Group fields can now be used to define activities that are eligible and ineligible for Premium pay when using the Rule Class: Premium (for example, if lunch is ineligible for premium pay).

Activity groups are defined in Pay Accessory Groups. When creating Work Subtypes to use these activity groups, the Activity Flag must be selected.

OPS-28869
21.22.0.0 ENH In Pay Rules, two new fields were added:
  • AbsenceDayStatus. Options are Always, Any absence, No absence, Single absence, Multiabsence.
  • DailyAbsencePiece. Options are F (First), M (Middle), and L (Last).

These fields can be used to distinguish whether absences are the first, middle, or last absence of the day and cost them accordingly.

 OPS-28991
21.22.0.0 CORR Blocker: An issue where using the OPS > Shift > Apply Shift Processing property resulted in unexpected Timekeeping results was fixed. OPS-29004
21.22.0.0 CORR Critical: In Pay codes, the Apply Over Time Reduce value of Apply and Keep original Pay now only calculates overtime and does not apply a reduction. OPS-28844
21.24.0.0 ENH In OPS Timekeeping Alert Rules, the Time Frame: Last Day in the Pay Week option was updated from a weekly type to a daily type. OPS-29346
21.24.0.0 CORR An issue where a rowset error appeared when trying to set up a new labor account when no existing labor accounts existed was fixed. Now, an error messages advises users to set up Labor Acct Config ancillary data. OPS-11400
21.25.0.0 CORR Critical: An issue in the Weekly Timekeeping screen where recosting employees resulted in an incorrect clawback amount for premium work was fixed. OPS-29530
21.26.0.0 ENH Critical: In the Calculate Timekeeping screen, an error message now appears if the define From Date and To Date span a period of more than four weeks (two pay periods). OPS-29718
21.26.0.0 CORR An issue in Calculate Timekeeping where Divisions names were truncated was fixed. OPS-29730
21.28.0.0 CORR An issue in Timekeeping when the OPS > Dispatch > Activate Day > Vacation Relief inherit original employee division When Activate Day property was selected, where recosting a vacation relief employee's pay period resulted in warnings in the OPS Process Log and their pay not being regenerated was fixed. OPS-30028
21.29.0.0 CORR An issue where selecting the OPS > Timekeeping > Freezing > Manual Adjustments Trigger Freezing property did not prevent users from updating pay records was fixed.

Now, the system does not save records if they are updated concurrently by a second user and a message tells the second user to refresh the data before making changes.

 OPS-30079
21.29.0.0 ENH On the Accrual Balance screen, when adding a new record the Accrual Type field now defaults to the accrual type set in the Context (F3). The field value can be updated as needed. OPS-29917
21.29.0.0 ENH Logging for cost allocations in Timekeeping was improved to address an issue where the timekeeping process failed unexpectedly. To see new logging, the OPS > Costing Allocation > Calculate property must be selected. Logging can be viewed in the OPS Process Log. OPS-30166
21.30.0.0 CORR Critical: An issue with OPS Timekeeping Alert Rules where the Time Frame: All Days in the Pay Week was based on the OPS > General > First Operational Day Of Week property and therefore not showing alerts when expected was fixed. Now, All Days in Pay Week uses the OPS > Timekeeping > Weekly Processing Date or OPS > Timekeeping > Bi-Weekly Processing Date property, as appropriate. OPS-30321
21.31.0.0 CORR Critical: An issue in the OPS Shift Definition screen where Shift could be defined as 0 was fixed. All shift values must now be greater than 0. OPS-30438
21.31.0.0 CORR Blocker: An issue in Timekeeping Cost Allocation where labor accounts were not retrieved from extra work subtypes as expected was fixed. OPS-30485
21.32.0.0 CORR An issue in where navigating away from the Timekeeping screen and then back to it resulted in Local Settings (Time Span Format and Time Format) not being retained, was fixed. OPS-30528
21.32.0.0 CORR Blocker: An issue where some holiday bid runs were not recognized in the Employee Profile screen or when costing was fixed. OPS-30538
21.34.0.0 CORR An issue in the Calculate Timekeeping screen where the dates did not show the last date used when timekeeping was calculated was fixed. OPS-30865
21.36.0.0 CORR Critical: An issue where Timekeeping had inconsistent absence alert behavior based on day-by-day vs. multiple-day costing was fixed. Now, OPS checks the employee bid unit for the entire week even when costing for individual days and shows timekeeping alerts as expected. OPS-30931
21.36.0.0 CORR Critical: An issue in the Weekly Timekeeping screen where recalculating timekeeping where the system hung while displaying the Re-cost Employee dialog was fixed. OPS-31031
21.36.0.0 CORR An issue in the Weekly Timekeeping screen where an assert error occurred when attempting to recost was fixed. OPS-30991
21.36.0.0 CORR Critical: An issue where the Timekeeping screen could not be opened if individual pay codes were selected in the Context (F3) was fixed. OPS-31028
21.38.0.0 CORR Critical: An issue in Timekeeping where completed work was costed as not completed was fixed. OPS-31186
21.39.0.0 ENH The system was updated so that OPS > Timekeeping > Cost by Segment > Consider Meal Break and OPS > Timekeeping > Cost by Segment > Consider Meal Break Max Time are only used if OPS > Work > Work Sources > Fixed Route is defined as BlockBuster Runs. OPS-31155
21.40.0.0 CORR An issue in Timekeeping where regular and overtime pay was missing for line premium costing was fixed. This fix automatically defines the OPS > Timekeeping > Populate Pay Time Fields Without Applying Shift Processing as selected. This may affect how transit agencies who DO NOT use shift processing see pay being calculated.

From Time and To Time values are now automatically populated. If your agency has not previously used these fields, you may now see two or more pay records to calculate pay instead of a single pay record.

If you are concerned about how this change may affect you, contact Customer Care.

 OPS-31378
21.40.0.0 CORR Blocker: An issue in Timekeeping where Pay Rules with a CalcMode of Bid Run Value were not finding work time on Holidays was fixed.

Only transit agencies who use Bid Run Value calculation mode for Holiday Work Pay Rules or Holiday Absence Pay Rules were affected. Employees who are entitled to Bid Run Value may not have received the bid run pay (i.e., the guarantee make up) for the holiday day.

 OPS-31537
21.41.0.0 CORR Blocker: Code for OPS-31031 was reverted to resolve an issue where holiday pay was not calculated as expected.

This issue affected v21.36–v21.40.

 OPS-31537
21.42.0.0 ENH The Pay Grid screen was updated. Job Class filtering now shows only the divisions available to the user based on their granted security permissions. OPS-31605
21.42.0.0 CORR An issue where the Calculate Timekeeping screen sometimes froze when calculating holidays was fixed. OPS-31658
21.44.0.0 CORR Critical: An issue where creating extra pay records for employees resulted in incorrectly updated sign off times and incorrect premium pay amounts was fixed. OPS-31859
21.47.0.0 ENH Critical: The Prior Pay Log was optimized to reduce unnecessary processing. OPS-32278
21.48.0.0 CORR An issue where the Calculate Timekeeping screen did not correctly load absence data when an employee had three or more consecutive days off between a holiday and an absence was fixed. When Disqualification Rules with Skip Off Days were in use, the system assumed a maximum of two days off, causing holiday pay not to be disqualified as expected. Now, the OPS > Timekeeping > Disqualification Rules Skip Off Days Maximum property controls the range of days checked and is agency-dependent, with a default of three days. OPS-32262
21.49.0.0 ENH System behavior was updated.

Now, the OPS > Dispatch > Day Locking > Ignore Dispatch Lock security permission key only applies to locked dispatch days.

The OPS > Dispatch > Dispatch Lock > Method property determines allowed operations (day activation, Daily Activity modifications, timekeeping calculation, and timekeeping modifications):
  • None allows all operations.
  • Before Timekeeping prevents day activation and Daily Activity modifications on locked days (unless Ignore Dispatch Lock is granted) but permits timekeeping operations.
  • After Timekeeping prevents all operations on locked days unless Ignore Dispatch Lock is granted, in which case Daily Activity modifications and timekeeping modifications are allowed.
 OPS-30024
21.49.0.0 CORR An issue where concurrent recost operations could generate doubled pay was fixed. OPS now detects conflicts between overlapping cost and recost operations and prevents them from running simultaneously. OPS-32295
21.49.0.0 CORR An issue where an error appeared when opening the Calculate Weekly Timekeeping screen was fixed. The error occurred when a division did not have a Transportation Mode configured. OPS-32354
21.49.0.0 CORR An issue where the EmployeeDayTypeGroups pay accessory group was not loaded before timekeeping calculations were performed was fixed. OPS-32357
21.49.0.0 CORR Critical: An issue where the Reduce Pay Code Group weekly pay rule double-counted time from another weekly pay rule was fixed. OPS-32364
21.50.0.0 CORR Critical: An issue in the Prior Pay Adjustments screen where the prior pay log didn't capture some user changes to employee data and activities was fixed. OPS-32453