Fiji - Patch 32 (20.2.23)
Release Summary
Kaptio is proud to announce this new Patch Release for Fiji.
This Patch is intended to address minor issues with previous Fiji releases.
See Minor Changes for more information.
Minor Changes
Feature: Service Search
Stop searching for accommodation if no adult is on passenger list (CEE-114)
Stopped accommodation searches when there are no adult passengers. The Search action is now disabled on the Service Search page and on Costings (Add Accommodation) when the traveller list has zero adults, preventing errors and guiding users to add an adult first.
Change Inventory Status colours in Service Search (CEE-239)
We updated Service Search to use distinct colours for inventory indicators. This includes the Room Selection status sections (e.g., Allotment, Freesale, On Request, Closed, Sold Out, Mixed) and the Live Inventory (API) and Internal pills on results. Colours align with Builder and Booking Wizard for a consistent experience across Kaptio.
Related Support Ticket: KHELP-11045
Feature: Itinerary Builder
Change Inventory Status colours in Builder and Supplier Bookings Tabs (CEE-240)
We’ve updated the Inventory Status pills to use distinct colours in both the Itinerary Builder and Supplier Bookings tabs, making statuses like On Request, Mixed, and API/Live Inventory easier to spot at a glance. Hovering a pill now shows the full status name for clarity. Colours align with those already used on BW Options and Pre/Post Stay for product consistency.
Related Support Ticket: KHELP-11045
Feature: Booking Wizard
Change Inventory Status colours in Booking Wizard (CEE-241)
We updated the Package Search → Booking Wizard so the Status pills use distinct colours on the Options and Pre/Post Stay tabs. This makes statuses like On Request, Mixed, and API/Live Inventory easier to spot, and aligns colours with those used elsewhere in Kaptio for consistency.
Related Support Ticket: KHELP-11045
Feature: Rail
Enhance Rail Fare Matching (CEE-269)
We added a fallback matching mechanism for live Rail services in pricing and confirmations. From now on, the system can process Rail Fare overrides in cases where the ID of the selected Fare has changed, making it unavailable for exact matching. In such cases, the system will fallback to matching the user selection to the supplier’s availability by the name of the Fare, the name of the Fare Group and the Fare Class.
Related Support Ticket: KHELP-11699 & 11868
Bug Fixes
Feature: API
Retry after failed prepare_reservation request sends create_reservation instead of retrying failed request (CEE-225)
When confirming live rail services, the system previously sent a create_reservation request instead of retrying the failed prepare_reservation request. This caused predictable errors due to missing connect_booking_id.
This has now been corrected so that the retry action consistently re-sends the same type of request that originally failed (e.g., prepare_reservation, create_reservation, or confirm_reservation), ensuring proper alignment with supplier booking flows.
Related Support Ticket: KHELP-11521
gtBooking number is not displayed for non-closed amendments in allotment table (CEE-232)
Fixed an issue where non‑closed itinerary amendments in the Allotment table showed a blank booking number. Amendments now display the primary booking number with “ (Amendment)” appended (e.g., 123456 (Amendment)) for clarity.
Related Support Ticket: KHELP-11622
Connect Reservation Id erased on confirmed booking (CEE-245)
Previously, the system worked incorrectly when the live service was confirmed by different users at the same time. In this case, within a small window after successful confirmation initiated by one user, the 3rd-party supplier sends a message “Client reference is not found“ to another user. The system interpreted this response as a failed booking attempt and cleared the Connect Reservation Id from the confirmed service, thus making future cancellations impossible. From now on, the Connect Reservation Id is retained on the services in this situation. We recommend that users click the Retry button if they receive the message “Client reference is not found“ during confirmation.
Related Support Ticket: KHELP-11770
Feature: Bulk Operations
Bulk Job can’t run due to too long Job Parameters (CEE-250)
We fixed an issue where Itinerary Content Bulk Jobs were failing to save/run on orgs with many channels due to the 131,072‑character Job Parameters limit.
When the parameters exceed this limit, they are now split and stored across linked KObject records (including for scheduled jobs), while smaller payloads continue to use the standard field.
Related Support Ticket: KHELP-11659 & KHELP-11741
Feature: Itinerary Builder
Issues with 'vehicle(s)' UOM in builder and passenger allocations (CEE-255)
Resolved an issue where services with a “vehicle(s)” unit of measure incorrectly defaulted to a single passenger and restricted allocations. The system now correctly assigns passengers based on itinerary size and the Max Unit Occupants limit, ensuring allocations behave consistently with other unit types.
Related Support Ticket: KHELP-11688 & KHELP-11815
Too Many SOQL Queries when saving builder (CEE-308)
In this release, we optimised the Itinerary Save functionality and removed 5 redundant SOQL queries to reduce the amount of “Too Many SOQL Queries” error in Builder
Related Support Ticket: KHELP-12081
Feature: API
itineraryContentId is missing from p_parameters in CustomKTAgendaHandler.doAction (CEE-281)
Fixed missing itineraryContentId in p_parameters passed to CustomKTAgendaHandler.doAction during PDF generation on Itinerary Content publish. The handler now consistently receives the Itinerary Content Id, enabling Railbookers to derive stage details even when the handler isn’t instantiated from a Visualforce controller context.
Related Support Ticket: KHELP-12055