General
Release notes on some items that apply to more than one Traveler Experience module.
| Version | Type | Description | ID |
|---|---|---|---|
| 21.1.0.0 | ENH | Logging to report certificate verification failures was improved to show more detail. This addresses an issue where the Client Shell would not connect to the Service Shell over SSL when the certificate chain contained more than one trusted authority. | DEVCORE3-5435 |
| 21.1.0.0 | CORR | An issue where v19 Client Shells were unable to log into newer Service Shells (for example, v21) has been fixed. | DEVCORE3-5438 |
| 21.1.0.0 | CORR | The issue of the link to confirm the change in a user's email address not being formed properly has been fixed. | TI-17750 |
| 21.2.0.0 | CORR | To fix the issue of multiple Service Shells using different profiles that were started in the same installation folder from sharing the same log file, switches have been added to enable the addition of the Profile and ID in the log file names produced by the FileTraceListener and WxCX logs. (For example, SrvShell_20211110_001.log becomes SrvShell_localhost_Primary_20211110_001.log.) Also, the "_Backup" suffix is now added to the log file name if the Service Sell was started as the backup server in an HA configuration. | DEVCORE3-5458 |
| 21.2.0.0 | ENH | DB-Schema changes: The following tables have been added to allow agencies to
create surveys using third party software such as SurveyMonkey and Google Forms:
|
TI-18235 |
| 21.3.1.0 | CORR | The issue related to the stored procedure for the CoreCleanupAuditContext feature causing a deadlock for some SQL users has been fixed. | DEVCORE3-5460 |
| 21.3.1.0 | CORR | The issue of the scripts used to update context properties to different versions not working for Oracle databases has been fixed. | TI-18405 |
| 21.3.1.0 | CORR | The issue that occurred when the event service was under heavy usage causing exceptions in the log and the Service Shell becoming unresponsive has been fixed. | DEVCORE3-5482 |
| 21.3.1.0 | ENH | When the application is configured to generate a crash dump on an exception, the log now includes a trace output with the name and path of the dump file and the type of the exception. | DEVCORE3-5484 |
| 21.3.1.0 | ENH | Improved Structured Exception (SE) handling with the addition of the ability to terminate the application abnormally when the first SE occurs and to generate a crash dump that can provide better data on the cause of the error. | DEVCORE3-5478 |
| 21.3.1.0 | CORR | The issue related to the stored procedure for the CoreCleanupAuditContext feature causing a deadlock for some Oracle users has been fixed. | DEVCORE3-5446 |
| 21.4.1.0 | ENH | A crash dump file is now generated during shutdowns from exception handling action. | DEVCORE3-5500 |
| 21.7.0.0 | ENH | The following new switches have been added to enable and control the monitoring
of long running ODBC SQL statements:
|
DEVCORE3-5524 |
| 21.8.0.0 | CORR | The issue of the ODBC Statement Monitor blocked query report not working with the Oracle native ODBC 12 (or earlier) driver has been fixed. | DEVCORE3-5530 |
| 21.9.0.0 | ENH | Users can now select from multiple choices when defining context properties in the Client Shell. | DEVCORE3-5392 |
| 21.11.0.0 | CORR | The issue of contents of other folders sometimes being shown together with those of the selected folder in the Properties screen has been fixed. (This is related to OPS-27091.) | DEVCORE3-5539 |
| 21.11.0.0 | ENH | The default value of the context property, has been changed to: premise, street_address, establishment. | TI-14239 |
| 21.13.0.0 | ENH | Added a new Trapeze6 property(context property): . When enabled, trip overlap check only applies to previous bookings with same origin and destination as current one. This change was made to validate pass bookings and pass booking times window returned. If enabled, "CheckOnlyMatchingOD", booking window will return time slots that have trips with different OD. | TI-20175 |
| 21.16.0.0 | CORR |
Fixed an issue where trips booked online had a fare type set to N/A which resulted in a $0 fare. This was caused by the Trapeze6 property linked to the incorrect Trapeze4 property, . The LegacyId used was incorrect. Now, LegacyId is linked to in Trapeze4. |
MODTE-40 |
| 21.16.0.0 | CORR | The issue of not all the vehicles were being shown on the realtime map during a specific time of the day has been fixed. | MPSTE-991 |
| 21.17.0.0 | CORR |
A new context property, has been added. If selected, the value is trimmed starting from the left of the vehicle ID to make it an integer and to match the TP6 data structure. |
MPSTE-2240 |
| 21.18.0.0 | CORR | The following new context properties have been added to fix issue of having
the customer name only being validated on the client side:
|
MPSTE-2179 |
| 21.21.0.0 | CORR | Fixed an issue of unexpected socket closures that can occur when a Workstation or Client Shell that previously called an HTTP 1.0 third party service later calls a Tp6 Service Shell or Schedule Server also with an HTTP 1.0 message but which expects an HTTP 1.1 message. | DEVCORE3-5581 |
| 21.27.0.0 | CORR | Fixed the result of supplying the wrong returned parsed data from Transit Master to the Service Adjustment when using the ICD Interface. | MPSTE-2848 |
| 21.41.0.0 | ENH | Added logic to check for the presence of the Init.Trips table and convert the
feed trip ID to the Trapeze trip ID if the table exists; otherwise, the feed trip ID
is assumed to be the Trapeze trip ID. Service adjustments are now consolidated so that a single adjustment is created for consecutive stop sequences. OverloadId is now set to the FeedEntityId from the feed. The Offset value is calculated based on the difference between the trip's start_time in the feed and the ETime of the start of the sequence. VehicleName in InfoServiceAdjustment is now set using trip_update.vehicle.label or trip_update.vehicle.id if provided by the feed. Added additional logging at the Service Adjustment Insertion step for improved traceability. |
MPSTE-3624 |
| 21.41.0.0 | ENH | Introduced the TiGTFSRTServiceAdjustment table to store imported entities and
their associated service adjustments. Implemented Record Managers for InfoServiceAdjustment and TiGTFSRTServiceAdjustment tables to manage insertion and deletion operations. Added an ImportedServiceAdjustmentCache to track currently imported entities. Enhanced the Service Adjustment Importer to update and clean up feed entities, removing old records and replacing updated entities as needed. |
MPSTE-3623 |
| 21.41.0.0 | ENH | Introduced a Service Adjustment Sub Importer within the Trip Update Importer,
supporting schedule relationships: ADDED (Overload), CANCELED (Canceled), and
DUPLICATE (Offset) Required fields for each import: ADDED: trip.trip_id, trip.schedule_relationship, trip.start_date, trip.route_id, stop_time_update.stop_sequenceCANCELED: trip.trip_id, trip.schedule_relationship, trip.start_date, trip.route_id, stop_time_update.stop_sequence DUPLICATE: trip.trip_id, trip.schedule_relationship, trip.start_date, trip.route_id, stop_time_update.stop_sequence, stop_time_update.departure.delay The context property can now be configured to Vehicle Adherence, Service Adjustment, or Both. |
MPSTE-3622 |
| 21.45.0.0 | ENH | Route Direction Name now uses trip_headsign from trips.txt. Increased size of
DirectionName field in the Lines table. Added context properties to control
headsign truncation:
|
MPSTE-3841 |
| 21.45.0.0 | CORR | Added the missing column to the Datacube Engine Rowset. | MPSTE-3887 |