23.08 Release Notes
New Features
API
RESTv1 (See the API documentation for further details)
The frequentFlyers/{key}/loyaltyAccountTransactions endpoint now supports POST/PUT/DELETE transactions. This allows API users with the appropriate permissions to add or remove point transactions from a frequent traveler’s profile.
A new POST /reservations/{key}/paymentTransactions/{paymentTransactionKey}/refundTransactions endpoint has been created. This will allows your external applications to refund payment transactions.
GET queues now supports reservationNumber and reservationLocator as optional parameters. When included, only queue items related to the specified PNR will be returned.
The permission API > Expose Summary Contact Information is now required for passenger contact data to be included in GET departures calls.
DCS
A new column has been added to the check-in screen simplifying the process for users to distinguish interline bookings. The column displays a value of "Y" or "N".
DIRECT
You now have the ability to book interline reservations directly on the SOAR website. Please note that, purchasing ancillaries and seat selection are currently not available for those reservations.
GDS
Passengers who have interline bookings starting with a segment operated by a partner carrier can now be re-protected in IROPS situations.
You can now cancel segments for interline bookings booked through ameliaRES. This feature is currently only accessible through the desktop application, and there are no cancellation fees applied.
Partner fare rules can now be viewed on the flight availability and reservation screens.
Adding ameliaRES segments to interline bookings is now supported through the desktop application.
When processing incoming SSM/ASM messages, in cases where the e-ticketable flag is not included, the system can use a default value of either “Y” or “N” based on your system configuration.
TICKETS
In order to simplify the process of identifying EMDs for handling, the ticket screen's EMD section now provides additional details such as flight date, departure/arrival airports, and the corresponding amount.
To streamline the process of refunding GDS booking EMDs directly from the check-in screen, we have introduced a new feature that enables users to initiate EMD refund from the DCS charges screen. Users can now refund a payment and all the associated EMDs will automatically be refunded.
When the payment screen is loaded for GDS bookings, all charges for EMDs will be automatically selected for payment by default.
When managing e-tickets in IROPS situations, if the Involuntary Change checkbox is selected and the user has the appropriate permission, we will now let the user deselect coupons on either side of the ticket maintenance window. This will ignore these coupons in the issuance message.
The Ticket Details screen has been enhanced to display tour code information.
RES
Call centre agents can now conveniently send a payment link for PNR transactions via email. This can be done when a user wants to pay using an online payment method. Reach out to InteliSys today to activate this seamless payment option for your airline.
The user would select “Request Payment by Customer”, fill in the appropriate data and send.
An email is sent using the information entered.
When the recipient clicks the link, they will be sent to the PNR on the SOAR MMB site. They can click Settle to make a payment using any of the supported methods.
For a new booking, the PNR is left on hold until the payment is made. If the payment is not made by the end of the hold period, it is cancelled.
Ancillary items can be marked as non-refundable. If a non-refundable ancillary item is cancelled or removed, the associated charge will remain on the PNR.
When making a change using the IROPS tool, you now have the option to notify passengers during the Bulk Move phase. This feature eliminates the need for manual alerts and delayed notifications.
When appending a new note to a PNR, the system can now display it at the top for immediate visibility of the most recent updates. Reach out to InteliSys to enable this feature for your airline.
Enhancements / Improvements
IASCASE / Issue # | Description |
---|---|
19867/22052/24953/26635/28717/29593 / AMELIA-16996 | In certain cases when rerouting multiple bags, the bag would appear on the wrong flight with incorrect passenger information. |
30767 / AMELIA-24527 | When checking in, the IATCI popup message box would show even when there was no partner airline that needed an IATCI message. This has been removed. |
DATABASE
Refer to the following for 23.08 DB Schema Changes.