Hawaii - Minor (22.12)

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

See Minor Changes and Bug Fixes for more information.

Fare Class Field Becomes Disabled and Uneditable in Manual Rail Segment Modal (CEE-463)

Fixed the field state management logic in the Manual Rail segment modal to keep the Fare Class field editable even after being cleared or when focus leaves the field. The field now remains enabled and allows users to enter or modify the Fare Class value at any time before saving.

Package Search Modal Content Cut Off When Accessed from Trip/Itinerary (CEE-492)

From now on we can see the entire Package and the scroll bar along the bottom

"Attempt to de-reference a null object" Error When Bulk Moving Live Rails with Occupancy Pricing (CEE-493)

Fixed the price request building logic to ensure response.price_lines_by_passengers is always included in response_fields when occupancy pricing is enabled on the service, regardless of other conditions.

Related Support Ticket: KHELP-12322

Incorrect Price Requests for Live Rails After Bulk Date Moves (CEE-495)

Fixed the price request building logic to correctly associate search_parameters with their corresponding selected_trips for each rail itinerary.

Related Support Ticket: KHELP-12324, KHELP-12261

Fare Class and Service Level Not Persisting for Live Rail Component Options in Packages(CEE-498)

Fixed the "Cannot Set Properties of Undefined (setting 'IsDisabled')" Error when opening existing Live Rail components.

Related Support Ticket: KHELP-12320

Fare Class and Service Level Not Persisting for Live Rail Component Options in Packages (CEE-538)

Fixed the save logic to properly persist Fare Class and Service Level values for Live Rail component options.

Related Support Ticket: KHELP-12370

Reservation Cancellation Failures Due to Missing Sales Price Line for Custom Items (CEE-544)

Fixed the cancellation price calculation logic to include the actual sales price for custom items in the price request. The system now properly sends both supplier and sales price lines when requesting prices for custom items during cancellation, ensuring the API receives all required data to calculate cancellation totals.

Related Support Ticket: KHELP-12373

Incorrect Confirmation Status When Cancelling Itineraries (CEE-545)

When cancelling an itinerary, all services (including previously confirmed services and those with "Confirmation Not Needed" status) were incorrectly being set to "Cancelled Manually" (61) instead of the appropriate status based on their pre-cancellation confirmation state.

Related Support Ticket: KHELP-12374

"Re-check Inventory" Not Working for On-Request Services with Advanced Inventory Setup (CEE-567)

Fixed the inventory check logic to ensure that services with Advanced inventory setup are always checked for inventory changes, regardless of their current status.

Related Support Ticket: KHELP-12358

Calculations for generating Price Model Output records are not considering promotions IF a custom field has been introduced (GTT-499)

Updated price calculation KTAPI request with itinerary fields from custom metadata type to consider promotion rules

Validations on By Departure Inventory creation tab disappear when switching tabs between service and Inventory (GTT-519)

Reapply validation rules when switching btw tabs

Creation of Tour Departure without Departure Status (GTT-590)

Fixed bug with saving empty required field Departure status.

Truncate a Callout snapshot record if it’s too big (GTT-613)

Truncated JSONRequest field value if length achieved max field length limit ---

Can’t set IsCrewMemeber flag for channel role in existing Kaptio settings interface (GTT-616)

Added IsCrewMemeber flag for channel role modals

Inventory contracts are created with incorrect Allotment Categories in new Inventory LWC (GTT-617)

Fixed bug that Inventory contracts are created with incorrect Allotment Categories in new Inventory LWC

Cancel button in Edit Supplier Agreement popup does not work as expected NX-1102 (KT-13380)

Issue: The Cancel button in the Edit Supplier Agreement popup now properly discards changes and restores original values. Previously, modifications made to the form would remain visible even after clicking Cancel, causing confusion about which values were actually saved.

Impact When editing a Supplier Agreement, clicking Cancel will immediately revert all fields to their saved values. The form will consistently display the correct saved data when reopened, eliminating confusion caused by unsaved changes persisting in the interface.

Example: When the Agreement Type is changed from "Commission" to "Net Rate" and Cancel is clicked, the form now correctly reverts to displaying "Commission" rather than incorrectly showing "Net Rate" on subsequent edits.

Duplicate Supplier Agreements Created on Repeated Save (KT-13852)

Issue: When creating or editing a supplier agreement, clicking the Save button multiple times could result in duplicate agreements being created in the system.

Root Cause: The Save button did not have proper protection against multiple rapid clicks. Once a save operation was initiated, the button remained enabled, allowing users to submit multiple requests before the first one completed.

