Improvements and Bug Fixes

• When a policy has one or more Para Service or Booking Purposes as infraction criteria, multiple suspension records are added per client suspension. In addition, if adding funding source, it could be more. To improve this, one suspension record would include all this information and be returned with the ReturnSuspension service as a single JSON object.

  • When responding to the ReturnSuspensions request, the Para Service and Booking Purpose information will be ignored if the suspension mode is set to Basic.

• When sending a request to Trapeze6 (TP6) to cancel future trips, it should act based on the suspension mode. A cancellation request should only be sent if the mode is turned on.

For non-point based percent policies, if the minimum requirement is set to Infractions, Min Infractions and Threshold Value fields will essentially be the same. Therefore, the following updates were made:

• Threshold Value field was hidden when adding a policy/warning stage/suspension phase.
• Threshold Value field was disabled when editing a policy/warning stage/suspension phase.

• Modifying Min Infractions in the above scenario should also update Infraction Threshold parameter to have the same value.

Fixed an issue in a Short Fare policy, where when a warning letter was sent and the client prepayment method was changed, the Service Infractions Service Shell received the request, but did not forward it to the Tp6 Service Shell.

Fixed an issue regarding a policy with multiple warning/appeal stages. When a stage was removed, the order of phases in the remaining stages became unorganized and was not in the intended sequence.

Fixed an issue where when merging all letters in a phase, the oldest letter was picked instead of the most recent.