Galapagos - Patch 20 (21.20)
Release Summary
Kaptio is proud to present this new Patch Release for Galapagos.
See Minor Changes and Bug Fixes for more details on the changes made.
Deployment Guide
See the Deployment Guide for changes that need to be carried out after installing.
Booking Wizard: New Save Flow (ST-591 & ST- 595)
Problem:
Currently, the system is heavily dependent on triggers and an outdated legacy library to manage business logic and data transactions. This design results in:
-
Redundant Queries and Uncontrolled DML Commits: Multiple triggers and scattered logic lead to unnecessary database queries and a proliferation of commits that are hard to track and justify.
-
Fragmented Transaction Management: Business logic is split between controllers and triggers, creating a fragmented, opaque transaction flow that makes it difficult to control and diagnose issues.
-
Maintenance and Onboarding Challenges: The reliance on a legacy framework \(often referred to as the old unit-of-work pattern or “fflib”\) adds friction to development. New team members struggle with understanding and maintaining the convoluted logic spread across various components.
These issues have made the current approach unsustainable because it increases complexity, reduces predictability, and hampers efficient debugging and testing.
Initial phase concentrated only on creating itinerary from the booking wizard.
How to enable
By default Create itinerary from booking wizard is working as before using triggers for many business logic actions. In order to enable new flow it can be done from the Kaptio Settings in the User Overrides section. It can enable both on the global organization level or per user/profile.
How it works
By default the create itinerary flow from the booking wizard is working without any changes. New save flow logic is hidden behind the user setting flag that can be enabled in Kaptio Settings User overrides section. The new flow is maintaining behavior of previous flow, it follows the same business logic but we avoid execution any business logic in triggers to gain control over execution flow. It should, iteratively provide better performance and allows to handle more data processing at once.
Minor Changes
Feature: Passenger Grid
Dont show Pax on Pax Grid if Pax are not allocated in a room (ST-348 & KAPI-2841)
This fix will now suppress cancelled passengers from the Passengers Tab.
Bug Fixes
Feature: Cancellations
Cancellation penalty is not displayed in the flow when we reduce room occupancy while processing Change Package or Departure (ST-849 & KAPI-3232)
Added Cancellation Fees to the Confirm Cancel Modal
Feature: Booking Wizard
Change Occupancy - The cancelled guest payment schedule items are selected when we select Total outstanding for payment after reducing the existing room occupancy (ST-889 & KAPI-3339)
This ticket addresses a blocker bug where cancelled guests' payment schedule items remain selectable after reducing room occupancy, causing incorrect payment calculations.
Booking Wizard Cabin Selection Component does not show cabin option (ST-1061)
In some cases, after selecting a Cabin Type in PS the available options for the that Cabin Type aren’t showing in Booking Wizard. This has now been resolved.
Search feature is currently broken in Booking Wizard in Tauck DEV (ST-1105 & KAPI-3701)
As part of continuing improvements to Package Search and Booking Wizard it was necessary to switch up the reference to the Account to use the DeveloperName rather than Name. This ensures uniqueness, but also broke the Contact/Pax search. This has now been resolved. There will be a further ticket to make this customizable in the future.
Feature: Package Search
Price lines not created when a package is unpriced (ST-945)
This ticket addresses an issue where price lines were being created for unpriced and core components that belonged to an unpriced package.
Components tied to specific departures not filtered out in package view search (ST-1028)
Fixed an issue where components in the Day2Day view in Package Search weren’t being filtered out correctly in some instances.
Feature: Tours
Tour Allocations are all allocated against one room when a child is included (ST-1039)
Fixes an issue when creating an itinerary that includes children the allocations are incorrectly all assigned to one room. Allocations are now assigned correctly.
Passengers being Allocated to more than 1 Tour Component (ST-1111 & KAPI-3724)
We fixed an error where passengers were assigned more than one tour component in error.
If a Payment is made by 1 passenger only, the grace period is applied to all passengers (ST-1042)
Previously, the 10-day grace period Cancellation fee was incorrectly applied to all passengers in the booking, even those who had not made any payments. This has now been fixed. The cancellation fee is now correctly calculated and applied only for the passenger who made the payment.