General
Release notes on some items that apply to more than one Traveler Experience module.
| Version | Type | Description | ID |
|---|---|---|---|
|
19.0.2.0 |
ENH | The issue of notifications being generated for clients who are inactive or whose EligToDate (Eligibility To Date) records were blank has been fixed. | TI-8162 |
|
19.0.2.0 |
ENH | The following changes have been made on context properties affecting voice
notifications for booking :
|
TI-8163 |
|
19.0.3.0 |
CORR | The vehicle number information is now correctly read out during Vehicle Arrived call outs. | TI-11462 |
|
19.0.3.0 |
CORR | The issue of blank messages being sent for SMS schedule based alerts has been fixed. | TI-11315 |
|
19.0.4.0 |
CORR | The default value for the Core/Locale/Formats/Date YY Pivot Year context property has been changed from 1920 to 1930 to prevent process failures due to the change in the year. This change relates to the Core/Locale/Formats/Date Display Format context property where users can choose format options that display the year as YY (two digits). The Date YY Pivot Year property determines how the system interprets YY. | DEVCORE3-4959 |
|
19.0.4.0 |
CORR | Resolved the issue that could lead to the Service Shell failing or reporting an exception when more than one Service Shell is running on the same machine and each one is writing to its own CDBLog window. | DEVCORE3-4777 |
|
19.0.4.0 |
CORR | The issue of the Service Shell intermittently failing in some servers in a
multi server environment has been fixed. To minimize memory issues related to
caching, the following switches have been added under Info/InfoWeb/Itinerary Caching
in Trace Options:
|
TI-11966 |
|
19.0.5.0 |
CORR | Password changes from CliShell now encrypt both the password and the user name when transmitted from the Client Shell to the Service Shell. This encryption is done even over non-SSL connections. For v19, the encryption method is set in the Core/Security/Policy/Password Storage/Algorithm context property, which also controls the algorithm used to store passwords in context properties and the database password in the Service Shell profile file. For versions 16 to 18, the default method is option 1, TCF1. | DEVCORE3-4968 |
|
19.0.5.0 |
CORR | The issue of a new Service Shell session object and ID being created even when not needed when a user logged into the Client Shell has been fixed. The issue occurred when the Service Shell switch, Core/Security/Change Session on Login was On. | DEVCORE3-4978 |
|
19.0.5.0 |
CORR | The issues with the route numbers being repeated and the incorrect date formats in service notices have been fixed. | TI-12086 |
| 19.0.6.0 | CORR | The error that occurred when resending account activation email messages in TransitNow has been fixed. | TI-12448 |
|
19.0.6.0 |
CORR | The issue of service alerts for stops notifications not being displayed has been fixed. | TI-12939 |
|
19.0.6.0 |
CORR | Users who do not need to edit context properties or user security settings do
not require grant permissions for the following security keys to run the Client
Shell:
|
DEVCORE3-5175 |
|
19.0.8.0 |
CORR | The issue of unnecessary content appearing on TransitNow activation email messages has been fixed. | TI-13953 |
| 19.0.10.1 | CORR | The issue of special characters appearing encoded in SMS messages sent with TextMarks has been fixed. | TI-14794 |
|
19.0.10.1 |
CORR | When users register for an account, they now receive an activation email message, which allows them to create their passwords to complete their account registration. | TI-14487 |
|
19.0.11.0 |
CORR | Fixes: In some instances, the Tp4 Workstation or Client shell may send the user's credentials to the SrvShell in an HTTP Basic Authorization header field, which is open text and therefore not considered secure. | DEVCORE3-5364 |
|
19.0.11.0 |
CORR | The issue of the current date instead of the trip date being used to calculate the expiry and delivery time for Imminent Arrival notifications past midnight has been fixed. | TI-15291 |
|
19.0.11.0 |
CORR | The issue of incorrect identity field values being returned when using an Oracle database with Real Application Clusters (RAC) has been fixed. | DEVCORE3-4644 |
| 19.0.13.0 | CORR | The issue of users, who have the advanced drop-off notifications enabled, not receiving separate notifications for all their bookings on a given date has been fixed. Previously, users with multiple bookings on a given date only received a notification for the first trip of that date. | TI-15856 |
| 19.0.13.0 | CORR | The issue of cancellations and detours from TransitMaster not being applied to both the arrival and departure times of a stop in the middle of the affected route has been fixed. | TI-14767 |
|
19.0.14.0 |
CORR | The issue of the incorrect order that services were run when the Service Shell was started has been fixed. | DEVCORE3-5377 |
| 19.0.14.0 | CORR | An issue where updating context properties in the Client Shell resulted in TCF Event notifications for the change being posted twice has been fixed. | DEVCORE3-5404 |