Fiji - Major (20.0)
Release Summary
Kaptio is proud to announce that in this Major Release, Fiji, we have introduced the following features:
-
Passenger Grid & PGI
-
Booking Wizard - Options Tab
-
Booking Wizard - Pre/Post Tab
-
RightRez - PNR Import
-
Departure Statuses + Unpriced Packages
New Metadata
For a full overview of new metadata introduced as part of this release, please refer to our Core Data Model Changelog.
New Features
Booking Wizard - Pre/Post Tab
-
The PRE and POST tabs are essential identical, the only difference being the dates per night will be in descending order for Pre-Stay nights 1-X and in Ascending order for Post-Stay
-
A new required field called
Max Number of Nightshas already been added to the Package Component object. This field will be shown for Accommodation services ifBooking Wizard Tab = Pre Stay or Post Stayand allows users to define the maximum number of nights bookable Pre or Post package. There is also an new option (not required) to define the minimum number of nights allowed.
See UI:
Selection:
-
Irrespective of the different accommodation services available, options will be broken down by price category (Service Name - Price Category) with the configured max nights shown as individual ‘Night Rows’ in each price category section
-
When a night >1 is selected, then any remaining nights between the selected night and the start/end of the package will be auto-selected. For example, If night 2 is selected then night 1 will be auto-selected. The reason for showing nights as individual rows is to make the inventory status and available inventory to be visible for each night at a glance. This will also mirror how pre/post accommodation is added to Itinerary builder as separate itinerary lines. Kaptio still feel the UI is not optimal but there were multiple design iterations and this was the best balance we could find.
Sorting:
-
There will be one component for Pre-Stay and one for Post-Stay accommodation.
-
The component options presented under each room header will respect the occupancy of that room i.e only price categories bookable for a room will be presented to the sales agent
-
Irrespective of the different accommodation services available, available options will be broken down by price category with the configure max available nights shown as individual rows per night
-
Service ordering (different hotels) - will respect Component Service sort order in package setup
-
Price Category order within a service will respect Price Category sort order in package setup
Table Fields:
-
Hotel Name - This displays the name of the ‘Accommodation service - Price Category’
-
Number of nights - Round check box, the column naming will change to Pre-Night and Post-Night in the respective tabs
-
Status - Displays the inventory status per night with the available inventory (X) when on Allotment
-
Dates - The date of the specific night in the row
-
Details - Selecting the ‘eye’ icon will open a modal displaying the Short Description of the price category or service
Booking Wizard - Options Tab
In this Release we have introduced the Options Tab in the Package Search - Booking Wizard. This allows for Optional Components to be viewed and selected before the Package is added to an Itinerary.
How to enable:
To enable and allow for Optional Components to be visible on the Booking Wizard Options tab:
Set the ‘Booking Wizard Tab’ field to ‘Options’ on the Package Component
| To display correctly on the Booking Wizard’s Options Tab, Components should also be configured with the Selection Type set to ‘Optional’. |
If no Package components have been configured to display on the Options Tab, the Booking wizard menu will display a disabled Options tab with a tooltip/hover over stating: 'There are no services configured for this Booking Wizard tab.’
Day Ribbon
At the top of the Options screen day ribbon will display that allows you to select which day of the package you want to be displayed. The arrows at either end of the ribbon will allow to move to the next or previous day in the ribbon.
The ribbon will only show package days that contain optional components with a corresponding start day.
Options Tab Selection
The results on the Options tab populate the following information:
-
Component - This displays the name of the Package Component
-
Option - This displays the Component Options (Service Name). If a component option has one price category then only the Service Name will be shown. If there is more than one price category then this will be shown as different options e.g:
-
Cruise Protection Plan (service 1) - Gold (price category 1)
-
Cruise Protection Plan (service 1) - Silver (price category 2)
-
-
Status - This displays the inventory status e.g. Allotment, On Request, Sold Out, Freesale, Closed and Not Available, and the units available (irrespective of unit of measure) if allotment has been configured for the Service/Price Category.
| If the Inventory Status is Sold out, the passenger selection will be disabled. |
-
Details - Selecting the ‘eye’ icon will open a modal displaying the Short Description from the Service.
-
Price Per Person - When unit of measure is Person (s), the Price Per Person column will display the price associated with each component option on a per-person basis.
-
Total Price - This displays no price/no value until a selection has been made. Once selected, this will display the total price for the Component/Service.
If more than two rooms are searched for, the names of the passengers in each room will be displayed in the room header next to the room number:
Viewing and Selecting Per Person Components When one or multiple component options configured in Package/Service set up with a Price Category unit of measure = Person(s), an icon displays that indicates that the selection can be made at a person level. For example, both passengers in a room would like to do different activities on Day 8 of the Package, or maybe not everyone in a room wants the same Protection Plan.
On selection of the icon, all the component options on the component will be expanded to show all the passengers in the room.
After a passenger for a Component Option has been selected, the same passenger name will be disabled/un-selectable for the other Component options configured with a Price Category Unit of measure = Person(s)
Sorting
There are three sorts for Package Components/Services and Price categories within the Options Tab:
-
Component ordering in the UI respects the Package Component sort order in package setup.
Service ordering within a component respects the Component Service sort order in package setup.
-
Price Category order within a service respects the Price Category sort order in Service setup
Protection Plan
A new value ‘Protection Plan’ has been introduced on the Package Component ‘Booking Wizard Tab’ field. This allows for a Protection Plan/Insurance component to be included in the Options tab selection but identified and itemised as a separate row in the Booking Wizard Summary.
| "Protection Plan" must be enabled manually, see the Minor Changes tab under Booking Wizard for more details. |
Next/Back Buttons
The next/back buttons within the Booking Wizard have been updated to reflect the name of the Booking Wizard tab instead of Next and Back, e.g. when the Options tab displays, the back button will display ‘Select Cabin’, and the next button will display ‘Pre Stay’.
Booking Wizard Summary Changes
The Booking Wizard Summary has been updated to show the Price Per Person, Quantity and Total Price per tab (Options, Pre Stay and Post Stay) that have any prices associated with them. Passenger names will display under the tab name when passengers in a room have made different selections in that tab.
| The summary will not display rows for tabs with no prices. |
Departure Statuses + Unpriced Packages
Departure Status In prior cycle we had implemented a Departure Status field on the Package Departure object, however in this cycle we have changed the available values in this field slightly so the available values are; Unopened, Open, On hold, Cancelled. Custom values can be added.
In addition we have introduced a Booking Eligibility field to the Package Departure object, with the following values; Bookable, Visible Only, Inactive.
-
Departures with Booking Eligibility = Bookable can be seen and booked/added to itineraries from Package Search
-
Departures with Booking Eligibility = Visible Only can only be viewed in Package Search and not added to itineraries.
-
Departures with Booking Eligibility = Inactive are not visible in Package Search.
In addition to these fields being delivered we have a flow "Setting Booking Eligibility based on selection in Departure Status” which sets the Booking Eligibility value based on what the user selects as a Departure status. The out of the box flow can be inactivated and another version created to account for any custom values in Departure Status field. But the OOB flow will map the fields according to the table below:
In addition to showing the Departure Status in Package Search we now also display an overarching Inventory Status for the departure, taking into account the different components which require inventory within the package. This means users sees the same pattern in package search as they will see for each service in builder / bookings to distinguish whether the package has available inventory or is on request. Where on Allotment, or ‘AL’, here would mean that all components which require inventory have inventory. While the departure would show On Request as soon as at least one component that requires inventory has an ‘RQ’ or On Request status.
How to Enable
As we’ve changed the values slightly for Departure Status field which does not affect orgs with the Kaptio Travel package already installed. Therefore, we recommend updating the values to the following; Unopened, Open, On Hold, Cancelled, and in addition you can add custom values such as Call to Sell.
Unpriced Packages
On the Package object we have introduced a new checkbox called ‘Unpriced’. The checkbox is located at the bottom of ‘Edit Package’ modal.
If ‘Unpriced’ is checked for a particular package, we show a ‘Unpriced’ label in the price summary in package search expanded details as shown below:
When users enter the booking wizard they will see an alert the ‘This Package is unpriced’ in the price summary and no prices will be shown and ‘Unpriced’ label shown instead.
Unfortunately due to dependencies on work for Options tab and Pre/Post tab we have not yet implemented the support for Unpriced there. Hence ‘Unpriced’ label will not yet be shown in those tabs.
New Enhancements
Passenger Grid & PGI
Passenger Grid - Overview
The Passenger grid is now split into three sections as per the picture below:
Passenger Grid - Section 1
Passenger Grid - Passenger row
When managing passenger information in the Passenger Grid (Section 1) you can view individual rows for each passenger associated with the booking and see columns representing fields on the passenger object as defined in the field set. This allows the user to efficiently manage passenger information by manually entering placeholder data initially if desired (with the ability to subsequently link each passenger to a Salesforce contact ), ensuring that all passenger details displayed will meet the needs of the organization.
JSON configuration to customize fields
Included in this feature is the possibility to enhance the functionality of the passenger grid beyond the configurability offered by the field set configuration by accessing and modifying the JSON configuration in the App Builder. When used this the sole configuration method used for the passenger grid. This does allow the user to add on top of the core configuration functionality offered by the field set configuration and customize the grid more extensively, such as setting which section specific fields display in and ensure fields display as ‘required’, read-only or editable, with custom rendering behaviour so that the passenger grid meets the specific needs of the organization.
JSON Config guidance:
The JSON config field in App Builder appears in the side pane:
-
To add or remove fields from Sections it is needed to modify corresponding list of fields.
-
Section 1: row →
fieldSet -
Section 2:
expandedRow→pgi→fieldSet -
Section 3:
additionalRow→fieldSet
-
{
"grid": {
"areRowsExpandable": true,
"areRowsSelectable": false
},
"row": {
"fieldSet": [
{
"label": "Salutation",
"fieldApiName": "KaptioTravel__Salutation__c",
"isEditable": true,
"isRequired": false,
"customComponent": {}
},
{
"label": "First Name",
"fieldApiName": "KaptioTravel__FirstName__c",
"isEditable": true,
"isRequired": false,
"customComponent": {}
},
{
"label": "Last Name",
"fieldApiName": "KaptioTravel__LastName__c",
"isEditable": true,
"isRequired": true,
"customComponent": {}
},
{
"label": "Email",
"fieldApiName": "KaptioTravel__Email__c",
"isEditable": true,
"isRequired": false,
"customComponent": {}
},
{
"label": "Gender",
"fieldApiName": "KaptioTravel__Gender__c",
"isEditable": true,
"isRequired": false,
"customComponent": {}
}
],
"showStatus": true,
"showAssignContactButton": true,
"showEditContactButton": true,
"additionalFieldsToQuery": []
},
"expandedRow": {
"pgi": {
"fieldSet": [
{
"fieldApiName": "KaptioTravel__TotalSell__c",
"isEditable": false,
"customComponent": {}
},
{
"fieldApiName": "KaptioTravel__Nationality__c",
"isEditable": false,
"customComponent": {}
}
]
},
"additionalRow": {
"fieldSet": [
{
"label": "Birthdate",
"fieldApiName": "KaptioTravel__DateOfBirth__c",
"isEditable": true,
"isRequired": true,
"customComponent": {}
},
{
"label": "Middle Name",
"fieldApiName": "KaptioTravel__MiddleName__c",
"isEditable": true,
"isRequired": false,
"customComponent": {}
}
]
}
}
}PGI status icon
As part of section 1 of the passenger grid an status icon has been added at the right end of each passenger row so users can immediately determine at a glance whether all mandatory fields have been completed without needing to extend any passenger rows. Mandatory fields are defined on a Org level.
Link Button & Search/Create Contact
To make it simple and easy to add a passenger to a booking we have built a sync between Salesforce contacts and the passenger grid. At the end of each passenger there is a Link/Linked button. When clicked this launches an existing Search/Create contact modal. In the modal user is presented with a list of the household accounts (and their contacts) related to contacts already linked to passengers in the grid. This modal allows users to search for existing Salesforce contacts if still required, create a new contact in the ‘Create Contact’ tab if still required and link contacts found/created through any of these steps to the passenger using an ‘initial linking’ in-memory flow that is invoked upon selecting ‘link’ or ‘Save’ respectively.
Edit Contact
Above we talked about the Link/Linked button which syncs informations to a salesforce contact. When a passenger is linked the “edit contact” button needs to be used to edit information. By clicking the button a modal will pop-up allowing users to edit informations shown in the passenger fields of sections 1 and 3 by performing edits directly on the salesforce contact. When editing and saving the changes they will automatically sync back to the Passenger Grid (in memory).
Manage Itinerary Groups
User will see a button in the UI "Manage Itinerary Groups" in the Passenger Grid. Clicking this button a modal 'Manage Itinerary Groups' is launched with existing functionality (adding group names). In the modal a new button has been added allowing the user to automatically create itinerary groups per room group ID in the booking where each room’s passengers are grouped together, with the primary passenger being the first listed in the passenger grid for that room, and the group named accordingly (e.g., "Room 1", "Room 2").
Passenger Grid - Section 2
Booking PGIs
By clicking the arrow at each passenger row allows the row to expand to access Section 2 (see picture above). This section is for the user to manage information that is specific to and required by the booking (known as Booking PGIs). Here all the fields required by the PGI by each customer have been configured to their needs to ensure that all necessary booking-specific information is captured according to the requirements of the booking
Passenger Grid - Section 3
Section 3 additional passenger information and preferences
In this section user can manage additional passenger details and preferences that are not covered in the primary contact information (Section 1) or booking-specific information (Section 2). This section requires an administrator to configure which OOTB and/or Custom passenger fields should display in Section 3 using the JSON configuration in App Builder and for the OOTB Fields to sync from the Salesforce contact upon initial linking and update the contact when edits are made. Once this is done and some informations are entered the additional passenger information and preferences will be stored on the salesforce contact according to the preference of my organisation.
Configuring Passenger → Contact and Contact → Passenger Flows
When a passenger is linked to a contact, the mapping of fields between Contact and Passenger objects is controlled using flows
-
These flows are configured in Kaptio Settings > PGI settings:
-
The ‘Non-Updatable Passenger Fields’ field allows you to define the API names of fields on the passenger object that should not be updated when the Contact → Passenger Flow is triggered. Here is an example of the field input:
-
KaptioTravel_FirstName__c;KaptioTravel_LastName_c;
-
For both of the flows, Flow builder can be used to configure the mapping of fields between the Passenger and Contact objects:
RightRez - PNR Import
Work was completed on importing PNRs provided by RightRez into Kaptio Travel. This work was done on an API level with no changes to Salesforce in this cycle. Testing this can be done by creating a PNR within RightRez and using the manual PNR import in Itinerary Builder to add the PNR. This process will be automated when the Shop RightRez Flight will be implemented in Cycle 5.
Bug Fixes
Feature: Package Search
KAPI-1057: The dropdown lists in the Package Search expand beyond the available screen width, causing them to be partially hidden
We fixed an issue causing dropdown lists to expand beyond UI limits, obscuring the content of the lists. Now, dropdown lists are configured to remain within the visible UI.
KAPI -1080: Package Search: Sort by Price in Results view is not working as expected
We fixed an issue where Package Search was not correctly sorting by the applied filters.
KAPI-1082: Package Code search should NOT be case sensitive
We fixed the Package Code field so that it is no longer case sensitive.
KAPI-1214 Package Search: day-by-day does not match the package start date
We fixed an issue where the dates would not match in Package Search, with day-by-day dates being one day before package start date. Now, these dates are accurate.
Related Support Ticket: KHELP-10441
KAPI-1223: Cruise Price summary - Able to unselect all cabin categories for a room
We fixed an issue where users were mistakenly able to unselect all cabins in Booking Wizard.
KAPI-1225: Cruise Price summary-Incorrect Default Price Selection, currency and Total Amount when only one category is available
We fixed an issue with the Summary Price in Package Search where the price would occasionally display incorrectly.
KAPI-1272: Delay in Price Summary and Day-by-Day appearing
We improved response speed on the Package Search UI.
KAPI-1363: Able to create Itinerary when a package departure is in past date
We fixed an issue that allowed users to create Itineraries for Package departures in the past. Now, itineraries may not make Package departures in the past.
KAPI-1349: Package Information not displaying from the Availability Tab
We fixed an issue where the Package information modal was not displaying on the Availability Tab of Package Search.
KAPI-1390 Able to select cabin with no availability
We no longer allow users to select cabins with no availability. Previously, users could select unavailable cabins in error.
Departure Type filter dropdown is overlapped with the fixed top bar in Package Search availability screen
We fixed a Package Search UI issue where the fixed top bar was being overlapped by the Departure Type filter dropdown.
Package Search: fix top bar when scrolling
In Package Search, we fixed an issue where the UI hid the date when scrolling away from the top of the screen. The date is now always visible on this screen.
When hovering over a date on Package Search, date does not match with the date in the header
We fixed an issue where the hover display was showing the incorrect date in Package Search.
Unable to launch Booking Wizard from Account/Builder
We fixed an issue where Booking wizard was unable to start when launched from an Account.
Component error thrown when accessing Package Search from Trip using the button
We fixed an issue which prevented launching Package Search from Trips.
Package Information Modal in Package Search > Results Screen Does not Work Correctly.
We fixed an issue that prevented the Package information modal from working as intended.
Results screen displays all Packages instead of the selected one from the Availability tab
We fixed an issue where the Results screen in package search would show too many packages after users made a selection in the availability screen.
Feature: Itinerary Builder
Inconsistent input box rendering in Itinerary Builder when opening days
We fixed an issue where the day input in builder was being inconsistent and causing problems for users.
Related Support Ticket: KHELP-9330
QTY column in Itinerary Builder is over allocating
We fixed an issue where the Quantity column in Itinerary builder was incorrect.
Service Departure Date showing incorrect year
We fixed the year format, due to an error where some entries would show the wrong year in some cases.
Related Support Ticket: KHELP-8238
Location not populated on package itinerary items
We have fixed an issue where the Location field was not populated when adding a package from package search.
Related Support Ticket: KHELP-10806
Component error in costings when editing price category
We fixed an error in costings when editing the Price Category.
Related Support Ticket: KHELP-10601
Order of locations in builder
We fixed an issue where, when searching, the Itinerary Builder displayed locations illogically.
Matches would appear alphabetically, but without placing the exact match at the top of the results. Now, exact matches have a priority over alphabetical matches.
Related Support Ticket: KHELP-10644
Too many inclusion records cause error in builder
We fixed an issue where a "Too Many Rows for direct Assignment" error would be thrown under some circumstances in Itinerary builder.
Related Support Ticket: KHELP-10734
Quick save in builder leads to missing inclusions
We fixed issue where saving itinerary in builder before price load caused missing inclusions.
Related Support Ticket: KHELP-10569
KAPI-1155: Changing dates for Services that have 'Day Use' Flag should allow the user to use the calendar to set the date
We fixed an issue where the calendar in Itinerary builder would not be usable for changing dates of services with Day Use flag set.
SupplierInvoicesTab.BulkAllocation button
We have added additional filter fields to the Supplier Invoices Tab.
Feature: Payments
When creating/editing Itinerary Payment Schedule rules - users should not be able to define negative numbers
Users are no longer able to define negative numbers when creating/editing Itinerary Payment Schedule rules when value type is set to percentage.
Selection dropdown stays open in module New Payment Schedule Assignment
We fixed an issue where UI dropdowns were not closing when expected.
Feature: Booking Wizard
Assign Household does not appear in Search/Create Contact in Booking Wizard
We fixed an issue where the Assign Household button would not appear correctly.
Feature: Documents
Document Persistence: Remove date logic - CPU Issue fix
We identified and fixed an inefficiency in the document persistence code and corrected. Additionally, we removed the ability to edit date, time and order fields in document agenda items.
Javascript error when downloading PDF from webquote in iframe
We fixed an error that would be thrown when downloading a PDF from an Iframe.
Related Support Ticket: KHELP-8180
Feature: Cruise
When adding a Package to an Itinerary, it does not show in Builder immediately
We fixed the UI to update more frequently when adding Packages to the Itinerary.
Feature: Service Search
Featured image for internal Service in Service Search
We can now select featured images in Services to be displayed in Service search.
Related Support Ticket: KHELP-10577
Service does not appear in Passenger Allocations
We fixed an issue where a Service would not appear in the Passenger allocation screen under some circumstances.
Related Support Ticket: KHELP-10823
Feature: Costings
Columns on Costings screen are not switching
We fixed an issue that stopped column switching in Costings from working as intended when Lightning Web Security was turned on.
Related Support Ticket: KHELP-10627
Costing Page Scrolls to the top when making changes
We fixed an issue with scrolling in Costings.
Related Support Ticket: KHELP-9612
Feature: Front End
Calendar modal becomes invisible when selecting Travel Dates for Service Notes.
We fixed an issue where the calendar was being obscured in Service Notes.
Related Support Ticket: KHELP-9641
Feature: Supplier Action
HTML code on Supplier Action page instead of proper formatting
Format on Supplier Action screen no longer shows HTML code.
Related Support Ticket: KHELP-9613
Feature: Package Editor
Package Clone does not show errors occurring in back-end
We fixed an issue where errors would not be displayed during a Package clone.
Related Support Ticket: KHELP-10527
Feature: Content
Site guest user cannot change Itinerary status via action buttons in Content
We fixed an issue where the Site guest user was unable to interact with buttons in Content documents.
Related Support Ticket: KHELP-10540
WETU Location Content not loading from its own location
We fixed an issue where WETU Integration in Itinerary Builder was using the Itinerary Item Location rather than Service Location when adding location content in Itinerary Documents.
Minor Changes
Feature: Package Search
KAPI-1073: Multiple Package code search does not display an appropriate error message
We added the error message Multiple Package Codes cannot be searched for, which appears when trying to search for more than one package code.
Departure hover heading should be smaller
We slightly adjusted the size of the Departure hover menu in the Package Search UI.
Remove placeholder text from Package Search expanded results
We removed some unnecessary placeholder text from the Package Search UI.
Remove initial Package Search search
On opening and loading the initial screen, Package Search would run automatically causing long loading times. This is no longer default, and the option can be controlled via the Lightning Component settings.
Related Support Ticket: KHELP-10611
Feature: Booking Wizard
Update lwcBookingWizardAddPrimaryContact to allow custom flowApiName to be passed in via. Lightning App Builder
We added a way for users to configure a custom flow to be executed in the booking wizard.
Update the 'Next' and 'Back' buttons to display name of the actual next and back tabs
The next and back buttons in Booking Wizard now show the name of the tab they lead to.
Itinerary Builder
Preview service content in builder
We added a service content preview in Itinerary Builder.
Related Support Ticket: KHELP-10608
Tour Departure object & tab
Created a Tour Departure object and customized the Group Tour (previously Group Travel) object record screen to include a Tour Departure tab.
Change colour of CNN badge to green
We changed the colour of the CNN (Confirmation Not Needed) badge for the confirmation status from red to green in the Builder and Supplier Bookings. This is to more clearly indicate that users do not need to take anymore action on the Bookings in question.
Related support ticket: KHELP-8561
Calculated Total Price on itinerary items in Cancellation mode
Services in Cancellation mode were generating suggestions using full cost for the minimum and maximum sell price.This resulted in the Itinerary Price Breakdown screen displaying the incorrect suggestions.
Now, the cancellation fee is used in calculations for such services.
Related Support Ticket: KHELP-10473
Feature: Payments
Change colors of buttons
In order to match the UI style of other Kaptio elements, we adjusted the colour of our buttons in the UI in Payments. Now, the overall UI is more cohesive when using the payment feature.
Feature: PNR
Make Booking Source field blank when importing PNR and force user to select one deliberately
We made the Booking Source field in the PNR Import screen empty by default. The Retrieve button will now remain inactive until Booking Source, PNR Code, and Price Category fields are filled, in order to prevent import errors.
Related Support Ticket: KHELP-9252
Feature: Cruises
Cruise price summary - UI should disable selection of cabin type when inventory is used up in previous selection
In the scenario where more than one room or cabin is requested, and selecting a cabin type reduces the available units to zero, the system now prevents users from selecting the same cabin type for the other room / cabin in the search.
Feature: Content
Improve the default order of destination content in the Itinerary content wizard and content output
We have changed the ordering hierarchy of destination content in Itinerary Content. When viewing the destination content within the Itinerary Content, the information now follows a country ⇒ state/province ⇒ city/town hierarchy.
To demonstrate, if a client has an itinerary with services in the following sequence:
-
Melbourne
-
Sydney
-
Perth
-
Bangkok
The display will default to this order:
-
Australia (country)
-
Victoria (state)
-
Melbourne (city)
-
New South Wales (state)
-
Sydney (city)
-
Western Australia (state)
-
Perth (city)
-
Thailand (country)
-
Bangkok (city)
Related Support Ticket: KHELP-10425, KHELP-10301, & KHELP-10333
Feature: Service Search
Show Accommodation Star Rating on the Service Search Results
Service search now shows the accommodation star ratings.
Related Support Ticket: KHELP-10609
Auto Select Train when a different fare class is selected
We have added a feature to automatically select the train when a different fare class is chosen in Rail Service Search.
Related Support Ticket: KHELP-10619