OPS v19.0.26 Release Notes

These release notes are for the most recent version of OPS v19.0.x. Refer to the Enhancements and Corrections tables for a complete list of modifications in OPS v19.0.x.

General

  • Critical: Fixed a processing issue with the OPSMONAssignments data table that would cause it to stop updating abruptly. (ID: OPS-29786)

Bidding

  • An issue where a bid was awarded message was sent to employees who were not awarded bid work (when bid processing stopped on their record in the Bidding screen was fixed). Now, employee messages are only sent when work is actually awarded. (ID: OPS-29813)

Dispatch

  • An issue in the Daily Activity screen where creating quick extra work and then selecting Split or Undo Split Work resulted in an Assert error was fixed. (ID: OPS-29932)
  • An issue in the Edit Work Times dialog in the Daily Activity screen where entered Comments were not retained was fixed. (ID: OPS-29805)
  • An issue in the Extra Work screen where the Default Activity Type field was not automatically populated was fixed. (ID: OPS-29587)
  • Critical: An issue in the Daily Activity screen where the Smart Filter only returned one result when filtering by Work Name if multiple extra work records with the same Work Name existed was fixed. (ID: OPS-17760)

Schedule Import

  • Blocker: An issue in Schedule Import where an assert error occurred when using SQL 2016 and below was fixed. (ID: OPS-29826)

Workforce Management

  • An issue where performance charges could be applied to open-ended absences (those without a defined To Date) was fixed. Now, if you select Add Performance Details on an open-ended absence, an error message appears. (ID: OPS-29692)

Yard Management

  • Blocker: An issue in the Vehicle Assignment screen when the OPS > Dispatch > Daily Activity > Enable Smart Filter property was selected where entering a time in the Split Block dialog caused the Client Shell to crash was fixed. (ID: OPS-29241)

Accruals

  • Blocker: An issue where an insufficient accruals message appeared and accruals were not generated even though the employee had enough accrual hours was fixed. (ID: OPS-30013)
  • Blocker: An issue where accrual generation failed when there was an existing accrual record on the accrual date was fixed. Now, the process completes and no new accrual is generated for the employee with the accrual record. (ID: OPS-29845)