INFO-Web G3

Release notes on tasks that apply to INFO-Web G3.

Version Type Description ID
19.1.0.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:
  • Retention Period: Amount of time that individual cached itinerary results are retained after their last use. Note: The check to remove data is in the clean-up timer, so entries could exist a bit longer than this value.
  • Cache Dump Timer: Number of times to trace the information about the cache.
  • Cache Cleanup Timer: Number of times to check the cleanup of the old entries in the cache.
  • Real Time Data Retention Period: Amount of time that the same cached real time data is reused. The requests to cached data beyond this time will require reapplication of real time data.
 TI-11966

19.1.0.0

 CORR The issue of itineraries not being generated for trips when no walking speed has been set has been fixed. TI-11767
19.2.0.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.3.0.0

 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.3.0.0 ENH Support added for Google reCAPTCHA version 3 for INFO web applications. TI-15195
19.5.0.0 ENH Support added to enable or disable real-time in the Next Departures, Trip Planning, and Headway Sheet screens. TI-14719
19.5.0.0 ENH Support added to display custom HTML error pages that are mapped to the various HTTP error codes. Default error pages will be displayed if there are no corresponding custom ones. TI-15560

19.12.0.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.16.0.0 CORR The issue of stay-in-seat transfers being included in itinerary results when not applicable has been fixed. TI-18851
19.16.0.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.16.0.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.16.0.0 CORR The following changes were made to fix the issue of the final walking time not always being added when calculating the arrival time for an itinerary:
  1. Added an optional filter for trip planning itineraries to use strict time checks that include walking times. If enabled, only itineraries that start walking after the leave-at time and itineraries that end walking before the arrive by time are displayed.
  2. Added the following context properties to enable and control the strict time window: TravelerInformation > FixedRoute > InfoWeb > TripPlanning > StrictTimeChecking and TravelerInformation > FixedRoute > InfoWeb > TripPlanning > StrictTimeWindow.
 TI-19275
19.18.0.0 CORR The issue of a missing parameter needed to calculate service adjustments for a specified leg when performing itinerary searches has been fixed. TI-19488
19.21.0.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.22.0.0 CORR The issue of the HTML codes not being rendered properly in the Notification email from remarks and on the stop-based alerts after users click the stop has been fixed TI-20333
19.23.0.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.27.0.0 CORR To fix the BsmAncillary service error, the following changes were made:
  1. If the TravelerInformation > FixedRoute > BusStopManager > UseBsmService property is set to Off (false), InfoBsm Helper is no longer initialized. This is now set to Off by default.
  2. A new switch, Info/InfoBsmHelper/Trace has been added for the InfoBsm Helper logs.
  3. Extra logging information has been added.
  4. The format of the String.Format warnings has been changed.
MPSTE-2369
19.29.0.0 CORR The issue of remarks created through the GTFS-RT Engine not being displayed in INFO-Web G3 or INFO-Agent has been fixed. MPSTE-2482
19.29.0.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.29.0.0 CORR The issue of the itinerary planning results not being sorted properly when sorted by walking distance has been fixed. MPSTE-2107
19.30.0.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.31.0.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.31.0.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.32.0.0 CORR The issue of the Search results not showing the routes sorted consistently by direction has been fixed. MPSTE-2659

This is task is related to MPSTE-2568.
19.33.0.0 CORR The display of remarks in headway alerts and trip-specific alerts was corrected by eliminating the termination logic within the loop of the column names, which was used to verify if the column name began with the anticipated value. MPSTE-2757
19.33.0.0 ENH Implemented the integration of an Occupancy field within the Bus information window, displaying pertinent Occupancy data sourced from the ALPHA system. MPSTE-2713
19.33.0.0 CORR Updated the definition for valid Schedule Adherence to not require Latitude and Longitude. MPSTE-2718
19.36.0.0 CORR Removed the logic for trimming leading 0s from column names. MPSTE-3118
19.38.0.0 CORR Implemented the feature to only display vehicles with real-time information when the context property TravelerInformation > FixedRoute > RealtimeMapDisplay > DisplayOptions > ShowVehicleWithRealTimeOnly is enabled. MPSTE-3554