General
Release notes on some items that apply to more than one Traveler Experience module.
| Version | Type | Description | ID |
|---|---|---|---|
|
19.1.0.0 |
CORR | The issues with the route numbers being repeated and the incorrect date formats in service notices have been fixed. | TI-12086 |
| 19.1.0.0 | CORR | The error that occurred when resending account activation email messages in TransitNow has been fixed. | TI-12448 |
|
19.1.0.0 |
CORR | The issue of service alerts for stops notifications not being displayed has been fixed. | TI-12939 |
| 19.1.0.0 | CORR | The issue of service notice data not being imported from TransitMaster has been fixed. | TI-13456 |
| 19.1.0.0 | CORR | The following changes have been added to allow the logging of all incoming
real-time data in a file:
|
TI-12257 |
|
19.2.0.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.2.0.0 | ENH | Added functionality to get the stop accessibility information from the line details. | TI-14379 |
| 19.2.0.0 | CORR | The issue of unnecessary content appearing on TransitNow activation email messages has been fixed. | TI-13570 |
| 19.2.0.0 | ENH | DB-Schema change: A new field, LockedTimeStamp has been added to the Registered Users table. This is used to save the time value in the database when a user account is locked and relates to the TravelerInformation/FixedRoute/TransitNow/Password/AutomaticUserAccountUnlockPeriod property. | TI-13957 |
| 19.2.0.0 | ENH | The following changes have been made to support the ability to unlock user
accounts when resetting passwords:
|
TI-13055 |
| 19.3.0.0 | CORR | The issue of special characters appearing encoded in SMS messages sent with TextMarks has been fixed. | TI-14794 |
|
19.3.0.0 |
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.4.0.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.4.0.0 | ENH | Added a new trace switch, Info/Lookup/ICDInterface/Trace, to control general trace logging in the CDBLog as well as a number of verbose trace messages, mainly focused on the ICDInterface::Default method. | TI-15714 |
| 19.4.0.0 | ENH | Native SSL support has been added to Trapeze applications using the Trapeze4 platform. | DEVCORE3-5356 |
|
19.4.0.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.5.0.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.6.0.0 | ENH | Improved logging of the Service Shell if errors occurred when calls were made to the INFO-MON shell to refresh the cached data. | TI-13556 |
| 19.6.0.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.7.0.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.7.0.0 |
CORR | The issue of the incorrect order that services were run when the Service Shell was started has been fixed. | DEVCORE3-5377 |
| 19.7.0.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 |
| 19.7.0.0 | CORR | The issue of the CoreMQ services not starting or causing errors when more than
one Service Shell are running in the same server has been fixed. When configuring a
Trapeze application that requires the Cmn_Lookup service group but does not require
INFO-MON CoreMQ, one or more of the following service groups may be included instead
of Cmn_Lookup in the profile file:
Add Cmn_LookupBase if using any of these Lookup groups. |
TI-16515 |
| 19.8.0.0 | CORR | The issue of the temperature in Celsius on the Wayside screen incorrectly being converted to the Fahrenheit scale has been fixed. (The format is set in the Core/Locale/Formats/Temperature context property.) | TI-14349 |
| 19.29.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 |