24.01 Release Notes

New Features

API

  • When moving a passenger to a new flight using PUT journey, ameliaRES can now support maintaining the passenger’s purchased ancillaries and assigned seats without adding new charges.

  • GET queues has a new ‘includeHistorical’ data parameter. When set to true, the endpoint will return both ‘handled’ and ‘open’ alerts. Previously, the endpoint only returned ‘open’ alerts.

  • A ‘PassengerReference’ field has been added to Passenger events. This field uniquely identifies the passenger that the event applies to.

DCS

  • ameliaRES can now send Upcoming Travel reminders via SMS for passengers who have selected SMS as one of their preferred notification methods. This feature requires activation of the SMS module in ameliaRES. Please contact your Account Executive or reach out to info@intelisysaviation.com to learn more about the amelia SMS product.

GDS / Interline

  • ameliaRES has been enhanced to include support for adding interline segments to interline bookings.

  • You can now exercise greater control over interline bookings by seamlessly adding, editing, and removing partner segments. This feature empowers manual intervention to address any potential data issues that may arise. Please note that special permission is required to access this function.

  • We have enhanced the display of fare rules for interline bookings, providing a more user-friendly experience by presenting them in clear, natural English rather than JSON format. The fare rules can now be included in the passenger's itinerary.

  • Your airline now has the capability to manually update coupon statuses. This proves especially beneficial in addressing potential data synchronization issues. By leveraging this feature, you can efficiently resolve reservation errors, guaranteeing a smooth boarding experience for passengers. Given the significant impact of this action, users are required to obtain appropriate permissions to proceed.

  • Now, you have the flexibility to refund an amelia EMD using a different payment method than the one originally employed.

  • With the activation of the auto refund feature, in the event of a segment cancellation within a GDS booking, ameliaRES will now seamlessly generate an Electronic Miscellaneous Document (EMD) for the penalty and initiate an automatic refund for the remaining credit.

RES

  • Previously, the custom message/body of itinerary emails was constrained to 1,000 characters. This limitation has been lifted, enabling more expansive and detailed messaging in your itinerary emails.

  • There is a new Daily Flown Revenue web report that shows the tickets tickets anc changes for PNRs in a given time range.

  • We've introduced an enhancement to the Detailed Sales report by adding a 'Coupon' column. This new addition will display all coupons associated with the respective tickets, providing a more comprehensive overview.

Enhancements / Improvements

IASCASE / Issue #

Description39

IASCASE / Issue #

Description39

36259 / AMELIA-26038

Previously, the API was allowing cancellation of journeys where a passenger was already checked in. Moving forward, this will result in an error message to the API caller.

38057 / AMELIA-26721

During the data synchronization process between reservation and APIS data, there was an error where Danish special characters were mistakenly replaced with English characters. This caused issues when attempting to match names while scanning boarding passes. This issue is now resolved.

38234 / AMELIA-26734

The issue, wherein PNR messages were being disregarded for journeys within the reservation lock time window (X hours before or after flight departure), has been successfully resolved. Previously, ameliaRES failed to send any response to inform the partner system that the requested change was not implemented. This issue has now been rectified, ensuring proper communication of changes within the specified time window.

38421 / AMELIA-26796

The outbound PNR Sync messages incorrectly included flown segments. This issue is now rectified.

38440/38456/38457 / AMELIA-26803

The system did not properly handle the coupon status updates with the REP status from ETDB. This issue has been resolved.

AMELIA-26765

When a voucher is used with another payment and the other payment fails, it can leave the voucher in a pending (unusable) state. ameliaRES will now automatically revert any affected voucher to an active state allowing the user to try it again on another transaction.



DATABASE

There are no DB schema changes in this release.