20200/31672 / AMELIA-16983

When transferring credit, certain character combinations would be considered invalid and inhibit the ability to transfer credit to specific PNRs.

21604 / AMELIA-18327

In a GDS PNR with multiple passengers, when SSR TKNE is received for one of the passengers, the hold time (TTL) is removed. If the PNR is then split, the TTL was not being recalculated for the PNR where no passenger had a ticket number.

28943/28952/29218/30890/31099/31661 / AMELIA-23188

When processing an incoming PNR message that cancels a leg and books a new leg at the same time, if the RBD is not available for the new leg, the system incorrectly responds with status HK for the new leg even though the seat is not actually booked in amelia.

30019/30223/30908 / AMELIA-23716

GDS e-tickets were not being applied properly when the message contained a space in the name element, but not for the ticket.

30940/31462 / AMELIA-24163

Infants would be duplicated on the manifest if they are booked using a PTC discounted fare.

31007 / AMELIA-24235

If the system has two active PNRs with the same external locator booked via different GDS systems, it could update the incorrect PNR on subsequent messages.

31313/31317 / AMELIA-24319

SSM message sequence number could be incorrect when messages are broken into multiple parts.

31339 / AMELIA-24338

If a GDS booking did not specify the passengers gender, but the SSR DOCS did, the gender was not used for the passenger’s profile.

31591 / AMELIA-24438

Involuntary ticket exchanges were taking cancelled segments into account which could cause issues with the exchange.

31705 / AMELIA-24483

In certain instances, the Quote Details on the Fare Class Selection screen could pull incorrect tax information and show an incorrect quote amount.