Skip to main content

Digital Connect 21.10 Release Notes

Release Identification

Release Version Type (Version, Update, or Patch) Date Approved by Description of Change
21.10 Version September 2021

Rafał Hołub

Software updated

Enhancements

Digital Connect introduces the following enhancements:

  • Performance improvements and workflow changes in MTO and Edit passenger Exchange
  • 3DS 2.0 - defined iframe size
  • Supplier Transaction ID in VCR and EMD
  • Multiple exchanges
  • EMD as Form of Payment

Defects

The following defects have been fixed as part of this release:

  • Incorrect installment interest format
  • Query Ancillaries connectivity issue - passenger type
  • Query Ancillaries connectivity issue - currency data

Enhancements

Performance improvements and workflow changes in MTO and Edit passenger Exchange.

The aim of this enhancement is to remove redundant downline calls to increase the performance of the MTO flow.

Previously, a single workflow has been used to retrieve a PNR and verify if changes were made which increased the number of unnecessary operations. There have not been any means to add Frequent Flyer data or Special Service Requests in the MTO flow – only the final purchase call allowed for such changes.

This enhancement introduces a new workflow that is called exclusively in the MTO flow. In the workflow, matchers have been added to check the data and open the PNR only if changes need to be introduced.

If any errors occur while updating the PNR fields, specific remarks are added related to the field that failed to update.

Prerequisites

None.

Limitations

None.

3DS 2.0 - defined iframe size

Digital Connect introduces an enhancement to the 3DS authentication process. When the payment response contains the INITIALIZEFRAME status, the iframe submitted by the POS has a size defined by the values in a newly introduced AdditionalDetails field. The Height and Width values may either be integer or have a value of 100% that will result in a full-screen iframe. In redirectHTML, the HTML form has an additional attribute - target="3DSecureform" that matches the name of the iframe used in the POS element. If the scenario when the iframe is not in use, the value will be target=_parent".

Prerequisites

None.

Limitations

None.

Supplier Transaction ID in VCR and EMD

As an enhancement to Digital Connect, the Supplier Transaction ID is included when issuing VCR and EMD.  Embedding the Supplier Transaction ID allows for correct matching of authorizations when the same credit card number is used in multiple transactions on the same day, and prevent leakage and/or misuse of airline/POS authorization codes. This enhancement applies to the following flows:

  • B2C
  • BNPL
  • MYB B2C BNPL

For new bookings, the Supplier Transaction ID is mapped into Sabre Command when VCR is issued. For the Post Booking flows, the values are mapped into the AER request parameter and Collect Misc Fee when VCR and EMD are issued respectively. The Supplier Transaction ID is acquired from the payment response. In case no ID is returned, Authorization Codes are mapped into VCR and EMD as before the enhancement.

Prerequisites

  • Payment needs to return TransactionID and SupplierTransactionID in PaymentRS

Limitations

None.

Configuration Keys

Original property name Description of changes Possible values Default value
gds.sabre.ticket.sendSupplierTransactionIdInTicketingCommand.enabled
Allow/disallow Supplier Transaction ID in ticketing command per payment true, false false

 

Multiple exchanges

Digital Connect 21.10 introduces an ability for consecutive exchanges and other post-booking operations, in order to give the customers a possibility to exchange their tickets even if their reservation has already been changed, went through an irregular operation or has been modified in the MTO flow. This enhancement applies to the following flows:

  • Manage Your Booking: Change Itinerary
  • Manage Your Booking: Cancel & Refund
  • Manage Your Booking: Modify Trip Options
