Galapagos - Major (21.0)

Kaptio is proud to announce that in this major Release, Galapagos, we have added the following features: * Change Package Occupancy - Add Rooms * Voucher Management - Vouchers as a payment method * Kaptio Auto Pay * Generation of Itinerary Payment Schedule Rules Known Issues * **KT-11222**: When there is more than one Payment Schedule Configuration for the same item (Service, Package, Account, Channel), and the second one is more complex than the first; A user adding an itinerary item with both items assigned (as in the 2nd Configuration) will not cause the more specific/complex Payment Schedule Configuration to take precedence. I.e. the itinerary will not receive payments schedules from the 2nd, more complex, configuration. The complex one taking precedence is the expected behaviour, but is not yet enacted. * **KT-11204**: When an Itinerary has 2 pax Itinerary Account, a Payment Schedule Configuration, a Payment Schedule Configuration, and is set to\`PPP \= True\`; * First, a user adds and saves an itinerary item (service) to the itinerary in Builder with no related Payment Schedule Configuration. * Second, the user clicks on the newly saved service line in Builder, and changes the service to a service WITH a related Payment Schedule Configuration and save. * Rather than saving a new service with a related Payment Schedule Configuration, the system returns Error! KaptioTravel\:Too many SOQL queries: 101. * **KT-11414**: When the new payment schedule engine is active, and and exists with deposit and balance payment schedules; Creating a new manual balance payment schedule where the date is either the same or later than the balance payment schedule will cause the new balance to delete and throw no error. The expected result is the schedule not saving and throwing one of two errors: * Error! Only 1 balance rule is allowed per itinerary (when PPP \= False). * Error! Only 1 balance rule is allowed per passenger (When PPP \= True). * **KT-11440**: When the new payment schedule engine is active: * There is a Payment schedule configuration (here called A) with one assignment, with the following combination assigned: * A Service (B) * A Package © * An Account (D) * A Channel (E) * There are the following stand alone records (with no payment schedule configurations assigned to them): * A Service (F) * A channel dependent Account (G) Then completing the following actions: * Creating an itinerary with account G, channel E, and service F. * Changing the itinerary account to account D. * Adding service B to the itinerary, then assigning it to all pax. * Deleting service B from the itinerary and adding package C to it, then assigning it to all pax. Will not create the expected payment schedules from the source channels, accounts, and services. :::note This is not the case in the fourth scenario. This scenario generates the payment schedules from package C. ::: * **KT-11445**: On an itinerary with 2 or more pax, and has assigned a payment schedule to a service which has two price categories the following process; * Adding both price categories to the itinerary. * Allocating them both to the 2nd pax using the payments tab. * Adding a manual payment schedule with the earliest due date. * Will not display the correct Payment Schedule Configuration, rather price\=0. * **KT-11485**: In the Scenario: * There is a a Package and Account with their own separate Payment Schedule Configurations assigned. * There is also an itinerary with 2 or more pax which was created from the Package and using the Account. * The following action: * Manually creating deposit payment schedules for all passengers. * De-allocating 1 or more passengers from the package items in the Package. * Will not generate the Schedules from the Account on the de-allocated passengers, as expected. * **KT-11552**: When an itinerary has 3 passengers in 2 groups (1 group of 2, and another of 1), who are assigned to an item with a max occupancy of 4, some payment schedules generated from an Account/Channel, and Enable Passenger Payments \= True; Adding a new passenger to the itinerary, without allocating them to a either group, then going to the Payments tab will create and save the new passenger, the cause an error on the tab. Expected behavior is throwing a Warning! Following Passengers are not assigned to any of Itinerary Groups: \[Passenger Name]. Please add them to an existing Itinerary Group or create a new group for them. error in the payments tab. The Passenger may still save. * **KT-11696**: The functionality to generate itinerary payment schedules which use the due dates from Package Departure’s Payment Schedule Rules has not yet been implemented. ### Deployment Guide: The Deployment Guide is available [here](https://releases.kaptio.com/releases/guide-galapagos/). ### New MetaData For a full overview of new metadata introduced as part of this release, please refer to our [Core Data Model Changelog](https://docs.kaptioapis.com/kaptio-travel/-/changelog).