Hawaii - Minor (22.9)
Release Summary
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.
Minor Changes
Feature: Costings
Margin calculation (ST-1969)
Fixed the markup/margin calculations in costings when the setting ‘Price Lines Per Passenger’ is enabled.
Feature: Group Tour
Operational Itinerary Re-Evaluation Service (Backend) (GTT-464)
Implemented Itinerary Items re-evaluation when passengers are registered on Operational Itinerary.
Service reconversion with >= 50k price records (GTT-479)
Fixed service conversion process with prices recalculation when more than 50k price records exist.
Add several Group Tours record types support (GTT-496)
-
Remove from Packaging and Subscribers Org following Field Set GroupTravelFieldsInModal for GroupTravel__c object
-
Update all existing Page Layouts for GroupTravel__c object, add all needed fields ---
Crew requirements & passenger creation for Operational itineraries (GTT-527)
Added crew requirements cloning and passenger records creation logic when operation itinerary is created
Managing crew records in Operational Itineraries (GTT-528)
Passenger with crew member channel roles are excluded from group size calculation in Operational itinerary.
Create a new field for Channel Role (GTT-529)
Added new field IsCrewMemberc on ChannelRolec object
Re-evaluate operational itinerary when assignment "itinerary item - configuration" has been changed (GTT-554)
Added Operational Itinerary revaluation when adding/deleting Itinerary Item and when any connection between Itinerary Item and Itinerary Configuration is changed
Re-evaluate operational itinerary after room group id is changed by the user (GTT-555)
Now Operation Itinerary is re-evaluated when room group id is changed on any passenger
Add validation for existing channel roles for crew requirements creation (GTT-557)
If there is no channel role in the operational itinerary’s channel then validation is triggered
Add validations for calculate prices button (GTT-569)
Added validations for calculate prices button
Operational Itinerary Service - Improvements (GTT-548)
Operational Itinerary Service - Improvements
Add validation for Price Model deletion (GTT-583)
Added validation: Price Model can’t be deleted if there is an operational itinerary linked to the Price Model via Tour departure record.
Tour Departure - SF Inventory Support (Operational Itineraries) (KT-13414)
Prioritise Tour Departure Allotment Days for Operational Itineraries. Do not use Operational Allotment days for other types of itinerary
Tour Departure - SF Inventory Support (Operational Itineraries) (KT-13475)
For operational itinerary: first allotment related to assigned tour departure will be prefered
Show & Edit Configurations in Passenger grid (KT-13486)
Enhance passenger grid to allow manual override of configurations with room assignment updates. Adding a new configuration column on passenger’s grid (only for Operational Itineraries) to view, add, edit or remove the configuration assignments per each passenger. Additionally, when the RoomGroupId changes, the system now automatically re-evaluates room configurations and room assignments
Registering Passengers Improvements (KT-13487)
We’re introducing several enhancements to the Import Passengers process:
-
If room allocation is missing in the import data \(i.e. the "Room Group ID" field is not set in the import data\) the import process will assign passengers to rooms based on the group tour’s price model setup: If the price model is linked to a Configuration Group with a Configuration Code "A", it will read the occupancy type defined on the Configuration related to the Configuration group. The process then uses that occupancy type to assign a Room Group ID to each passenger. Note: If some passengers have the Room Group ID set in the input data, that is honoured. We’re only setting the values where it is missing.
-
It is now possible to update existing passengers by setting the passenger ID in the input data.
-
It is now possible to cancel existing passengers by \(in addition to passing in the passenger ID so they can be identified\) setting the field "Cancelled" in the input data to "true". This will deactivate all configuration assignments and, if the passenger was alone in a room, will cancel the room as well. Note: We maintain the configuration history so it can be reinstated if needed Note: By default, cancellation is only supported via the REST API endpoint.
-
If more than 270 passengers are passed to the REST endpoint, the endpoint will return an error and will not import any passengers.
-
Passengers from multiple itineraries can now be imported in the same call to the API endpoint. The itinerary ID must be set on each passenger record.
-
The default passenger \(TBD Traveller 1\) is deleted after a successful import. ---
Feature: Cabin Configuration Scheme
Generate ServiceCabinSegmentAssignments for Routed Departures (GTT-515)
When creating a Service Departure with record type "Routed Departure", the system now automatically generates Service Cabin Segment Assignments for all cabin and segment combinations. Each assignment links a specific cabin to a specific segment and is initialised with State = "Not Occupied".
Add backend logic for Cabin configuration scheme to create Service departures from Timetable creation tool (GTT-570)
Implemented query and assignment logic for the Cabin Configuration Scheme in the Create Timetable component
Add Ship/Train field to the Timetable creation feature (GTT-571)
Added the ‘Ship/Train’ input to the Timetable creation feature