Digital Connect Check-In 22.07 Release Notes
Release Identification
Release Version | Type (Version, Update, or Patch) | Date | Approved by | Description of Change |
---|---|---|---|---|
22.07 | Version | 22 Jul 2022 |
Piotr Gorski |
Software updated |
Features
Digital Connect Check-In introduces new features and enhancements in the following areas:
- Support New Gender UI and XI for Infants
- Provide Gender as a Code in DOCS
- Improvement for Enhanced Baggage Book Results
- Return Departure Airport in the Bag Tag Information
- Add Extra Request Validation for Pricing Baggage
- Bag Tag Details Default Values
- Device Config Schema Improvement
Defects
The following Digital Connect Check-In defects have been fixed for this release.
- DR – B6 not Getting Second Bag Free from DR Rule
- Passenger Details INTERNAL ERROR When First Flight in PDC
- LAD0 - PROD - DCCI Returns SUCCESS on Failed Offload with "/PR/ IN OFFLOAD ENTRY NOT APPLICABLE"
The following sections explain more details about the new items.
Support New Gender UI and XI for Infants
Now, besides Male and Female genders for infants, Digital Connect Check-In supports in passenger documents two new genders for this passenger type - Undisclosed and Unspecified.
Prerequisites
None
Limitations
None
Configuration
None
Provide Gender as a Code in DOCS
To enable clients to use their own gender translation Digital Connect Check-In can now provide gender as a code.
The client can decide how the gender should be returned – either as a code or as a name - by using the below configuration.
Prerequisites
None
Limitations
None
Configuration
Property Name | Description | Example Value |
Data Type |
---|---|---|---|
s4ci.feature.document.genderCode.enabled | Determines whether a gender code or a gender name should be returned in DOCS. If enabled DCCI will return a gender code. | False | Boolean |
Improvement for Enhanced Baggage Book Results
There are two options to link the baggage Air Extras (AE). They can either be linked per specific baggage or per specific baggage and segment group.
Digital Connect Check-In has adjusted the enhanced baggage book results to present AE links per group of segments.
This feature has been added as a part of Multiple Baggage Charges.
Prerequisites
None
Limitations
None
Configuration
Property Name | Description | Example Value |
Data Type |
---|---|---|---|
s4ci.feature.baggage.book.linkAirExtrasPerSegments.enabled | Determines whether the AE must be linked per segments or not. |
False |
Boolean |
Return Departure Airport in the Bag Tag Information
Digital Connect Check-In client application requires the information about bag tag departure airport for the first baggage, to build the appropriate request, to price the second baggage.
To meet this requirement, Digital Connect Check-In improved the baggage pricing service and now returns the departure airport code in the bag tag information, thus providing baggage route for a client.
Prerequisites
None
Limitations
None
Configuration
None
Add Extra Request Validation for Pricing Baggage
Digital Connect Check-In has added an extra request validation in /dcci/baggage/price. Now, when the request does not include any passenger, the request validation error message is returned.
Prerequisites
None
Limitations
None
Configuration
None
Bag Tag Details Default Values
Digital Connect Check-In has improved the logic of the pooled baggage support. When /cki/passenger/details service does not return the value for pooled baggage, Digital Connect Check-In will provide carrier code and arrival airport code for previously checked bags.
As a source for data Digital Connect Check-In uses:
- for carrier code - context airline
- for arrival airport – the final destination (last arrival airport from segments eligible for check in)
Prerequisites
None
Limitations
None
Configuration
Property Name | Description | Example Value |
Data Type |
---|---|---|---|
s4ci.feature.baggage.pool.defaultBagTagDetails.enabled |
Determines whether context airline as a default bag tag carrier and final destination as a default bag tag destination are enabled or not. default: True |
True |
Boolean |
Device Config Schema Improvement
Digital Connect Check-In has improved the configuration schema and now supports the dot character "." as a valid part of the device id in the device configuration.
Prerequisites
None
Limitations
None
Configuration
None
DR – B6 not Getting Second Bag Free from DR Rule
Customer Tracking #: N/A |
Sabre Tracking #: CSSDC- 2455 |
Description: Digital Connect Check-In /baggage/price returned the DR entitlements incorrectly. |
|
Resolution: Now, Digital Connect Check-In /baggage/price returns an internal error message in case of DR entitlements. |
|
Programs/Modules Affected: /dcci/baggage/price |
Passenger Details INTERNAL ERROR When First Flight in PDC
Customer Tracking #: N/A |
Sabre Tracking #: CSSDC- 2469 |
Description: dcci/passenger/details returned Internal error when retrieving a PNR with connecting flights where the first flight was PDC’ed and the feature PNR_BASED was enabled. |
|
Resolution: dcci/passenger/details returns reservation with two itinerary parts when PNR_BASED feature is enabled and the first flight in reservation is PDC’ed. |
|
Programs/Modules Affected: /dcci/baggage/price |
LAD0 - PROD - DCCI Returns SUCCESS on Failed Offload with "/PR/ IN OFFLOAD ENTRY NOT APPLICABLE"
Customer Tracking #: N/A |
Sabre Tracking #: CSSDC- 2443 |
Description: Invalid offload status was returned when the offload had been requested by seatNumber and offload was not successful. |
|
Resolution: Digital Connect Check-In evaluates the correct status based on the index in CKI response. |
|
Programs/Modules Affected: /dcci/passenger/Offload |