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:
  • TiSurvey - Primary record for storing the survey information. One record will be created for each newly added survey. The table has the following fields: tiSurveyId, startTime, endTime, and internalTitle.
  • TiSurveyContent - Stores the actual survey contents for the specific TiSurvey record. The table has a one-to-many relationship with TiSurvey, where a TiSurvey record can have one or more TiSurveyContent records associated with it. The table has the following fields: tiSurveyContentId, tiSurveyId, languageId, description, and surveyUrl.
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:
  • Core/SQL/ODBC/Statement Monitor/Enable
  • Core/SQL/ODBC/Statement Monitor/Report Threshold
  • Core/SQL/ODBC/Statement Monitor/Report Blocked Transactions
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, MAP/MapAddress/Google/Params/Result Place Types has been changed to: premise, street_address, establishment. TI-14239
21.13.0.0 ENH Added a new Trapeze6 property(context property): PASS/PassInfoServer/CreateTrip/TripOverlap/CheckOnlyMatchingOD. 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 PASS/PassInfoServer/Defaults/FareTypeId Trapeze6 property linked to the incorrect Trapeze4 property, PASS/PassInfoServer/PASS Booking Client/Default Space Type. The LegacyId used was incorrect. Now, LegacyId is linked to PASS/PassInfoServer/Faring/Default Fare Type in Trapeze4.

MODTE-40
21.18.0.0 ENH

A new context property was added: PASS/PassInfoServer/SmartCard/AllowUserManagementExpression to support Smart card method updates.

This is a client expression that’s used to determine if a given client is allowed to manage their smart card information. If it is set to True or if it’s blank, then the client is allowed. Otherwise they aren’t allowed.

MODTE-432
21.18.0.0 ENH
The following two context properties were created to update the ValidateSmartCard method to include validations for Cubic smart cards:
  • PASS/PassInfoServer/SmartCard/Cubic/NumberOfIdDigits: A comma-separated list of values representing the number of digits that comprise a valid Cubic card ID.
  • PASS/PassInfoServer/SmartCard/Cubic/ValidIdPrefixes: A comma-separated list of valid prefixes for Cubic card IDs. Card IDs must be numeric so it is assumed that the values for this property are also numeric.

MODTE-400
21.19.0.0 ENH

A new context property was added: PASS/PassInfoServer/SmartCard/AllowUserManagementExpression to support Smart card method updates. This is a client expression that’s used to determine if a given client is allowed to manage their smart card information. If it is set to True or if it’s blank, then the client is allowed. Otherwise they aren’t allowed.

MODTE-432
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 expects an HTTP 1.1 message.

DEVCORE3-5581
21.21.0.0 ENH

In PassInfoServer, improved the performance of the PassGetClientTrips method by reducing simple repeated operations.

MODTE-907