Digital Connect Check-In 21.05 Release Notes
Release Identification
Release Version | Type (Version, Update, or Patch) | Date | Approved by | Description of Change |
---|---|---|---|---|
21.05 | Version | 21 May 2021 |
Grzegorz Kurek, Rafal Holub |
Software updated |
Features
Digital Connect Check-In introduces new features and enhancements in the following areas:
- GOL – Installments
- Search by FOID - Enhancement
- Grouping Segments in /passenger/details
Defects
The following Digital Connect Check-In defects have been fixed for this release.
- Business Error: Unable to Build Location Specific Date Time. Missing Location Configuration for DSS
- Unable to Retrieve Passenger on OA flight
- DCCI using Invalid PCCs for Baggage Booking
The following sections explain more details about the new items.
GOL – Installments
Retrieve installment options before payment
Passenger paying for their pending AEs can verify if their payment can be split into several installments. Payment in installments is optional; the passenger has an option to request to process their payment in this method.
Digital Connect Check-In will share information on the available installment options for passenger based on the AEs and can be paid accordingly. The following options include all the important details based on which the passenger must be able to decide on an appropriate installment option:
- Total payment amount
- Installment amount
- Interest amount
- Interest rate
- Additional payments (e.g. taxes)
Prerequisites
None
Limitations
None
Configuration
None
Support installments in /dcci/pay service
Passengers while paying for the ancillaries with their credit card have an option to pay in installments instead of paying entirely.
When the passenger retrieves the different installment options and decides on a particular one then this information must be provided to /dcci/pay service, to complete the transaction.
Prerequisites
Installment options must be retrieved before calling /dcci/pay
Limitations
The passenger chosen for AEs must be the same passenger for whom the installment payment option is calculated, else the request will be rejected.
Also, the credit card through which the passenger will pay must be same as the one that is used to calculate the installment options. Otherwise, the request will be rejected.
Configuration
None
Search by FOID - Enhancement
Return FOID in /passenger/details Response
DCCI /passenger/details allows search of the reservation using different criteria. One among them is FOID.
The FOID must be included in the retrieved results as it makes it easier to check the passenger who requested for the document.
This functionality will work whenever /passenger/details response is returned. And, both unique and non-unique lookup will be supported.
Prerequisites
None
Limitations
None
Configuration
Property Name | Description | Example Value |
Data Type |
---|---|---|---|
s4ci.feature.passengerDetails.requestedSearchCriteria.enabled |
Determines whether the response must be enhanced with the requested search criteria info (for example, whether the passenger fulfills the requested search criteria). This applies to cases where only basic reservation data is returned. Default is [False] |
True |
Boolean |
Grouping Segments/ Passenger/ Details
Grouping Segments in DCCI/ Passenger/ Details
With Digital Connect Check-In enabling a functionality to check-in passengers on the requested segments, the passengers can be advised to group their segments in their reservation.
And, the grouped segments should follow a logic which considers :
- Connectivity between segments
- Information about return flights
Segments must be grouped using the following rules:
- Segments must be grouped together if they are connected through OB/IB edit codes (connecting segments).
- Return flights (RT EditCode) must break the connectivity of the segments.
Prerequisites
None
Limitations
None
Configuration
Property Name | Description | Example Value |
Data Type |
---|---|---|---|
s4ci.feature.passengerDetails.segmentGroups.enabled | Determines whether groups of segments should be returned in reservation. Default is [false] |
False |
Boolean |
Business Error: Unable to Build Location Specific Date Time. Missing Location Configuration for DSS
Customer Tracking #: Case ID 05459560 |
Sabre Tracking #: CSSDC-1901 |
Description: Customer reported that they are unable to show passenger details in Digital Workspace as they are receiving error message - Business error: Unable to build location specific date Time. Missing location configuration for DSS, while selecting passenger details. |
|
Resolution: Digital Connect Check-In was updated to fetch location data from additional sources. |
|
Programs/Modules Affected: /dcci/passenger/details |
Unable to Retrieve Passenger on OA flight
Customer Tracking #: Case ID: 05361403 |
Sabre Tracking #: CSSDC-1974 |
Description: Customer reported that while retrieving Pax by PNR or last name, receiving error message and unable to proceed with Pax check-in. |
|
Resolution: OA flights support was improved for rare cases, where some itinerary data is missing in Sabre check-in services. |
|
Programs/Modules Affected: /dcci/passenger/checkin |
DCCI using Invalid PCCs for Baggage Booking
Customer Tracking #: N/A |
Sabre Tracking #: CSSDC- 1982 |
Description: Baggage pricing and booking was performed in invalid or default PCC. |
|
Resolution: Baggage book service was updated to create AEs in correct PCC by performing context change before the booking operation. |
|
Programs/Modules Affected: /dcci/baggage/book |