INFO-Web G3

Version	Type	Description	ID
19.0.3.0	ENH	The issues related to the Favorite (star) icon in the Trip Planner screen in Spanish have been fixed.	TI-8020
19.0.4.0	CORR	The issue of itineraries not being generated for trips when no walking speed has been set has been fixed.	TI-11767
19.0.8.0	CORR	The issue of not having all the bus icons displayed on the map for trips with mid-trip layovers when Real Time Manager service was used has been fixed.	TI-11986
19.0.10.1	ENH	A new context property, MaxDistanceToConsiderWalking has been added. It sets the maximum distance to be recommended for a user to walk. If the straight line distance between the trip origin and destination is less than this value, the ConsiderWalking flag of the itinerary (in the ItineraryLookup response) is set to "1", otherwise, it is set to 0. The default is 0, which is the minimum value and 5000 meters is the maximum value. (This property is under INFO/Info Web/DefaultOptions/ in versions 13 and 14 and under TravelerInformation/FixedRoute/InfoWeb/in versions 15 and higher.) In versions 13 to 15, the description of the TravelerInformation/FixedRoute/InfoWeb/TripPlanning/MaxDistanceForWalkingDirections context property has been changed to setting the distance of the walking leg for it to be displayed. The walking instructions are displayed if the distance to be walked is greater or equal to the set value. In version 16, TravelerInformation/FixedRoute/InfoWeb/TripPlanning/MaxDistanceForWalkingDirections context property has been changed to TravelerInformation/FixedRoute/InfoWeb/TripPlanning/MinDistanceForWalkingLegDirections. The change reflects the proper usage of the property, which is to set the minimum distance of the walking leg for it to be displayed, i.e., if the walking distance is less than the set value, the walking instructions are not displayed.	TI-3322
19.0.18.0	CORR	The issue of the list of stops not being shown when users attempted to view the Route schedule has been fixed.	TI-17924
19.0.21.0	CORR	The issue of the sum of the walking distances/times of the itinerary legs sometimes not matching the total walking distance/time shown in the itinerary results has been fixed.	TI-18852
19.0.21.0	CORR	The issue of users not being able to email itinerary results when using the Email Itinerary feature has been fixed. Previously, users were able to email the results successfully on their first attempt but sometimes their subsequent attempts produced errors.	TI-18865
19.0.23.0	CORR	The issue of the itinerary search results not being sorted properly based on the selected sorting option has been fixed.	TI-20112
19.0.23.0	CORR	The issue of the Loading Itineraries screen sometimes appearing to be stuck or frozen during an itinerary plan search has been fixed.	MPSTE-1911
19.0.23.0	CORR	A new context property, INFO/Lookup/Instance/LookupInfoRemarks/Enable MultiLanguage Check has been added. The property has to be enabled if multiple language support is required to view remarks (alerts) in the Headway sheet.	MPSTE-1902
19.0.25.0	CORR	A new context property, TravelerInformation/FixedRoute/Common/ClosestStop/RouteDisplayOrder has been added. If selected, users can select how the routes are sorted and displayed based on the nearby stops. The options are: Route name - Sorted by LineAbbr. This is the default. Trip - Sorted by the earliest trip time of the route. (When selected, processing time maybe slower because stop times must be retrieved and processed first.) User - Sorted by the user-defined sort order in the Line table. Note: This property does not apply to ATIS because ATIS always sorts routes by name.	MPSTE-2465
19.0.25.0	CORR	The issue of the itinerary planning results not being sorted properly when sorted by walking distance has been fixed.	MPSTE-2107
19.0.25.0	CORR	The issue of the routes not being displayed when the context property, TravelerInformation/FixedRoute/Common/NextDepartures/RouteDisplayOrder was set to User has been fixed.	MPSTE-2535 This task is related to DEVCORE3-4450.
19.0.25.0	CORR	The issue that occurred when users searched for bus times on a future date that happened to be the last date of the current sign-up period has been fixed.	MPSTE-2158
19.0.25.0	CORR	The issue of the itinerary results not being sorted properly based on trip times has been fixed. The results are now sorted properly whether the itinerary was newly generated or retrieved from the cache.	MPSTE-2231

