22.06 Release Notes
New Features:
DCS
- When a passenger checks in a journey that has both secure and non-secure legs, they will only be checked in if they are cleared on all legs. That means if APIS data is missing for any secure legs, the check in will be denied for the entire journey.
- A new validation has been added to help prevent a flight from being closed too soon. The time window when users can close flights is configurable per airline.
- Airlines can now configure the system to send/not send APIS data for a flight based on the aircraft model.
- A new feature has been added to help provide better customer service at airports. When loading a flight in the Check-in screen, if there are passengers with seat exceptions on the flight, a warning sign will appear to notify the agent. That warning sign also serves as a shortcut to the Seat Exceptions screen. The agent can quickly open the Seat Exceptions screen to handle exceptions with a single click.
- There is now an option to show a popup warning when the check-in agent tries to assign an emergency row seat during check-in. This warning reminds the check-in agent to validate the person being checked in is capable of complying with emergency exit row requirements.
GDS
(Important to GDS and DCS teams)
- When doing an even exchange for E-tickets, the user can now select that it was an 'involuntary' exchange during the managing process. This may happen when there are tickets on the reservation that are either unused or partially used and must be exchanged for new tickets. The new ticket will indicate during a display that it was an involuntary exchange.
- We now have the ability to process exchanges through GDS that require additional payment for fare and tax differences. Changes that require the collection of modification fees (EMDs) are still not supported. Refunds are still not supported.
RES
(Important to Commercial teams)
- When sending notifications from the Alert Notification screen, users now have the ability to determine if an itinerary is sent with each email update that is sent out.
- You can now split passengers from a PNR even when all segments are cancelled.
- When trying to use the manage ticket feature and an error occurs, the user will be given an error code with more descriptive text indicating that the intended action could not be completed.
- Agents with the proper permission can undo check-in for passengers in the Agency Portal.
Enhancements / Improvements:
IASCASE / Issue # | Description |
---|---|
19385 / AMELIA-16065 | The route order would become disarrayed when moving flights to and from the Routes to be Rolled section |
21587 / AMELIA-18326 | The Service Block management screen was crashing when multiple blocks were set for the same tail. |
22502/24250/27507/27637 AMELIA-19164 | An HK response was being sent even when segments were not found. An update was made to properly respond NO and with and SSR OTHS NO RECORD. |
27383 / AMELIA-22330 | After splitting passengers off a PNR, the following ASC message still contained the split passengers. |
27734 / AMELIA-22605 | An ASC message was not being triggered when the last public seat was consumed. |
DATABASE
Refer to the following for 22.06 DB Schema Changes.