24.03 Release Notes

New Features

API

  • Sending itineraries via reservations/{key}/emailItinerary now supports the inclusing of a .ICS file to easily add your reservation details to your calendar.

  • GET departures has a new “flightLegDateRequest” parameter. When true, the the scheduled date/time will be used. When false, the flight watch date/time (including delays) will be used.

DCS

  • The passenger’s email address and loyalty tier have been added as optional columns in the check-in grid.

DIRECT

  • SOAR OCI now has the ability for passengers to cancel their online check-in request which sets the passenger back to NOIN (not checked-in).

GDS / Interline

  • To ensure agents are adequately informed during Irregular Operations (IROPS) situations requiring amelia users to modify a partner segment on interline bookings, we've introduced two enhancements: 1) Inclusion of partner segments in SYNC messages sent to the booking originator; 2) Implementation of RDT messages to redirect results from the partner carrier to the booking originator.

  • In the event of IROPS (Irregular Operations), it is now possible to reaccommodate passengers by transferring them from an amelia segment to an interline segment. This functionality extends to all bookings, even those that were initially non-interline.

  • The fare rules screen, as well as itineraries and e-tickets generated through ameliaRES, now include the display of Baggage Allowance information for interline segments.

  • Users can now use multiple payment methods when making payments on EMDs issued for GDS bookings.

RES

  • The system can now differentiate between refundable/non-refundable fares and taxes. This allows you to specify a fare as non-refundable, but still have specific charges/taxes refundable. Please talk to your account executive for details on how to configure your fares and charges.

  • Emailing passenger notifications from alerts now supports the ability to include the PDF or embed the itinerary in the email body.

  • Audit entries for adding and changing reservation segments now include the arrival time.

  • There is a new web report (Passenger Flight Notification Report) that shows the details for all passenger notifications sent in a certain timeframe. The reports includes the PNR Locator, Passenger Name, Notification Type (email, SMS), Alert Type, Sent Date/Time and Message Body.

  • The Agent Bookings Export Report now has a “Channel” column that shows what channel the reservation was created from.

  • The Company Expiry Report, which was previously only available in the Data Exports, is now available as a web report.

Enhancements / Improvements

IASCASE / Issue #

Description

IASCASE / Issue #

Description

26635/37917 / AMELIA-26659

When re-routing multiple bags simultaneously, the system would sometimes link the baggage to an older PNR.

35276/38274 / AMELIA-25671

If the Charge Override Tracking screen was closed without using the Save/Cancel buttons, the override would be applied without having to give a reason. This has been amended to cancelling the override. The only way to proceed with the override is to use the Save button.

36951 / AMELIA-26275

When doing a fare change to a fare with packaged ancillary items, the items would not be removed. The fare packaged items will now be removed and, if applicable, items packaged to the new fare will be added.

37841 / AMELIA-26655

When copying and pasting email addresses from other sources, the paste could include unseen, invalid charactures (e.g. line feed) which could cause the send to fail. We have updated the code to trim any invalid characters to ensure the send is successful.

37981 / AMELIA-26645

In certain instances, the BKF81 record within HOT files may contain an additional space, leading to complications during processing by accounting software.

37994 / AMELIA-26711

Resolved an issue causing duplicated payments on a booking when the first coupon of the ticket is issued for an OAL segment.

38490 / AMELIA-26830

Fixed an issue that was preventing the manual refund processing for EMDs on amelia bookings.

AMELIA-25594

Currently, when handling inbound PNR messages from GDS for trips with connections, amelia exclusively accepts through fares from the origin to the destination. However, recognizing that multiple sector fares are occasionally consolidated instead of a through fare, amelia now allows this combination. The system will prioritize the through fare if available; otherwise, it will consider combined sector fares.



DATABASE

Refer to the following for 24.03 DB Schema Changes.