New Features:

API

(Important to internal and external development teams)

RESTv1 (See the API documentation for further details.):

All of the travelOptions API endpoints have been changed to have cabinClass as an optional parameter rather than required. When not provided, the API results will include fares for all cabins.
The seatSelectionOptions API endpoint has been been updated to include a reservedWithInfant attribute that is true when the seat has a lap infant or infant passenger. This allows the API consumer to display this information on the user interface.

The system now support a pre-set checked baggage weight. When this mode is enabled, bag weight will be populated automatically when amelia users enter the number of bags or when the system processes inbound PRL and IATCI messages. Only users with the appropriate permission can overwrite the bag weight.
A new business rules has been implemented that, when enabled, the system will keep passenger information and APIS information in sync automatically. The following fields will be synched between the 2 screens: First Name, Last Name, Middle Name, Nationality, Title, DOB and Gender.
When using strict boarding mode, a scan of a group PNR will filter Check-in grid to just the reservation party.
Save check-in grid column order to grid settings for subsequent logins.

(Important to GDS and DCS teams)

Incoming PRL messages will now process GOSHO and NOREC entries and create new PNRs where required.
We now have the ability to process an even exchange through GDS . Based on our testing, there can be rounding differences between the way the ameliaRES and a GDS calculates taxes. To accommodate this, we have added a customizable threshold where it will still be considered an even exchange even if there is a slight difference it totals. You can discuss with your account executive if you wish to activate this feature.

(Important to Commercial teams)

When a segment is cancelled via the Travel Agency portal, the ticket can be fully refunded and a unique payment created for cancellation charges. This includes when the segment is by itself, or if all other segments are flown.
The Travel Agency portal now supports the ability to show all cabin classes when searching for flights. Contact your account executive for details on how to customize your site to support this feature.
We can now ticket codeshare reservations with the 1P Ticket Database. The ticket display will show which tickets are applied to the reservation, either from the 1P or 1Q Database.
The Detailed Sales Report now shows the associated ticket number(s) for each passenger/journey.
The Outstanding Date Range Web Report has been enhanced to show the journey notes for each reservation.

IASCASE / Issue #	Description
18317 / AMELIA-14933	OSI CTCE lines with specific formats would sometimes be parsed incorrectly and the message would fail to process
20686/26166 / AMELIA-14618	Child-only bookings via GDS failed when there was no passenger reference in the message.
24039 / AMELIA-20180	Larger SSM messages could fail to be processed by certain receiving systems, so they were updated to be sent in multiple parts.
26872 / AMELIA-21738	Adding a journey via GDS would fail when the new journey was being booked in a different currency than the first journey.
27098 / AMELIA-22158	Could not find SYN messages when searching by locator.

DATABASE

Refer to the following for 22.04 DB Schema Changes.