Breadcrumb
- Digital Connect Online Help
- Getting Started
- Release Notes
- Digital Connect 22.03 Release Notes
Digital Connect 22.03 Release Notes
Release Identification
Release Version | Type (Version, Update, or Patch) | Date | Approved by | Description of Change |
---|---|---|---|---|
22.03 | Version | March 2022 |
Sebastian Santos |
Software updated |
Enhancements
Digital Connect introduces the following enhancements:
- Travel Bank Refunds - Security Checks
- Seating Data and Air Extras retained upon upgrade.
- Verifying VCR status for upgrade flow
- Upgrade Flow - revert points in Flat Fee Upgrade
- Price breakdown per passenger in shop response
- Air Search Response enhancement - Endorsable Indicator and Meal Code
- DC Metasearch enhancement - optional Fare Basis Code
Defect fixes
Digital Connect introduces the following defect fixes as part of this release:
- Incorrect Departure Date in Stopover Flights
- Commercial Seat Name Incorrectly Displayed on EMD
- Restrictive Email Length Validation
- PNRs not Placed on Queue When Adding SSRs
- Redemption Booking SIgned-in User Details Issue
- Session Id Missing in PnrDisplay Response Headers
- Agent Sales Report Dashboard Activation Issue
- Ancillary Error for Second Bag Fee
Enhancements
Travel Bank Refund - Security Checks
The Travel Bank refund functionality is enhanced with regards to the security checks preventing unauthorized users from receiving refunds to their Travel Bank accounts. The security checks are extended to the Modify Trip Options (MYB:MTO) and Change Itinerary (MYB:CI) flows. The enhancement does not involve any changes to the configuration keys.
Prerequisites
- Airline must have Travel Bank enabled.
Limitations
None.
Seating Data and Air Extras retained upon upgrade
This enhancement ensures that when a passenger upgrades one or more of their segments (but not all segments) and makes a new seat selection in the new cabin, all his original seats for non-upgraded segments are retained including the Air Extras data. The passenger can view the originally paid seat as well as the newly selected upgrade upon completion of the upgrade flow on the MYB summary page.
This enhancement applies to the Upgrade flows:
- FFU
- FQTU
There are no contract changes for this enhancement.
Prerequisites
None.
Limitations
None.
Verifying VCR status for upgrade flow
Digital Connect introduces an enhancement that verifies the VCR status to apply necessary servicing options to the correct VCR. Multiple VCRs with different statuses can be a part of a PNR. This allows PNRs that contain valid tickets alongside voided and/or refunded tickets to enter the upgrade/MTO flow and successfully upgrade flight segments and associate the EMD to the correct VCR. In case of a ticketing failure, an error message is displayed on the Confirmation page.
The Upgrade/MTO EMD may be associated to VCRs with the statuses:
- OK
- CKIN
The Upgrade/MTO EMD’s may not be associated to VCRs/Segments in the following statues:
- VOID - Void
- RFND - Refunded
- EXCH - Exchanged
- USED - Used
- LFTD - Lifted
- CTRL - Control
Prerequisites
- The airline has FQTU/FFU and/or MTO enabled.
Upgrade Flow - revert points in Flat Fee Upgrade
Digital Connect enhances the upgrade flow with the ability for the application to revert the user’s points back to their Loyalty account in cases when the upgrade transaction is unsuccessful. This ensures that points are not deducted from the user's account unless the upgrade transaction is successful and the user has a confirmed space in the upgraded cabin.
Prerequisites
None.
Limitations
- Does not apply to the FQTU flow
Price breakdown per passenger in shop response
The aim of this new functionality is to expose a price breakdown per passenger from the API response. The configuration "sat.flights.pricePaxesCalculation.type": can be sent to “ALL_PAX” or “ONE_PAX” to present the price breakdown per passenger type or for the individual passengers.
• If the configuration is set to: "ALL_PAX", the total fare amount for all passengers per passenger type is displayed.
• If the configuration is set to: "ONE_PAX", the total fare amount per passenger under one passenger type is displayed.
This allows for the price breakdown to be used by Digital Connect directly without the need to match DC data with Sabre Web Services' response.
The enhancement applies to all types of calendar searches currently supported in DC (Calendar30, Matrix, 7-day ribbon, and Flexible Calendar), branded fares, and the RBE path.
Prerequisites
- For Calendar30
- Calendar shopping must be enabled.
- For Calendar Matrix
- Airlines must have RT (return) display and Matrix format configured (Matrix is available for RT trips only).
- Airlines must have Advanced Shopping enabled (Matrix is available for advanced shopping only).
Limitations
None.
Air Search Response enhancement - Endorsable Indicator and Meal Code
Digital Connect introduces an enhancement to the Air Search service that includes additional fields in the service response. The information includes an endorsable ticket indicator and meal code for the specific flight segment sold.
The endorsement indicator is returned as one of two subfields of the Air Info field - a non-refundable indicator and a non-endorsable indicator.
Meal codes are displayed per flight leg:
"origin": "BNE", "destination": "MEL", "departure": "2022-02-18T16:00:00", "arrival": "2022-02-18T18:30:00", "bookingClass": "M", "layoverDuration": 0, "fareBasis": "IZLT0A14", "subjectToGovernmentApproval": false, "meals": [ { "passengerType": "ADT", "mealCode": "G" }, { "passengerType": "CHD", "mealCode": "G" }, { "passengerType": "INF", "mealCode": "G" }
The enhancement applies to:
- RBE Flow
- B2C Flow
- Matrix Search
- Calendar 30
- Branded Search
Prerequisites
None.
Limitations
- The enhancement is not applicable to unbundled offers.
DC Metasearch enhancement - optional Fare Basis Code
Digital Connect metasearch was enhanced by passing the fare basis code as optional. This allows the airlines that retrieve the fare basis from other sources to bypass a DC validation that throws an error in case of fare basis code mismatch. By making the fare basis code optional, the validation is relaxed to allow the flow to continue without getting an error response.
An additional parameter (skipFareBasisCheck, boolean) has been added to the metasearch request.
Prerequisites
None.
Limitations
None.
Defects
Incorrect Departure Date in Stopover Flights
Customer Tracking #: 05491648 |
Sabre Tracking #: DC-12104 |
---|---|
Description: Some flights containing a stopover were returning an incorrect departure date for the second leg of the flight. |
|
Resolution: Resolved by using the scheduled departure date from the downline response as the actual scheduled departure date while preparing the response for both flight legs/segments. |
Commercial Seat Name Incorrectly Displayed on EMD
Customer Tracking #: 06012843 |
Sabre Tracking #: DC-14095 |
---|---|
Description: An incorrect commercial name was displayed on Seat EMDs in the B2C flow. |
|
Resolution: The seat commercial name is retrieved from Ancillaries' response while preparing the EMD document of the Collect Misc Fees operation. |
Restrictive Email Length Validation
Customer Tracking #: 05776574 |
Sabre Tracking #: DC-13150 |
---|---|
Description: The email length validation prohibited using some valid email addresses to be used, resulting in returning an error. |
|
Resolution: The regex configuration which was being updated for emails was not being reflected in the Passenger service since it was using EmailFieldValidator class, where hardcoded regex was used. Instead, we changed emails to be validated for passengers using TextFieldValidator class by taking dynamic regex passed from SAT settings. Passenger model classes that were being used were in the common-contract jar. |
PNRs not Placed on Queue When Adding SSRs
Customer Tracking #: 06012612 |
Sabre Tracking #: DC-14199 |
---|---|
Description: PNRs were not being placed on a queue upon adding SSRs. |
|
Resolution: Payment-Workflow XML was lacking the condition present in DC-Core after completing payment. PNRs should then be added to a particular queue in caste there were SSRs added. We have added the condition to resolve the issue. |
Redemption Booking SIgned-in User Details Issue
Customer Tracking #: 06106217 |
Sabre Tracking #: DC-14126 |
---|---|
Description: When creating a redemption booking, an error was occurring while pre-populating the details of a signed-in Mosaic user. |
|
Resolution: We introduced a code fix to get the profile when the card does not have an expiration date. The profile can be updated without the card expiration date by making the configuration sat.json.service.profile.validation.profile.userCreditCards.expirationDate.required=false optional. |
Session Id Missing in PnrDisplay Response Headers
Customer Tracking #: N/A |
Sabre Tracking #: DC-14180 |
---|---|
Description: While calling reservation/pnr/display with subjectAreas in the request, the service did not return session id in the headers. |
|
Resolution: Code has been enhanced for reservation/pnr/display with subjectAreas in the request for the service to return the sessionId in the response headers. |
Agent Sales Report Dashboard Activation Issue
Customer Tracking #: 05706361 |
Sabre Tracking #: DC-12998 |
---|---|
Description: Agent Sales Report dashboard did not display. |
|
Resolution: Code has been fixed for asr-reports apps in which stationNumber and employeeNumber elements can accept the string datatype values. It can accept the leading zero values for both elements. |
Ancillary Error for Second Bag Fee
Customer Tracking #: N/A |
Sabre Tracking #: DC-14190 |
---|---|
Description: When booking a round trip with different outbound and inbound brands, the GET ancillary code has correctly returned 0C3, but an error was returned upon making the select itinerary call: "ancillaryOperation[0].selectedPassengers[0].index": [ "invalid|passenger not eligible" ] |
|
Resolution: A code fix in "AncillaryOfferProvider" has been introduced to resolve the issue. |