Original booking B2C First Second Third Fourth Limitations
Scenario pax ancillaries seats
Ticket revenue (RT) domestic CL Not Flown  1 ADT no no Voluntary-same route (full exchange) Involuntary-same route (full exchange) Cancel & Refund    
Ticket revenue (RT) domestic CL Not Flown  1 ADT + 1CHD yes no Voluntary-same route (outbound exchange) Involuntary-same route (outbound exchange) Cancel & Refund    
Ticket revenue (RT) domestic CL Not Flown  3 ADT + 2CHD + 1INF yes yes Voluntary-same route (inbound exchange) Involuntary-same route (inbound exchange) Cancel & Refund    
Ticket revenue (RT) domestic CL Not Flown  3 ADT + 2CHD + 1INF yes yes Voluntary-same route (inbound exchange), skip ancillary selection  Involuntary-same route (inbound exchange), skip ancillary selection Cancel & Refund    
Ticket revenue (RT) connecting international Not Flown  1 ADT no no Voluntary-same route (full exchange) Involuntary-same route-connecting (full exchange) Cancel & Refund    
Ticket revenue (RT) connecting international Not Flown  1 ADT + 1CHD yes no Voluntary-same route (outbound exchange) Involuntary-same route- connecting (outbound exchange) Cancel & Refund    
Ticket revenue (RT) connecting international Not Flown  3 ADT + 2CHD + 1INF yes yes Voluntary-same route (inbound exchange) Involuntary-same route-connecting (inbound exchange) Cancel & Refund    
Ticket revenue (RT) connecting international Not Flown  3 ADT + 2CHD + 1INF yes yes Voluntary-same route (inbound exchange), skip ancillary selection  Involuntary-same route-connecting (inbound exchange), skip ancillary selection Cancel & Refund    
Ticket revenue (OW) Not Flown  1 ADT no no MTO-Add paid seat Involuntary-same route Voluntary-different route Cancel & Refund ExCS
Ticket revenue (OW) Not Flown  1 ADT + 1CHD yes no MTO-Add change paid seat Involuntary-same route Voluntary-different route Cancel & Refund ExCS
Ticket revenue (RT) Not Flown  1 ADT no no Involuntary-same route Involuntary-same route Cancel & Refund   ExCS

Limitations:

Out of the scope of this enhancement:

  • Multi-city trips
  • Redemption bookings
  • Multiple Forms of Refund
  • Multi-currency reservations
  • POS changes
  • GDS and OAL PNRs
  • Multiple active tickets for a single passenger 

The scenarios marked in the table are limited by Exchange Context Shopping.

 

EMD as Form of Payment

An enhancement introduced in Digital Connect 21.10 allows customers to use Electronic Miscellaneous Documents as a form of payment for new bookings and in the Post Booking flow. The EMDs can be used alongside other forms of payment (MFOP).

Prerequisites:

  • PNR must be created before using the EMD.
  • The EMD must have an OK status.

Limitations:

  • Flight promotions are not supported when using EMD as FOP.
  • Passenger name on the EMD must match the name on the VCR.
  • A maximum of 8 EMDs can be used as a form of payment.
  • MYB MTO flow, codeshare flights, loyalty bookings, and the use of interline EMDs are out of the scope of this feature.
  • Digital Connect does not validate the EMDs - all refundable documents can be used as payment.
  • Digital Connect does not validate currency changes in the document vs PNR.

Defects

Incorrect installment interest format

Customer Tracking #:

N/A

Sabre Tracking #:

DC-13109

Description:

Digital Connect was incorrectly passing the interest percentage, the UI was displaying 199% instead of 1.99%

Resolution:

A configuration "sat.payment.application.multiply.installmentInterest.oneHundred" has been implemented. When set to false, the percentage is displayed correctly.

 

Query Ancillaries connectivity issue - passenger type

Customer Tracking #:

05840785

Sabre Tracking #:

ASTR-26503

QueryAncillaries was throwing a connectivity error due to a schema error thrown by the Loyalty Conversion Service (LCS) service. The reason behind the error was that the QueryAncillaryConversionData request passed the passenger type as "ADT-1".

The Reference field obtained from GetReservation response was trimmed to a 3-character format to resolve a correct passenger type to the LCS, therefore sending "ADT" instead of "ADT-1" as passenger type.

 

Query Ancillaries connectivity issue - currency data

Customer Tracking #:

05850102

Sabre Tracking #:

DC-13349

Description:

QueryAncillaries was throwing a connectivity error due to a schema error thrown by the Loyalty Conversion Service (LCS). The reason behind the error was that the request did not contain currency data.

Resolution:

DC code has been adjusted to pick up the currency from the first available Priced Ancillary offer with an equivalent price. If none of the offers has an equivalent price, the first available offer with a price associated will be used.