Fiji - Patch 33 (20.2.24)
Release Summary
Kaptio is proud to announce this new Patch Release for Fiji.
This Patch is intended to address minor issues with previous Fiji releases.
See [Minor Changes] for more information.
Minor Fixes
Feature: Service Search
Pass specific age of passengers to search for accom (same as rail) (CEE-113)
We have updated the logic to fetch adult ages from the passengers list.
Feature: Rail
Implement hotfix for distinguishing Inline vs Predefined Manual Rail records (CEE-270)
The price category display for Manual Rail itinerary items has been enhanced to show information from different sources based on the item’s configuration:
-
Predefined Manual Rail items: Display the external name from the price category popover
-
Inline configured Manual Rail items: Display the first fare class of the first segment
Important Note:
The "Source Manual Rail Service" identifier is used to detect inline-configured rail items. This identifier must remain unchanged to ensure proper classification of existing inline manual rail configurations.
Related Support Ticket: KHELP-11962
Feature: Itinerary Builder
Patch Apex heap fix from CEE-53 to 20.2 (CEE-301)
We have resolved a critical issue where users encountered “Apex Heap Too Large” errors when opening the Price Category popover for services with a large number of location junctions (e.g. rail services or car rentals with extensive primary location mappings).
Related Support Ticket: KHELP-10621
Feature: API
Show errors from API in the error toast (CEE-254)
To enhance troubleshooting and customer support, detailed error information from the KT API will now be clearly displayed in error messages within the application interface.
Previously, error messages lacked specifics, requiring manual retrieval from debug logs. Now, when API errors occur, the toast notifications will clearly display relevant details, including error codes, descriptive messages, and session identifiers (if available). For example:
Something went wrong while connecting to an external supplier. An error report has been sent to us. Please retry your recent action and open a support ticket if the error appears again. Code: 3000 Message: The request was not able to produce a result Details: Caught a generic exception: The following requested customer_id(s) do not exist: 101GA00004xk9mkYAA.In case of API timeouts, a clear notification indicating the timeout event will be shown:
Something went wrong while connecting to an external supplier. An error report has been sent to us. Please retry your recent action and open a support ticket if the error appears again. Response timed out. No response from KT API within a configured timeout.These improvements facilitate quicker diagnosis and resolution of issues, significantly reducing the reliance on support requests.
Related Support Tickets: KHELP-10787 & KHELP-11060
Bug Fixes
Feature: Rail
Departure/arrival location dropdowns cut off (CEE-253)
We have updated the UI to fix a cut off in the departure/arrival location dropdown list.
Related Support Ticket: KHELP-11296
Rail Search: departure/arrival aren’t allowed to be the same locations (CEE-310)
Previously, the system did not allow selecting the same train station for both departure and arrival locations when searching for live rails. For users shopping multiple rail trips, this behaviour was inconvenient because they were forced to clear both location inputs before starting another search. From this release, the restriction is lifted, allowing for faster operation for users. Also, we added a button to swap departure and arrival locations to make the search more convenient.
Related Support Ticket: KHELP-10694
Feature: Itinerary Builder
Error message when user interacts with "Skipped" status of itinerary item (CEE-268)
Fixed condition brackets for Skipped status.
Related Support Ticket: KHELP-12150
Patch KT-9775 into Fiji 20.2 (CEE-300)
We have fixed an issue that caused too many soql queries on the itinerary content table.
Related Support Tickets: KHELP-10957
c.LwcHelpers is not a constructor (CEE-339)
We fixed the error "c.LwcHelpers is not a constructor" that was occurring on some services in the builder after bulk moving their dates.
Related Support Ticket: KHELP-12134