Hawaii - Patch (22.12.9)

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-02-24

Release Type

Patch Release

Deployment Guide

See this page for the Hawaii Deployment guide.

Minor Changes

Feature: Group Tour, Payments

Payment Schedule Processing Optimization (KT-14018)

Problem/Background

Payment schedule recalculation always ran in sync, leading to unnecessary work during updates. There is no reason to run it in sync for Operational itineraries, and it serves no purpose for Price Model itineraries.

Solution

Payment schedule and recalculation flows now skip Price Model itineraries and honor async processing for Operational itineraries across itinerary, itinerary group, and passenger updates.

Impact

Operational updates are processed more efficiently with fewer unnecessary schedule recalculations, improving overall system responsiveness.

Bug Fixes

Supplier Invoice Lines "Dates with Time" and "Due Date" are calculating incorrectly (KT-14062)

Problem: "Dates with Time" and "Due Date" fields on Supplier Invoice Lines are calculating incorrectly.

Solution: Fixed the "after travel" date calculation logic for supplier invoice lines to correctly compute "Dates with Time" and "Due Date" fields.

Lead Passenger Assignment Fix for Multi-Role Import Scenarios (KT-14078)

Problem

When importing passengers into an itinerary that already contained passengers with different channel roles, the system could incorrectly assign lead passenger status to newly imported passengers, even when a valid lead passenger already existed on the itinerary.

This issue occurred specifically when:

  • An itinerary had existing passengers with valid lead-eligible roles (such as Adult)

  • One of those existing passengers was already designated as the lead

  • New passengers with different channel roles were imported

  • The system failed to recognize that existing passengers were valid lead candidates

As a result, the newly imported passenger would incorrectly become the lead passenger, overriding the existing lead assignment and potentially causing confusion in customer records and communications.

Solution

The passenger validation logic has been enhanced to properly evaluate all passengers—​both existing and newly imported—​when determining lead passenger assignments. The system now:

  1. Retrieves complete role information: When validating lead passengers during import operations, the system fetches channel role details for both incoming passengers and existing passengers on the itinerary

  2. Validates across all roles: The lead passenger eligibility check now considers the occupant types of all passengers, ensuring existing valid leads are preserved

  3. Maintains data integrity: The enhanced validation prevents incorrect lead reassignment when passengers with various channel roles are present

Impact

For Operations Teams:

  • Passenger imports will now correctly preserve existing lead passenger assignments

  • Lead passenger information will remain accurate when adding passengers to itineraries with multiple channel role types

  • Reduced need for manual correction of lead passenger assignments after bulk imports

For Sales and Customer Service:

  • Customer communications will consistently reference the correct lead passenger

  • Improved data accuracy for itineraries with diverse passenger configurations (e.g., drivers, captains, adults)

  • More reliable lead passenger information for booking confirmations and correspondence

For System Administrators:

  • Enhanced data quality for passenger records

  • Reduced support requests related to incorrect lead passenger assignments

  • Better handling of complex itinerary configurations with multiple role types

Technical Details

Components Modified: Passenger trigger logic, Lead passenger validation
Test Coverage: Added comprehensive test case covering multi-role scenarios with existing and new passengers

Validation

The fix has been validated with scenarios including:

  • Itineraries with existing TBD passengers as leads

  • Import of passengers with different channel roles (Driver, Captain, etc.)

  • Multiple existing passengers with various occupant types

  • Verification that only one lead passenger exists per itinerary after import operations