Galapagos - Patch 26 (21.28)
Release Summary
Kaptio is proud to present this patch release for Galapagos. This minor release was introduced to improve on minor issues with previous Galapagos releases. See Bug Fixes and Minor Changes for more details.
Deployment Guide:
The Deployment Guide is available here: https://www.notion.so/kaptio/Deployment-guide-for-Galapagos-12f36c78aa9080f68103fe3da8b2574e
Lapse Fields on Itinerary & Room Level (ST-1577 & KAPI-4434)
The feature introduces automatic inventory lapse functionality that allows users to release reserved or booked inventory by simply checking a checkbox field. When an itinerary is marked as lapsed, the system automatically calls an existing LapseItineraryService
to cancel allotments and free up inventory units for rebooking.
Manual steps
To enable the use of Lapse Fields functionality, ensure that system administrators manually grant Edit access to users for the following custom fields:
Itinerary Object (Itinerary__c
)
-
Lapsed__c
- Checkbox field to mark itinerary as lapsed -
LapseDate__c
- Date field automatically populated when lapsed
Room Object (Room__c
)
-
Lapsed__c
- Checkbox field for future room-level lapse functionality -
LapseDate__c
- Date field for future room-level lapse functionality
Itinerary Level Lapse
New Fields
-
Lapsed__c
(Checkbox): Default value = false. When set to true, automatically triggers inventory release process. -
LapseDatec
(Date): Automatically populated with today’s date whenLapsedc
is set to true.
How it works
Automatic Lapse Processing
When a user sets Lapsed__c = true
on an Itinerary record, the system automatically:
-
Sets Lapse Date:
LapseDate__c
is automatically populated with the current date (overrides any manually set date) -
Releases Inventory: Calls the existing
LapseItineraryService
to process inventory release -
Cancels Allotments: All related Itinerary Items with allotment inventory have their
AllotmentAction__c
changed from "Reserve" to "Cancel" -
Updates Status: Itinerary Item
AllotmentStatus__c
changes from "Reserved" to "Cancelled" -
Frees Inventory: Released units become available for rebooking on other itineraries
Trigger Logic
The lapse functionality operates through two trigger phases:
-
Before Update:
LapseDatec
field is set automatically whenLapsedc
changes from false to true -
After Update:
LapseItineraryService
is called to handle inventory release for all affected itinerary items
Field Change Detection
The system only processes lapse functionality when:
-
Lapsed__c
field changes fromfalse
totrue
-
No processing occurs if the field is already
true
-
No processing occurs when only
LapseDate__c
is modified
Room Level Lapse Data Model (Reserved for Future Use)
New Fields
-
Lapsed__c
(Checkbox): Default value = false. Reserved for future room-level lapse functionality. -
LapseDate__c
(Date): Reserved for future room-level lapse functionality.
Data Model Preparation
Field Structure
-
Fields follow identical naming and structure conventions as Itinerary-level lapse fields
-
Standard Salesforce field permissions and security model applied.
Future Implementation Ready
-
No Active Functionality: Room-level lapse fields are present but not connected to any business logic
-
No Inventory Impact: Setting room-level lapse fields has no effect on inventory or allotments
Planned Future Functionality
-
Room-Specific Lapse: Ability to lapse individual rooms within an itinerary without affecting other rooms
-
Granular Inventory Control: Room-level inventory release for partial itinerary modifications
Minor Changes
Feature: RightRez
Add TripType and segmentNumber to Tauck PNR Model object PNRFlightSegment (ST-1185 & KAPI-3785)
Added support for tripType
(OUTBOUND_TRIP or RETURN_TRIP) and segmentNumber
fields to the FlightSegment
object, aligning with data provided by RightRez. These fields are now captured from RightRez and passed through to K2M. Additionally, analysis identified further fields for future consideration: totalTaxes
, fuelSurcharges
, passengerReference
, status
, sellingExchangeRate
, and cos
(likely mapping to TauckBookingClassc
).
Bug Fixes
Feature: Passenger Grid
Edit contact link should not be clickable when the passenger is not linked to any contact at Passenger Grid (ST-1270 & KAPI-4019)
Resolved an issue on the Passenger tab where the "Edit Contact" link was incorrectly displayed for passengers not linked to a contact. Previously, clicking this link showed an informational pop-up stating that no contact was linked. With this fix, the "Edit Contact" link will no longer appear unless the passenger is properly linked to a contact, ensuring a cleaner and more intuitive user experience.
Feature: Adjustments
Adjustments always applied in the same currency as they are configured with (service price) (ST-1333)
Resolved an issue where automatic Adjustment services were not correctly converting prices when applied to itineraries with a different currency. Previously, the adjustment amount was applied using the original service currency (e.g., EUR) without conversion to the itinerary currency (e.g., USD or AUD). The system now properly converts the adjustment amount to match the itinerary currency based on the defined exchange rates.
Adjustments not impacting the Payment Schedules (ST-1555 & KAPI-4352)
Resolved an issue where negative adjustments added in the Adjustments tab were not correctly reflected in the Payment Schedule Outstanding Amount on the Payments tab. Previously, although the adjustment impacted the passenger total on the Overview tab, it did not update the outstanding payment amount as expected. With this fix, adjustments now correctly influence the payment schedule, ensuring financial data remains accurate across tabs.
Feature: Package Search
Change Occupancy/Transfer - Cabin flyout from package search result is not loading instead spinner is displayed (ST-1373 & KAPI-4100)
Resolved a bug where the Cabin flyout failed to load when accessing package search via the Change Occupancy or Transfer buttons in the Booking Overview. Previously, clicking the eye icon in the expanded search results would cause a persistent spinner to display instead of loading available cabins. This has now been fixed, and all associated cabins are correctly displayed in the flyout as expected.
Change Occupancy with Cancel and reduce room size, leading to 'Too Many SOQL Error' (ST-1527 & KAPI-4308)
Resolved an issue in the Tauck QA environment where users encountered a "Too many SOQL queries: 101" error when modifying room occupancy during itinerary creation. The error occurred after cancelling/changing occupancy and updating options such as protection plans and pre/post extensions. This fix ensures users can now successfully add changes to the itinerary without encountering query limits.
Feature: Booking Overview
Cancellation schedule modal is not opening from Booking Overview tab (ST-1550 & KAPI-4389)
Fixed an issue in Booking Overview to ensure that the Cancellation Fees modal shows when clicking the “eye” icon.
Tauck Embedded Booking Overview Actions Display Bug (ST-1568 & KAPI-4403)
Addresses an issue when opening Booking Wizard and Package Search from Booking Overview. It will now open at 100% viewport height and width.
Booking Overview - Commission amount is not displayed for Agent booking (ST-1129 & KAPI 3747)
Fixed an issue where the advisor commission amount was not displayed in the Booking Overview tab after creating an itinerary. While the commission was correctly calculated and visible in the Costings and Payments tab, it was missing from the Booking Overview. This has now been resolved, and the advisor commission amount is consistently displayed across both tabs.
Cannot read properties of undefined (activeRooms) in LwcBookingOverview (ST-1583)
Resolved an issue in Booking Overview where a Toast error is thrown if the activeRooms
property is missing. This change adds additional guarding in the event that bookingOverviewData
is missing the activeRooms
property.
Feature: Inventory
Kaptio Booking Conversion Template Flow not setup as a 'Template (ST-1563 & KAPI-4375)
Resolved an issue preventing users from opening or cloning the Kaptio Booking Conversion Template flow when deployed via a Managed Package. The flow had not been marked as a Template in the advanced settings, which restricted access to view or clone it. This has now been corrected, allowing users to properly open and clone the template as expected.