Hawaii - Patch (22.12.6)

Release Summary


Kaptio is proud to announce this patch release for Hawaii. This release is intended to address issues with previous releases.

See Minor Changes and Bug Fixes for more information.


Sandbox Availability Date


2026-01-29


Release Type



Deployment Guide


See this page for the Hawaii Deployment guide.


Minor Changes


Feature: Live Services


Allow Refresh and Cancel Actions on Confirmed Bookings with Inactive Service Mapping Tables (CEE-562)

Overview:

Enhanced the booking action logic to allow Refresh and Cancel actions on confirmed live service bookings even when their associated Service Mapping Tables (SMTs) have been deactivated. This ensures that existing confirmed bookings remain manageable while preventing new bookings through inactive gateways.

Related Support Ticket: KHELP-12502


Feature: Package Search, Passenger Allocations


Person Account Aware Itinerary Creation (CEE-656)

Itinerary creation now better supports Person Accounts by automatically linking and pre-populating the lead passenger in the following flows:

  1. Package Search launched from a Trip (Trip → Package Search)

    • If the Trip’s account is a Person Account, the first (lead) passenger on the new itinerary is now:

    • Linked to that Person Account.

    • Pre-populated with the account’s data.

  2. Package Search launched from an Account (Account → Package Search)

    • If the Account is a Person Account, the first (lead) passenger on the new itinerary is now:

    • Linked to that Person Account.

    • Pre-populated with the data.

  3. “New Quote” from a Trip (Trip → New Quote)

    • If the Trip’s account is a Person Account, the first (lead) passenger on the new itinerary is now:

    • Linked to that Person Account.

    • Pre-populated with the account’s data.

These changes ensure that when working with Person Accounts, the lead passenger on new itineraries is automatically and consistently derived from the underlying Person Account configuration, reducing manual data entry and improving data consistency.

New pilot features: control passenger linking in bookings

We’ve introduced two new pilot features that give you fine-grained control over passenger linking behavior:

  • DisablePassengersLinkingB2B When enabled, passenger linking will be disabled for B2B bookings.

  • DisablePassengersLinkingNonB2B When enabled, passenger linking will be disabled for non‑B2B bookings.

Their names are intentionally descriptive – each feature does exactly what it says: it disables passenger linking for the corresponding booking type.

How to enable these pilot features

  1. Ensure the user has Pilot Features permission

    • Assign the “Pilot Features” permission set all users who need the logic to be disabled.

  2. Add the features in app settings

    • Go to App settings → User overrides → Pilot features.

    • Add the following feature flags(with separator ;) as needed:

    • DisablePassengersLinkingB2B

    • DisablePassengersLinkingNonB2B

Once configured, the selected pilot features will take effect and prevent passenger linking for the chosen booking segment(s).

Related Support Ticket: KHELP-12485


Feature: Manual Rail


Automatic Synchronization of Fare Class and Name Fields for Predefined Manual Rail Services (CEE-402)

Overview:

Added automatic synchronization of Fare Class and Name fields across all rail segments when Price Category changes in the Itinerary Builder for a Predefined Manual Rail

Related Support Ticket: KHELP-12219

Bug Fixes


Connect Reservation Id Not Saved After Retry When Salesforce Exception Occurs (CEE-547)

Overview:

Fixed an issue where the Connect Reservation Id was not saved on itinerary items after a retry following a Salesforce exception during booking, preventing future Refresh and Cancel actions.

Related Support Ticket: KHELP-11191


Regression: TBD time is no longer allowed on itinerary items (CEE-668)

What was fixed

  • Restored support for “TBD” as a valid value for:

  • Time From

  • Time To

  • Itinerary items and their parent itinerary booking records can now be saved correctly when these fields are set to TBD.

Result

  • Agents can once again save itinerary items with TBD times without errors.

Related Support Ticket: KHELP-12492