Release Identification

Release Version	Type (Version, Update, or Patch)	Date	Approved by	Description of Change
22.01	Version	December 2021	Sebastian Santos	Software updated

Enhancements

Digital Connect introduces the following enhancements:

• Logging in with email address
• Dynamic control over Air Search response
• Adding Other Airline (OA) operating flight number
• Adding Other Airline (OA) record locator in the Purchase response

 

Enhancements

Logging in with email address

This Digital Connect enhancement allows passengers to log in to their Frequent Flyers account using their email address in addition to the Frequent Flyer number. Digital Connect makes an external authentication request to validate the Frequent Flyer number or email and log the passenger into the application. This enhancement applies to every instance of the logon component being used. The passenger provides their Frequent Flyer number or email in the login field along with their password, and DC validates the credentials with an OKTA call without storing the passenger's password in the application.

The enhancement applies to the following booking flows:

• B2C
• RBE
• MTO
• Exchange
• FFU

Request and response examples

Prerequisites

• Airlines need to have both the frequent flyer number and email address enabled as form of user identification for login.
• This enhancement needs to be enabled by configuration.

Limitations

None.

 

Dynamic control over Air Search response

Digital Connect introduces functionality that allows airlines to dynamically control the air search response for "bundled" and "unbundled" offers. The new property splitByItineraryPart has been added under the additionalParameters object. Setting this property to a "true" or "false" value takes precedence over the existing splitByItineraryPart configurations and mutation rules for the current request flow. If the property is set to "null" or omitted, the request split by itinerary part logic falls back to configuration and mutation rules.

The functionality applies to the following flows:

• B2C air search
• Redemption air search
• Context shopping

Request example:

{
        "cabinClass" :   "Economy" ,
        "awardBooking" :   false ,
        "searchType" :   "BRANDED" ,
        "additionalParameters" : {
                "splitByItineraryPart" :   true
        },
        "promoCodes" : [],
        "itineraryParts" : [
                {
                        "from" : {
                                "code" :   "AUH" ,
                                "useNearbyLocations" :   false
                        },
                        "to" : {
                                "code" :   "LHR" ,
                                "useNearbyLocations" :   false
                        },
                        "when" : {
                                "date" :   "2021-10-06"
                        }
                }
        ],
        "passengers" : {
                "ADT" :   1
        }
}

 

Prerequisites

None.

Limitations

The feature is applicable to: 

• Branded fares
• Flexible calendar
• Calendar 30

Matrix search type always returns a "bundled" response. If splitByItineraryPart is set to 'true' in the request for Matrix search, still a "bundled" response is returned. No warnings are displayed.

 

Adding Other Airline (OA) operating flight number

As a minor enhancement in this version, Digital Connect is returning Other Airline operating flight numbers and operating airline codes in various DC services. Before this enhancement, Digital Connect only returned the flight number and airline code with no reference to the actual operating flight number or operating airline.

Following is the list of services that return the additional data:

• B2C flow, B2C-BNPL and RBE flow
• products/air/search
• products/air (POST and GET)
• ancillaries
• seats
• calendar 
• products (PUT and GET)
• purchase

Out of scope:

• GET/ pnr response
• GET /products/cart
• Post booking flows
• Products/air/metasearch

Examples

OperatingFlightNumber as part of flight:

"flight": {
"flightNumber": 7706,
"operatingFlightNumber": 7681,
"airlineCode": "AR",
"operatingAirlineCode": "G3",
"stopAirports": [],
"advisories": []
}

Prerequisites

None.

Limitations

None.

 

Adding Other Airline (OA) record locator in the Purchase response

Before the introduction of this enhancement, Digital Connect only returned hosted airline record locator. The enhancement returns Other Airline (OA) and codeshare segments record locator under segment in the purchase response. This allows passengers to use the record locator to check their itinerary or perform an online check-in using the Other Airline (OAL) system. Being able to identify their operating carrier also aids passengers in navigating through airports (e.g. to find the correct check-in desk.)

Digital Connect returns the new field 'otherArilineRecordLocator' under segment in the Purchase service response. In the case of an interline flight, the service is mapping 'AirlineRefId' under the segment element in GetReservation response. In the case of a codeshare segment, the service is mapping 'CodeSahreOperatingRecordLocator' under segment in the GetReservation response. The OA record locator is obtained from the other airline host with a TTY request.

Applies to the following flows:

• B2C flow, B2C-BNPL and RBE flow

Out of scope:

• Post-booking flows
• GET /pnr response

Examples

"segments": [
   {
      "@type": "Segment",
      "cabinClass": "Economy",
      "equipment": "E90",
      "otherAirlineRecordLocator": "AXANMT"
   }
]

 Codeshare segment example:

Prerequisites

None.

Limitations

None.