Resolution: We’ve improved the save button’s handling to prevent duplicate submissions. The button is now properly disabled during the save operation, and users will see a loading indicator while their agreement is being saved. Once the save completes (successfully or with an error), the button is re-enabled for further action.

Impact:

Action Required: No action needed. This fix is automatic and applies to all existing and new supplier agreements.

Duplicate "When" Field Value in Supplier Payment Rules Table (KT-13854)

Issue: The Description field in the Supplier Payment Rules table now displays correctly without duplication. Previously, the "When" field value (e.g., "Before Travel", "After Booking") appeared twice in the description, creating redundant and confusing text.

What Changed: The payment rule description format has been corrected to display:

Additionally, the description now properly uses singular "day" when the Days field equals 1, and plural "days" for all other values, improving readability.

Impact: Payment rules in the Supplier Agreement will now display clear, properly formatted descriptions without duplicate values, making it easier to understand payment terms at a glance.

Incorrect Passenger Date of Birth in Passenger Import (KT-13857)

Issue: Date fields in the passenger import feature (including Date of Birth) now import correctly without timezone conversion errors. Previously, dates in imported CSV or Excel files could be shifted by one day due to automatic timezone adjustments during parsing.

Root Cause: When Excel files were parsed, the XLSX library was configured to convert date cells into JavaScript Date objects, which triggered browser timezone conversions. This caused dates to shift unexpectedly depending on the user’s timezone.

Example of previous behavior: * Import file contains: DateOfBirth__c: 1990-06-30 * After import, passenger record shows: 1990-06-29 (shifted by one day)

What Changed: The file parser now processes dates as formatted strings rather than Date objects, preventing timezone conversion:

Impact: Passenger imports will now display dates exactly as specified in the uploaded CSV or Excel file, eliminating one-day discrepancies caused by timezone conversion.

Passenger Import Failure When Date of Birth or Age Fields Are Empty (KT-13858)

Issue: Passenger import operations were failing when Date of Birth (DoB) or Age fields contained empty strings or null values. The system was attempting to parse empty strings as date values, resulting in "Invalid date:" exceptions that prevented the entire passenger record from being imported, even when other required fields were properly populated.

Solution: Enhanced the passenger import field validation logic to properly handle empty or blank values:

Impact:

Passenger Import Limited to 200 Records (KT-13904)

Issue: When importing passenger files with more than 200 records, only the first 200 passengers were imported with no error messages displayed.

Root Cause: The itinerary query included a Passengers__r subquery that hit Salesforce’s aggregate query row limit (200 rows) during bulk passenger inserts, silently failing the operation.

Solution: * Refactored Passengers trigger to query passengers separately from itinerary data, avoiding the aggregate query limit * Passengers are now queried independently and grouped by itinerary ID, allowing processing of unlimited passenger records * Enhanced error notifications to display success/error counts and stack traces for better visibility * Improved error handling in post-processing operations with granular exception categories * Updated notification labels to show import result counts

Impact: * Passengers can now be bulk imported in unlimited quantities (previously capped at 200) * Import failures are now properly logged and reported to users * More robust handling of post-processing failures (room assignments, configuration assignments, TBD cleanup)

Compatibility: No breaking changes. Existing imports of ≤200 passengers remain unaffected.

Configuration Assignments Preserved When Room Group ID Changes (KT-13905)

Issue: When a passenger’s room group ID was changed in the Passengers Grid, their existing configuration assignments were being inadvertently deleted. This occurred because the system was not properly marking existing configurations as selected when loading passenger data, causing the UI to treat them as unselected and removing them during updates.

Solution: Updated PassengersGridController to set passengerConfiguration.selected = true when loading existing configuration assignments. This ensures that previously assigned configurations are correctly identified as selected in the UI, preventing them from being deleted when room assignments change.

Impact: Passenger configuration assignments now persist correctly when room group IDs are modified. Users can change room assignments without losing previously configured services for passengers.

Duplicates for Passenger Configuration Assignements when you update passenger data via import (KT-13912) Issue: Passenger Configuration Assignment records were being duplicated when passengers were re-imported or re-evaluated within the same itinerary. This occurred because the system was upserting assignments without properly handling existing records, causing multiple copies of the same configuration assignment to accumulate.

Solution:

Impact: Passenger re-import and re-evaluation operations now correctly update configuration assignments without creating duplicates. This ensures accurate passenger configuration tracking and prevents data integrity issues.