Iceland - Minor (23.26)
The Iceland 23.26 minor release strengthens Booking Wizard and air reservation workflows with clearer household address information, reliable reservation numbering, and more precise handling of occupancy changes. It also protects PNR data after travel has begun by preventing refreshes that could replace complete booking details with changed post-departure records.
Booking Wizard: Distinct Change Occupancy Classification (ST-4432)
KAPI-8994 Process Original Itinerary Before Cancellation or Transfer (CompleteFix) Cancellations Transfer Change Occupancy updates are now identified separately from general package modifications. This allows downstream integrations to process occupancy changes using the appropriate workflow while standard package modifications continue unchanged.
Reservations: Correct Starting Sequence for New Departures (ST-4428)
Reservation sequence number starts at 000 instead of 001 for new reservations Booking Wizard The first passenger reservation number on a new departure now starts at sequence 001 instead of 000. Subsequent reservation numbers continue to increment from this valid starting point, supporting consistent downstream processing.
Booking Wizard: Household Addresses in the Passenger Table (ST-4406)
Booking Wizard | Passenger Tab Address Missing from Household Booking Wizard The passenger table now displays the complete household billing address in all supported Booking Wizard modes, making address information available when reviewing assigned passengers.
Booking Wizard: Complete Addresses in Contact Search (ST-4405)
Booking Wizard | Search Contact Address incomplete Booking Wizard The Search/Create Contact window now displays the complete household billing address rather than only the street and postal code. The wider address column also makes city, state, and country information easier to review when selecting a contact.
PNR Management: Protect Booking Data After Departure (ST-4346)
Suppress PNR refresh once travel has commenced Right Rez PNR refresh now stops once the earliest stored air departure for that locator has passed, preventing post-departure GDS changes from overwriting existing passenger, segment, fare, and ticketing data. Manual and API refreshes provide a clear message, while new PNR imports and eligible future locators remain available.