Digital Connect Check-In 21.09 Release Notes

Release Identification

Release Version	Type (Version, Update, or Patch)	Date	Approved by	Description of Change
21.09	Version	24 Sep 2021	Grzegorz Kurek, Rafal Holub	Software updated

Release Version

Type (Version, Update, or Patch)

Date

Approved by

Description of Change

21.09

Version

24 Sep 2021

Grzegorz Kurek,

Rafal Holub

Software updated

Features

Digital Connect Check-In introduces new features and enhancements in the following areas:

Mandate – UAE Secure Boarding
Support 3DS 2.0 in Payment Process – New Requirements
Support for Multi-Segment Boarding Passes
Store Baggage Weight and send it in UpdateReservation
Support Infant Added as an Edit Code
Enhance Segment Selection Process

Defects

The following Digital Connect Check-In defects have been fixed for this release.

G3 G2S Cutover DW Unable to Change Seat – “Error Occurred While Loading Seat Map”
G3D0 DCCI ERR.DCCI.APP.INTERNAL_EROOR | pnrlookup Group Booking
DXCI 2.6 PROD

The following sections explain more details about the new items.

Mandate – UAE Secure Boarding

Digital Connect Check-In will enhance the service providing passenger details with the additional information about passenger boarding clearance. This feature will allow to skip scanning of the passenger's travel document and will no longer be required at the time of boarding. The Boarding status will be passed as the new eligibility and, based on this status, the passenger will be allowed to board or else.

Return in Passenger Details Boarding Clearance Information

Digital Connect Check-In has enhanced the service that provides passenger details with additional information, about passenger boarding clearance. This additional information is returned as edit code with the clearance status.

Prerequisites

None

Limitations

None

Configuration

Property Name	Description	Example Value	Data Type
se.adapter.s4ci.configuration.reservationConfiguration.retrieveDetailedInformationEnabled	Specifies whether SSRs, OSIs, Remarks, EditCodes must be retrieved and exposed. Default is [false]	False	Boolean

Support 3DS 2.0 in Payment Process – New Requirements

3D Secure 2.0 is the new authentication protocol for online card payments and is designed to improve the previous version. Digital Connect Check-In already supports the new version of 3D Secure, and this project covers further improvements of 3DS 2.0.

3DS 2.0 – Provide iFrame Parameters

In 3D Secure 2, some issuers will need the customer’s device fingerprint before authenticating the payment. In this case, a hidden inline frame - IFrame - is used to send the device fingerprint request to a card issuer thus allowing the bank to perform the device fingerprinting at the background.
Until recently, the standard 1x1 iframe parameters were used to provide UI with the information on the size of iframe that must be created. Now, the HEIGHT and WIDTH parameters are introduced in addition, to support more values of the iframe size.

Prerequisites

None

Limitations

None

Configuration

Property Name	Description	Example Value	Data Type
se.adapter.s4ci.configuration.paymentConfiguration.remotePayment.additionalDetails = "WIDTH,HEIGHT"	Indicates remote payment redirect additional details which must be retrieved from PWS for example, WIDTH, HEIGHT Default is blank (for backward compatibility).		List <String>

3DS 2.0 – Provide Source as DCCI Transaction Identifier

The payment service cannot support both check-in and eCommerce paths of 3DS as they cannot identify the source of the transaction and, send it down the correct path.
To determine if the user is redirected to 3DS, Payment requires the source id to identify the source of the transaction.

Prerequisites

None

Limitations

None

Configuration

Property Name	Description	Example Value	Data Type
se.adapter.s4ci.configuration.paymentConfiguration.sourceIdentifier	Indicates which system is performing payment (Is used in payment authorization). For instance, for check-in purposes, it will typically be DCCI. Default is [DCCI]	DCCI	String

Support for Multi-Segment Boarding Passes

Currently, when a passenger is checked in on more than one flight, the airlines must print a boarding pass for each flight. Airlines would like to use multi-segment boarding passes in such a scenario. This will allow one boarding pass to be used for up to three different flights processed in the same check-in transaction.

Prerequisites

None

Limitations

None

Configuration

Property Name	Description	Example Value	Data Type
s4ci.feature.boardingPass.multiSegmentEnabled	Determines whether multi-segment boarding pass flag is sent to SSCI services. Default is [false]	True	Boolean

Store Baggage Weight and send it in UpdateReservation

Digital Connect Check-In must store the baggage weight and send it in UpdateReservationRQ to ANCS, to enable correct calculation of the overweight baggage charges.

Prerequisites

None

