Digital Connect 22.09 Release Notes

Release Identification

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

 

 Software updated

Enhancements

Digital Connect introduces the following enhancements:

  • Ability to override refund to return to Original Form of Payment (OFOP)
  • Codeshare Ancillary Reserving Error resolution
  • Support for Apple Pay in Multiple Forms of Payment (MFOP)
  • Returning information about remaining seats in Air Search response during Exchange Shopping
  • Ancillary price discrepancy

Defect fixes

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

  • PNR with free paid seats not calculated to the total
  • Schema validation failure for ProcessEligibilityRulesRQ
  • Incorrect flight information (FLIFO) retrieval
  • Passenger email update issue
  • Unsuccessful Velocity signup

Enhancements

Ability to override refund to return to Original Form of Payment (OFOP)

Digital Connect introduces a new configuration that allows full refunds to the originally used Form of Payment (FOP), as opposed to the FOP filed in ATPCO that has been used before. This enables the airlines to offer more flexibility in defining where the refund should be allocated. The override applies to Adult, Child, and Infant passenger types for PNRs with and without schedule changes. The enhancement only applies when conditions are met, as defined in the SSRCM rules processor. If SSRCM returns both the FOP and travel bank in its return override list, Digital Connect will prioritize the original FOP and classify the travel bank return as an alternate refund target. Single and multiple forms of payment are supported as part of this enhancement.

Applies to the Cancel and Refund flow (MYB:CR)

Request changes

Scenario 1:
{"confirmed":true,"selectedRefundTarget":"OriginalFop"}

Scenario 2:
{"confirmed":true,"selectedRefundTarget":"TravelBank"}

Response changes

     "alternateRefundTargets": [
        {
            "@type": "TRAVEL_BANK",
            "@id": "8",
            "refund": {
                "paymentCode": "BT",
                "paymentType": "TRAVEL_BANK",
                "price": {
                    "alternatives": [
                        [
                            {
                                "amount": 590.42,
                                "currency": "USD"
                            }
                        ]
                    ]
                }
            },
            "documentRefs": [
                {
                    "@ref": "1"
                },
                {
                    "@ref": "3"
                },
                {
                    "@ref": "5"
                },
                {
                    "@ref": "6"
                }
            ]
        }
    ]
}

Prerequisites

The Auto Exchange and Refund service (AER) needs to support refunding using the original form of payment (OFOP).

Limitations

Works only the FOPs supported by the airline and does not apply to cash and cheque payments.

Codeshare Ancillary Reserving Error resolution

Digital Connect introduces a code enhancement that resolves an error that occurred when passengers were booking ancillaries on codeshare flights. During ancillary purchase, an ancillary reserving error was displayed. The payment site displayed the payment as complete and the passenger could see the amount of charge on the confirmation page, however, due to the ancillary error, payments were authorized but not completed. We resolved the issue by updating DC code to skip the booking class condition check for codeshare flights and proceed to add coupon data.

Prerequisites

None.

Limitations

None.

Support for Apple Pay in Multiple Forms of Payment (MFOP)

Digital Connect expands the Multiple Forms of Payment functionality to allow airlines to include Apple Pay as MFOP in the B2C Shop and Book workflow. The Apple Pay form of payment has been added as part of DC 22.07 release.

Insurance is available for transactions in which the airline is the Merchant of Record (MoR). The following MFOP are supported:

  • Loyalty Points (LP) + ApplePay (AP) - including reversal for points if AP fails
  • Travel Bank (BT) + ApplePay (AP) - including reversal for points if AP fails
  • ApplePay (AP) + Credit Card (CC) - no reversal
  • ApplePay (AP) + 3DS - no reversal

Prerequisites

text

Limitations

  • Alternate Forms of Payment (AFOP), such as Gift Card, Polzi, PayPal, and ZIP are not supported as MFOP and are limited to a Single Form of Payment
  • B2C Book Now Pay Later (BNPL) flow is limited to SIngle Form of Payment
  • Post-booking flows are not currently supported

Returning information about remaining seats in Air Search response during Exchange Shopping

Digital Connect introduces an enhancement that allows returning information about the seats remaining for a particular offer in the Exchange flow. Before its introduction, DC has only returned this information when the Low Fare Search (IBF) has been used in the Exchange flow:

"seatsRemaining": {
        "count": 9,
        "lowAvailability": false,

This information has been missing if an airline had a premium "TKT_ExchangeShopping" product enabled. DC Exchange Shopping response did not return the low availability parameter, therefore to maintain consistency between the contract and DC response, a configuration defining the value for low availability parameter (Boolean) has been added on the DC side.
If the value is not configured and is equal to empty, then the "lowAvailability" parameter must be set to false.

Examples

POST /pnr/exchange/products/air/search

"bundledOffers": [
        {
            "shoppingBasketHashCode": -1864916856,
            "brandId": "QP",
            "soldout": false,
            "bundlePrice": {},
            "availableObFees": [],
            "seatsRemaining": {
                "count": 0,
                "lowAvailability": false
            },

ExchangeShoppingRS

<Fare brand="QP" brandingProgram="206373" mixedBrands="false" passengersInDifferentCabins="false" postCalcIndex="1" requireSplitPNR="false" valid="true">
	<ReservationSegmentDetails segmentNumber="1">
		<PassengerBookingDetails bookingClass="Q" brand="QP" brandingProgram="206373" cabin="Y" documentNumber="XXXXXXXXX5851" fareBasis="QLEQPZ0B" meal="B" seatsRemaining="9">

Prerequisites

None.

Limitations

None.

Ancillary price discrepancy

Digital Connect introduces an enhancement that resolves an issue with ancillary price discrepancy between DC and its downline. The reason behind that discrepancy was the lack of mapping of the required field sent to the downline in getAncillaryOffers request. We have configured Digital Connect to pass the ticket reference number and the name reference number to downline in getAncillaryOffers request.

The enhancement applies to the Modify Trip Options (MYB:MTO) flow.

Prerequisites

None.

Limitations

None.

Defect fixes

PNR with free paid seats not calculated to the total

Customer tracking #:

06160356

Sabre tracking #:

DC-14216

Description:

When in an itinerary reservation with a free seat a passenger attempted to exchange for a paid seat, the seat price was not calculated into the total price. After completing the purchase, the seat remained unpaid.

Resolution:

Digital Connect code was modified to check for paid seats during exchange to include its cost in the total amount

Schema validation failure for ProcessEligibilityRulesRQ

Customer tracking #:

-

Sabre tracking #:

DC-15242

Description:

There was a schema validation error occurring during PNR retrieval for ProcessEligibilityRules request when the PNR contained a WR status (removed) segment. This has been caused by an incorrect request being sent when retrieving PNR eligibilities.

Resolution:

The syncGetResSegmentIdsToEligibilitySegmentIds method has been modified to resolve the issue.

Incorrect flight information (FLIFO) retrieval

Customer tracking #:

06095144

Sabre tracking #:

DC-14150

Description:

For flights with stopovers that have one of the portions cancelled, the service products/air/flight/status did not read the flight information (FLIFO) correctly.

Resolution:

A new configuration has been added that enables DC to read entry identifier and text information from a downline service and expose the relevant information to the Point of Sale.

Passenger email update issue

Customer tracking #:

06487814

Sabre tracking #:

DC-15497

Description:

There was an issue occurring when a passenger tried to update their email address after completing a booking. If a top-level domain has been used instead of the email address used to book the flight, Digital Connect returned an error message.

Resolution:

The PassengerInfo.java class used 'EmailFieldValidator' for email validation. The 'EmailFieldValidator' uses default regexp, not from SAT configuration.

We have resolved the issue by using 'TextFieldValidator' which uses SAT configuration regexp instead of 'EmailFieldValidator'.

Unsuccessful Velocity signup

Customer tracking #:

06487841

Sabre tracking #:

DC-15496

Description:

There was an issue occurring when a passenger attempted to join Velocity Frequent Flyer by checking the checkbox on the passenger page. Digital Connect /purchase API returned an "accountCreationError" message when a top-level domain email longer than six characters was used.

Resolution:

The PassengerInfo.java class used 'EmailFieldValidator' for email validation. The 'EmailFieldValidator' uses default regexp, not from SAT configuration.

We have resolved the issue by using 'TextFieldValidator' which uses SAT configuration regexp instead of 'EmailFieldValidator'.