Digital Connect Check-In 23.01 Release Notes
Release Identification
| Release Version | Type (Version, Update, or Patch) | Date | Approved by | Description of Change |
|---|---|---|---|---|
| 23.01 | Version | 22 Jan 2023 |
Piotr Gorski |
Software updated |
Features
Digital Connect Check-In introduces new features and enhancements in the following areas:
- Enhance /dcci/reservation/create with 7PS Command
- Intelligent /baggage/checkin
- Handle Price Baggage Cache as Optional When Price Baggage Data is not Neccessary
- Modification of SSR DOCO (Redress/Known Traveler Number and Visa): Error Handling
- [SSDSSCIOS-6871] Workaround for the CKI Issue with DOCS Requirements for INF Passenger Type
Defects
The following Digital Connect Check-In defects have been fixed for this release.
- [BAGS][PDC flight] Error Occurs While Trying to Update the Bag for the Reservation with PDC Flight
- Checkin BP Behavior Modified / Discussed with LA Directly
- Incorrect Format of Frequent Flier Information Sent by Check-in App to Ancs's GAO
- Passenger Details Refresh Return Array of Checked Baggage
The following sections explain more details about the new items.
Enhance /dcci/reservation/create with 7PS Command
The purpose of this feature is to allow agents to create a dummy reservation and issue a gate pass for a non-traveling person who needs to accompany a passenger to the gate.
Now, Digital Connect Check-In supports creation of a PNR for the accompanying person/ people by adding 7PS entry in the dcci/reservation/create service.
Prerequisites
The airline must include the priority code for gate pass in the PRC table, to use the Gate Pass in Interact. The airline must have a dedicated Gate Pass pseudo flight. The ASA Table must be updated by the carrier.
Limitations
This feature is available only for agent application. It is not available for self-service applications.
Configuration
None
Intelligent /baggage/checkin
Digital Connect Check-In has extended the POST /baggage/checkin service to perform check-in of baggage items based on the results of /baggage/price and /baggage/book services.
To use this functionality, the client must call POST /baggage/checkin either with an empty body or a body with bagTagOption.
Prerequisites
None
Limitations
None
Configuration
None
Handle Price Baggage Cache as Optional When Price Baggage Data is not Neccessary
Digital Connect Check-In has improved the dcci/baggage/checkin service and does not log an error message related to a missing cached object when the PriceBaggage cache is optional.
Prerequisites
None
Limitations
None
Configuration
N/A
Modification of SSR DOCO (Redress/Known Traveler Number and Visa): Error Handling
In line with IATA requirements, the following fields are mandatory when the users are adding/ modifying the passenger information:
- Country code in Redress and in Known Traveler Number
- Visa Expiry date
In accordance with these requirements, SSCI has made these fields mandatory. Now, when the DOCS sent to SSCI do not contain this mandatory data and SSCI returns an error, Digital Connect Check-In provides the user with a dedicated error code COUNTRY_CODE_REQUIRED or EXPIRY_DATE_REQUIRED instead of a generic one.
Prerequisites
None
Limitations
None
Configuration
| Property Name | Description | Example Value |
Data Type |
|---|---|---|---|
| s4ci.feature.document.update.specificErrorStatuses.enabled | If set to true, then new error status (COUNTRY_CODE_REQUIRED, EXPIRY_DATE_REQUIRED) will be returned while updating the redress, known traveler, visa documents. default:false |
false |
Boolean |
[SSDSSCIOS-6871] Workaround for the CKI Issue with DOCS Requirements for INF Passenger Type
In some cases, for an infant passenger, the CKI does not return DOCS requirements for check-in in the RequiredInfoSumList structure, in the POST /v3/cki/passenger/details response.
In order to minimize impact on the client, Digital Connect Check-In has prepared a following temporary solution:
When s4ci.feature.document.infantDocsCheck.enabled is turned ON then
- Check the PassengerItinerary level RequiredInfoList first and then check if the travel DOCS are required (DOCS/INF); if yes, then mark the infant as ineligible PASSENGER_DOES_NOT_HAVE_REQUIRED_IDENTITY_DOCUMENTS
- Otherwise, check if the given infant has no DOCS that is already provided and a TIMATIC check is required. The associated passenger is required to provide travel DOCS (DOCS)and then mark the infant as ineligible PASSENGER_DOES_NOT_HAVE_REQUIRED_IDENTITY_DOCUMENTS
Prerequisites
None
Limitations
None
Configuration
| Property Name | Description | Example Value |
Data Type |
|---|---|---|---|
| s4ci.feature.document.infantDocsCheck.enabled |
Checks the PassengerItinerary level RequiredInfoList first and checks if the travel DOCS are required (DOCS/INF) if yes then mark infant as ineligible PASSENGER_DOES_NOT_HAVE_REQUIRED_IDENTITY_DOCUMENTS. Otherwise check if given infant has no DOCS already provided and TIMATIC check is required and associated passenger is required to provide travel DOCS (DOCS) then mark infant as ineligible PASSENGER_DOES_NOT_HAVE_REQUIRED_IDENTITY_DOCUMENTS |
false |
Boolean |
[BAGS][PDC flight] Error Occurs While Trying to Update the Bag for the Reservation with PDC Flight
|
Customer Tracking #: N/A |
Sabre Tracking #: CSSDC- 2605 |
|
Description: The dcci/baggage/book failed during the weight update of the already checked-in baggage, when the first segment was in PDC status. |
|
|
Resolution: Now, dcci /baggage/book service allows updating the weight of an already checked-in baggage, when the first segment in the reservation is in PDC status. |
|
|
Programs/Modules Affected: dcci/baggage/book |
|
Checkin BP Behavior Modified / Discussed with LA Directly
|
Customer Tracking #: N/A |
Sabre Tracking #: CSSDC-2612 |
|
Description: The customer was not getting the object boardingPass for standby passengers in the passenger details response. It was due to Digital Connect Check-In changing the behavior of the configuration s4ci.feature.passengerDetails.paxSegStatus.enabled. |
|
|
Resolution: Digital Connect Check-In reverted the changes to the configuration s4ci.feature.passengerDetails.paxSegStatus.enabled and Digital Connect Check-In added a new configuration s4ci.feature.passengerDetails.directCheckedInStatus.enabled to decide if the check-in flag is populated directly from CKI, otherwise it is based on Digital Connect Check-In logic. |
|
|
Programs/Modules Affected: dcci/passenger/details |
|
Incorrect Format of Frequent Flier Information Sent by Check-in App to Ancs's GAO
|
Customer Tracking #: N/A |
Sabre Tracking #: CSSDC- 2622 |
|
Description: Loyalty details contain invalid number sent in GetAncillaryOffersRQ when added incorrectly. |
|
|
Resolution: The member id must be cleaned when added incorrectly. |
|
|
Programs/Modules Affected: dcci/passenger/details |
|
Passenger Details Refresh Return Array of Checked Baggage
|
Customer Tracking #: N/A |
Sabre Tracking #: CSSDC- 2626 |
|
Description: Digital Connect Check-In POST /baggage/book and /passenger/details/refresh returned information about the checked-in baggage and linked air extras that contained the same air extras. |
|
|
Resolution: Now, Digital Connect Check-In POST /baggage/book and /passenger/details/refresh returns only information about the checked-in baggage and does not return linked air extras containing the same air extras. |
|
|
Programs/Modules Affected: post/baggage/book and /passenger/details/refresh |
|