Limitations

None

Configuration

Property Name	Description	Example Value	Data Type
s4ci.feature.baggage.book.optimization.enabled = (true/false)	Determines whether calls to SSCI /passenger/details service should be optimized or not. Default is [false]	True	Boolean

Support Infant Added as an Edit Code

Digital Connect Check-In supports INF passenger type when an infant has a booking. In few cases, Airlines allow an INF passenger to travel without a PNR. In such cases, INF is added at the time of check-in as an edit code. Currently, Digital Connect Check-In is not able to fully support INF as edit code and does not support adding DOCS to the edit. When this enhancement is implemented, Digital Connect Check-In will be able to support INF passenger without a PNR but added at the time of check-in as an edit.

Prerequisites

None

Limitations

None

Configuration

None

Enhance Segment Selection Process

Digital Connect Check-In uses a logic to select segments which must be sent to CBF, to correctly calculate baggage fees. This logic will now be enhanced to cover more scenarios including connecting flights operated by hosted carriers and other airlines.

Enhance segment selection feature in baggage/ Price

Digital Connect Check-In has a logic to select segments to be sent to CBF. This logic will now be enhanced to cover more scenarios.

Prerequisites

None

Limitations

None

Configuration

Property Name	Description	Example Value	Data Type
s4ci.feature.pricingConfiguration.additionalEligibleSegmentsFromPnr.enabled	Enables enriching PriceBaggageRQ with segments retrieved from PNR GetReservation	False	Boolean

Enhance segment selection feature in passenger/details

Digital Connect Check-In must enhance passenger details service to return the connecting segments when they are returned by SSCI service cki/passenger/details.
Currently, when there is OA segment in the connection, Digital Connect Check-In does not return it in case if there is no bag route. The reason for it is the lack of full data about the flight (for example, dates) making it impossible for Digital Connect Check-In to build itinerary.

Prerequisites

None

Limitations

None

Configuration

Property Name	Description	Example Value	Data Type
s4ci.feature.passengerDetails.returnedSegmentsRules = PNR_BASED	Defines a set of rules used to populate segments that are returned in the reservation. When set to ALL then all active segments from the PNR are returned. When set to PNR_BASED then segments from the PNR starting with a first hosted segment are returned. Error is returned when there is no hosted segment found. When set to SSCI_BASED then check-in related segments are returned. Error is returned when there is no hosted segment found.	ALL, PNR_BASED, SSCI_BASED	List <String>

Property Name

Description

Example
Value

Data
Type

s4ci.feature.passengerDetails.returnedSegmentsRules = PNR_BASED

Defines a set of rules used to populate segments that are returned in the reservation. When set to ALL then all active segments from the PNR are returned. When set to PNR_BASED then segments from the PNR starting with a first hosted segment are returned. Error is returned when there is no hosted segment found. When set to SSCI_BASED then check-in related segments are returned. Error is returned when there is no hosted segment found.

ALL, PNR_BASED, SSCI_BASED

List <String>

G3 G2S Cutover DW Unable to Change Seat – “Error Occurred While Loading Seat Map”

Customer Tracking #:

N/A

Sabre Tracking #:

CSSDC-2134

Description:

The agent received an error while trying to change the seat in DW.

Resolution:

Digital Connect Check-In returns partial status for each segment rather than an error message when one of the seatmap cannot be retrieved from the downline service.

Programs/Modules Affected:

None

G3D0 DCCI ERR.DCCI.APP.INTERNAL_EROOR | pnrlookup Group Booking

Customer Tracking #:

N/A

Sabre Tracking #:

CSSDC-2135

Description:

Digital Connect Check-In receives ERR.DCCI.APP.INTERNAL_ERROR while retrieving the PNR RGMPWY (Group Booking).

Resolution:

The group reservation error handling for unsupported IATCI flow has been unified with self-service flow. When the first name is not provided, then in both cases Digital Connect Check-In returns ERR.DCCI.PASSENGER_RETRIEVAL_OPTIONS_MISMATCH.

Programs/Modules Affected:

None

DXCI 2.6 PROD

Customer Tracking #:

N/A

Sabre Tracking #:

CSSDC-2148

Description:

The passengers could not proceed with online check-in due to following error : ERR.DCCI.INTERNAL.SERVICE_UNAVAILABLE.CONNECTIVITY
The error was caused by unnecessarily sending SequenceNumber in Ancillary to GetSeatMap service.

Resolution:

SequenceNumber in Ancillary is being removed before sending request to GeatSeatMap service.

Programs/Modules Affected:

None