Breadcrumb
- Digital Connect Online Help
- Getting Started
- Release Notes
- Digital Connect 22.10 Release Notes
Digital Connect 22.10 Release Notes
Release Identification
Release Version | Type (Version, Update, or Patch) | Date | Approved by | Description of Change |
---|---|---|---|---|
22.10 | Version | October 2022 |
|
Software updated |
Defect fixes
Digital Connect introduces the following defect fixes as part of this release:
- Interline ticket with CTRL status
- Staff travel PNRs not processed
- Staff travel - unable to edit passenger details
- Adding paid seats after voluntary exchange
- An issue with MFOP booking exchange
- Open system Payfields not added when Infant present in the booking
- Downline unresponsive when retrieving divided PNR
Defect fixes
Interline ticket with CTRL status
Customer Tracking #: n/a |
Sabre Tracking #: DC-15891 |
---|---|
Description: In cases when a coupon had a CTRL status, but under interline its status was OK, Digital Connect had returned an error due to not reading the coupon status from the node returning the actual status, thus making the PNR not eligible for cancellation. |
|
Resolution: If the downline returns a CTRL status for any coupon, but the Controlling Provider returns another status, then this status replaces the downline status. |
Staff travel PNRs not processed
Customer Tracking #: 06317211 |
Sabre Tracking #: DC-15005 |
---|---|
Description: Digital Connect lacked the functionality to process non-revenue (staff travel) PNRs. |
|
Resolution: Staff travel PNRs are processed in Manage Your Booking: Change Passenger Details and Manage Your Booking: Modify Trip Options flows. To identify a PNR as staff booking, Digital Connect checks the PNR for the following parameters:
|
Staff travel - unable to edit passenger details
Customer Tracking #: 06317217 |
Sabre Tracking #: DC-15571 |
---|---|
Description: Digital Connect lacked the functionality for non-revenue (staff travel) confirmed bookings to update passenger details such as phone number, email address, Frequent Flyer number and Special Service Requests e.g. meals, special needs requests, travel documents and visa information. |
|
Resolution: We have enabled the confirmed staff travel PNRs (HK status) to add/edit passenger details. Digital Connect only identifies staff travel bookings that meet the following parameters:
|
Adding paid seats after voluntary exchange
Customer Tracking #: 06435987 |
Sabre Tracking #: DC-15321 |
---|---|
Description: If a passenger attempted to add a seat after a voluntary exchange, Digital Connect was returning the following error message: "PNR is not eligible for ADD_MODIFY_ANCILLARIES. Reason: irop.disallow". |
|
Resolution: The IROPFlown mutation rule has been updated to allow adding a seat after a voluntary exchange. |
Issue with MFOP booking exchange
Customer Tracking #: 06637260 |
Sabre Tracking #: DC-16024 |
---|---|
Description: When attempting to exchange a booking containing an EMD for an Economy X seat that has been paid for using a credit card + Travel Bank form of payment (MFOP), users were unable to complete their payment due to a downline error. |
|
Resolution: To resolve the issue we have fixed auto refund for the Travel Bank form of payment for the Modify Trip Options flow (MYB-MTO) without login, provided the Travel Bank without login feature is enabled. |
Open system Payfields not added when Infant present in the booking
Customer Tracking #: n/a |
Sabre Tracking #: DC-16099 |
---|---|
Description: In cases when Infant was present in bookings purchased using points and/or credit cards, Open system Payfields were not added. |
|
Resolution: We have added validations in the comparator of the field segments when extracting the ETicketCoupon field of the segments. |
Downline unresponsive when retrieving divided PNR
Customer Tracking #: n/a |
Sabre Tracking #: DC-15927 |
---|---|
Description: When a PNR was created from the airline's user interface, while trying to retrieve the PNR from the DC downline and divide the PNR, the downline became unresponsive and the divided PNR was not appearing. |
|
Resolution: We have updated the first Name on the payfields of the booking to follow the same standard as in Passengers, which is the first name middle name or the initial letter of the middle name depending on configuration, along with the title. |