Skip Navigation

Digital Connect 22.12 Release Notes

Release Identification

Release Version Type (Version, Update, or Patch) Date Approved by Description of Change
22.12 Version December 2022

 

Software updates

Enhancements

Digital Connect introduces the following enhancements:

  • Co-located Airports
  • Eligibilities validation mutation rule 

Defect fixes

Digital Connect introduces the following defect fixes as part of this release:

  • Error response containing class and line information from the stack trace
  • Error on second purchase call in Modify Trip Options flow

Enhancements

Co-located Airports

Digital Connect introduces the ability for airlines to support co-located airports (sister airports) that allow certain cities to be considered/allowed for rebooking because of their close proximity. This benefits the airlines in scenarios when a reservation is IROP-affected, and when a promotion code applies to the reservation as filed in the downline rules processor. It also gives the passengers more flexibility to choose their departure or arrival airport based on currently configured DC rules, while disallowing them to abuse waivers that are not desired by the airline.

The enhancement applies to the Change Itinerary flow (MYB:CI)

Prerequisites:

  • DC requires the downline rules processor to return co-located airports in ProcessEligibilityRules response
  • Co-located airports need to be correctly set up
  • The MYB:CI flow must be enabled

Limitations:

After an IROP exchange the co-located airports, exchange will no longer be available as the itinerary will become multi-city.

 

Eligibilities validation mutation rule

Digital Connect introduces additional mutation rules that validate the eligibility of a given PNR and disables the opportunity to enter the post booking flow if there are no eligibility rules that apply to that PNR.

This change applies to the Exchange and Cancel and Refund flows.

Prerequisites:

None.

Limitations:

None.

Defect fixes

Error response containing class and line information from the stack trace

Sabre Tracking #:

DC-14909

Customer Tracking #:

n/a

Description:

When returning an error, the DC OTA_Cancel service response contained redundant data.

Resolution:

We modified the method of creating error messages not to include unnecessary information.

 

Error on second purchase call in Modify Trip Options flow

Sabre Tracking #:

DC-14250

Customer Tracking #:

n/a

Description:

Upon repeating a purchase call in Modify Trip Options flow, in scenarios involving refunds, Digital Connect tried to refund EMDs that were already refunded in the previous call, returning an “errorAerMtoAncillaryRefund” error in the pnr/mto/purchase service response.

Resolution:

We have implemented changes to the series of steps performed as part of the MTO flow in such scenarios to resolve this issue.