Schedule Import
Release notes for schedule information import and modification features.
| Version | Type | Description | ID |
|---|---|---|---|
| 21.1.0.0 | CORR | An issue where importing more than two FX holidays when the first FX holiday wasn't already in OPS Holiday and the second Holiday ID was the Max Holiday ID + 1 resulted in an SQL error has been fixed. | OPS-24633 |
| 21.2.0.0 | CORR | Load exception performance has been improved. Now, only exceptions related to runs and trips in the current sign-up period are loaded. | OPS-25081 |
| 21.3.1.0 | ENH | Critical: An issue in mid-signup imports where roster changes weren't imported as expected when Runs in Signup without runversionid=0 records were included has been fixed. | OPS-25548 |
| 21.4.1.0 | CORR | An issue where importing into an existing sign-up period removed all holiday work from extra work rosters for the import period was fixed. | OPS-25920 |
| 21.4.1.0 | CORR | An issue when importing from Trapeze FX using Schedule Import where a second record was created when line names appeared in a different case (lowercase vs. uppercase) has been fixed. Now, if the only line abbreviation difference between the existing record and the new record is its case, OPS updates the current line with the newly imported line information. | OPS-25897 |
| 21.8.0.0 | CORR | Fixed an issue where using the Import Into An Existing Sign-Up Period functionality in OPS Sign-Up Management resulted in overlapping and invalid data. | OPS-26680 |
| 21.11.0.0 | CORR | Fixed an issue where the ability to delete a sign-up period by right-clicking and selecting Delete could be enabled even when the Delete Sign-up Period option in the menu bar was disabled. Both methods of deleting a sign-up period are now uniformly enabled or disabled. | OPS-17669 |
| 21.12.0.0 | CORR | Fixed an issue that would cause an error when attempting to perform a FX Runline Costing Import via OPS Line Costing. | OPS-27289 |
| 21.16.0.0 | CORR |
Fixed issues with the FX Schedule Import feature that caused unwanted changes to the FX tables for Line and MasterLine. The system no longer updates the FX data when importing schedules, and preserves the original formatting and sorting of the FX information. Improved the logic for comparing lines from FX and OPS when importing schedules. The system now uses trim functions to remove any leading or trailing spaces from the line abbreviations and names, and avoids creating duplicate or incorrect lines. Added a solution to clean up the FX data using appropriate delimiters and text transformers. The system now allows replacing spaces with ‘0’ or other characters for sorting purposes, and documents the fields that interact with FX data. |
OPS-28235 |
| 21.16.0.0 | CORR |
Fixed an issue where the ModBy field in the OpsTravels table was not updated with the OPS user who initiated the schedule import. Updated other schedule import tables to use the OPS user’s identity name as the ModBy value. |
OPS-28023 |
| 21.21.0.0 | ENH | Blocker: An error message was added to address an issue where an Exception error occurred when using the Schedule Import screen for HASTUS imports (the property is set to Hastus 2010) without a custom service being defined. | OPS-28831 |
| 21.21.0.0 | CORR | An issue when importing from HASTUS where trips that pulled out the day before service gave incorrect error messages because OPS did not support negative time was fixed. Now, block times are adjusted to match trip times. | OPS-28627 |
| 21.24.0.0 | ENH | OPS now supports HASTUS imports that include non-operating holidays. | OPS-29342 |
| 21.26.0.0 | ENH | Blocker: A new system property was added: . If selected, when importing FXMasterLine to OPSMasterLine and
information already exists in OPS, the system updates OPSMasterLine data to match FX
MasterLine data. This property is cleared by default. The system was updated so that if is selected, then applicable defined UserString supplementary data is now also imported. |
OPS-29637 |
| 21.27.0.0 | CORR | Blocker: An issue in Schedule Import where an assert error occurred when using SQL 2016 and below was fixed. | OPS-29826 |
| 21.33.0.0 | CORR | Schedule Import now shows only relevant options in the Context (F3) Agency field, based on the dependencies defined in the property. | OPS-30481 |
| 21.34.0.0 | CORR | In Schedule Import, a validation message was added for scenarios where a run
type name or run type abbreviation will be overwritten during an import. Trapeze suggests not reusing existing run types. In the event a run type is reused it may result in historical data alteration. |
OPS-30817 |
| 21.35.0.0 | ENH | In Schedule Import, a validation message was added for scenarios where a run
type name or run type abbreviation will be overwritten during an import. Trapeze suggests that existing run types are not reused. In the event a run type is reused it may result in historical data alteration. |
OPS-30817 |
| 21.37.0.0 | CORR | An issue where HASTUS schedules could not be imported if the first record was for a holiday was fixed. | OPS-31119 |
| 21.38.0.0 | ENH | Blocker: Improvements were made to address an issue with Schedule Import where
blocks with overlapping trip times couldn't be imported when they contained
different exception values. Now, if there are overlapping trips and the ExcCombo is defined as Off, a warning is given. For other overlapping ExcCombo values, an error is given. |
OPS-31203 |
| 21.39.0.0 | CORR | An issue where an error referencing OPSDailyScheduleBlocks appeared when importing a schedule from HASTUS was fixed. | OPS-31254 |
| 21.39.0.0 | ENH | A Schedule Import failure message that occurred when FromTime was null was updated. Assert(NotNull) Failed. (>=) Attempt to compare null Times was updated to Run[Id:Number RunVersionId: Number] PieceNumber does not have a valid FromTime, toTime. Please fix the FX Data and import again. | OPS-31302 |
| 21.40.0.0 | CORR | Critical: Messaging was updated for the situation where a second user attempted
to import a schedule when a schedule import was already running. Now, when the second attempt is made, a log message indicates the user who is currently running a schedule import and when the first import was started. |
OPS-28891 |
| 21.40.0.0 | CORR | Error handling was added to address an issue in OPS Sign-Up Management where using the Import Into An Existing Sign-Up Period option after updating line names didn't import schedule data. | OPS-31013 |
| 21.40.0.0 | ENH | In Schedule Import, system handling of HASTUS imports was updated. | OPS-31377 |
| 21.41.0.0 | CORR | Blocker: Code for OPS-30805 was reverted to resolve an issue in Schedule Import where unexpected overlapping trips messages were shown in the import log. Only transit agencies who schedule blocks with overlapping trip times were affected. This issue resulted in missing runs in WorkPlanner, Dispatch and bid lists and affected v21.36–v21.39. | OPS-31485 |
| 21.41.0.0 | ENH | An issue with Schedule Import where no consists were generated for activated dates after importing new sign-up periods was fixed. | OPS-30509 |
| 21.42.0.0 | CORR | Critical: An issue with Schedule Import where drive time wasn't calculated as expected because of missing pull-out information was fixed. | OPS-31620 |
| 21.43.0.0 | ENH | Schedule Import was updated to improve system behavior around importing EXC
(Exception) trips. Now, if a block is part of the Off exception and includes
overlapping trips but the Off exception is not used in any dates in the FX Calendar,
then duplicate trips are removed. Import will continue and a warning message is
shown. Otherwise, (if the Off exception is being used or if another exception combination is used) if overlapping trips are found, the blocks cannot be imported. The source schedule must be fixed to import the blocks. |
OPS-31746 |
| 21.44.0.0 | CORR | Blocker: An issue in Schedule Import where some Trip Types were not imported and error messages indicated no matching trip records existed was fixed. Now, all FX trip types are treated as regular (RG) trips during import. | OPS-31820 |
| 21.46.0.0 | CORR | Critical: An issue where service group filtering was not applied as expected, resulting in the wrong work being shown to operators during bids was fixed | OPS-32030 |
| 21.46.0.0 | CORR | Blocker: An issue with Schedule Import where mid-signup imports deleted trip details from outside the imported sign-up period was fixed. | OPS-32113 |
| 21.49.0.0 | CORR | Blocker: An issue where negative BlockVersionId values were imported during a mid-signup schedule import was fixed. | OPS-32455 |