19.0.3.0

ENH

The issues related to the Favorite (star) icon in the Trip Planner screen in Spanish have been fixed.

TI-8020

19.0.4.0

CORR

The issue of itineraries not being generated for trips when no walking speed has been set has been fixed.

TI-11767

19.0.8.0

CORR

The issue of not having all the bus icons displayed on the map for trips with mid-trip layovers when Real Time Manager service was used has been fixed.

TI-11986

19.0.10.1

ENH

A new context property, MaxDistanceToConsiderWalking has been added. It sets the maximum distance to be recommended for a user to walk. If the straight line distance between the trip origin and destination is less than this value, the ConsiderWalking flag of the itinerary (in the ItineraryLookup response) is set to "1", otherwise, it is set to 0. The default is 0, which is the minimum value and 5000 meters is the maximum value. (This property is under INFO/Info Web/DefaultOptions/ in versions 13 and 14 and under TravelerInformation/FixedRoute/InfoWeb/in versions 15 and higher.)

In versions 13 to 15, the description of the TravelerInformation/FixedRoute/InfoWeb/TripPlanning/MaxDistanceForWalkingDirections context property has been changed to setting the distance of the walking leg for it to be displayed. The walking instructions are displayed if the distance to be walked is greater or equal to the set value. In version 16, TravelerInformation/FixedRoute/InfoWeb/TripPlanning/MaxDistanceForWalkingDirections context property has been changed to TravelerInformation/FixedRoute/InfoWeb/TripPlanning/MinDistanceForWalkingLegDirections. The change reflects the proper usage of the property, which is to set the minimum distance of the walking leg for it to be displayed, i.e., if the walking distance is less than the set value, the walking instructions are not displayed.

TI-3322

19.0.18.0

CORR

The issue of the list of stops not being shown when users attempted to view the Route schedule has been fixed.

TI-17924

19.0.21.0

CORR

The issue of the sum of the walking distances/times of the itinerary legs sometimes not matching the total walking distance/time shown in the itinerary results has been fixed.

TI-18852

19.0.21.0

CORR

The issue of users not being able to email itinerary results when using the Email Itinerary feature has been fixed. Previously, users were able to email the results successfully on their first attempt but sometimes their subsequent attempts produced errors.

TI-18865

19.0.23.0

CORR

The issue of the itinerary search results not being sorted properly based on the selected sorting option has been fixed.

TI-20112

19.0.23.0

CORR

The issue of the Loading Itineraries screen sometimes appearing to be stuck or frozen during an itinerary plan search has been fixed.

MPSTE-1911

19.0.23.0

CORR

A new context property, INFO/Lookup/Instance/LookupInfoRemarks/Enable MultiLanguage Check has been added. The property has to be enabled if multiple language support is required to view remarks (alerts) in the Headway sheet.

MPSTE-1902

19.0.25.0

CORR

A new context property, TravelerInformation/FixedRoute/Common/ClosestStop/RouteDisplayOrder has been added. If selected, users can select how the routes are sorted and displayed based on the nearby stops. The options are:

Route name - Sorted by LineAbbr. This is the default.
Trip - Sorted by the earliest trip time of the route. (When selected, processing time maybe slower because stop times must be retrieved and processed first.)
User - Sorted by the user-defined sort order in the Line table.

Note: This property does not apply to ATIS because ATIS always sorts routes by name.

MPSTE-2465

19.0.25.0

CORR

The issue of the itinerary planning results not being sorted properly when sorted by walking distance has been fixed.

MPSTE-2107

19.0.25.0

CORR

The issue of the routes not being displayed when the context property, TravelerInformation/FixedRoute/Common/NextDepartures/RouteDisplayOrder was set to User has been fixed.

MPSTE-2535

This task is related to DEVCORE3-4450.

19.0.25.0

CORR

The issue that occurred when users searched for bus times on a future date that happened to be the last date of the current sign-up period has been fixed.

MPSTE-2158

19.0.25.0

CORR

The issue of the itinerary results not being sorted properly based on trip times has been fixed. The results are now sorted properly whether the itinerary was newly generated or retrieved from the cache.

MPSTE-2231