Eiffel - Major (19.0)

Release Summary

Kaptio is proud to announce that in the Eiffel release, we have introduced two new features: a new Payment UI and the Pay per Passenger feature. Additionally, we’ve made many enhancements to Package Search.

Release Type

Major Release

Deployment Guide

The Deployment guide is available here: https://kaptio.notion.site/Deployment-guide-for-Eiffel-93ef82a0d2434d81af53d090f065412a

Sandbox Availability Date

2024-03-04

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

New Payment UI

In this release we introduce a new user interface for our payment screen. In addition to implementing a new design for the screen, we have also reduced the steps it takes to make a payment by combining the payment screen and Make payment model together into the same screen. As a result the user has an overview of the payment schedule and outstanding amounts while making the payment, as well as visual indicators whether a payment schedule has been made.

How to enable

For our customers who already use our payment Lightning Web Component, there’s no action required to enable the new UI. However, in order to be able to use the 'View More' option to view all payments made for the itinerary please add the Payments related list to all of your relevant itinerary page layouts.

If the Kaptio Page Wrapper is currently being used to display the Payment tab in your org, you can replace it with a component called Lwc Itinerary Payments within the Payment tab on your Itinerary Page (this is done in Lightning App Builder).

Pay Per Passenger [Pilot]

Pilot Feature. Contact your Customer Success Manager to ask for assistance

In this release we introduce a pilot version of our Pay per passenger feature. When the pay per passenger feature is enabled for an itinerary, it creates a payment schedule for each passenger and allows the user to either enter a manual amount to be paid per passenger or select payment schedule rule(s) for each passenger to be paid. As a result the user knows exactly how much has been paid and how much is still due for each passenger.

How to enable

In Setup → Custom Settings → App Settings you’ll find a checkbox called Enable Pay per Passenger. **To enable passenger payments in your org, make sure that checkbox is checked. In addition, you have the ability to configure at Channel level as well as Account level whether passenger payments should be enabled or not. For example, you could enable it for your FIT channels, but keep itinerary payment schedules for your group channel.

So after you’ve enabled Pay per Passengers in App Settings, head to your relevant channels and to the Payment Schedule Rules tab and check Enable Passenger Payments.

Last but not least, for your Travel Agent accounts, which have their own Reseller Payment Schedule, edit the schedule and make sure to check Enable Passenger Payments there as well. If your Travel Agents have a Channel dependent payment schedule, no action is required.

New Enhancenments

Manual Rail Amendments

In the Colosseum Release, we introduced the Manual Rail Feature. We’ve now enhanced this feature in the latest release, allowing Manual Rail and Pre-defined Manual Rail services to be bulk moved, have their day changed, and be dragged and dropped within the Itinerary Builder to alter dates. This enhancement would only apply to Manual Rail services that have an 'Unconfirmed' confirmation status.

Feature: Manual Rail

Custom Commission Calculations

We have improved the implementation of specifying custom commissions on Itinerary Items. Previously, the Commission Group could only be selected for the custom Itinerary Items. Starting from this release, the Commission Group can also be specified for the standard Itinerary Items so that custom reseller commission can be applied to them.

Feature: Itinerary Items

Package Search - Availability Screen improvements [Package Search Pilot]

Part of Package Search Pilot - Colosseum Minor 1. Contact your Customer Success Manager to ask for assistance.

In this release we have also made changes to our availability screen in package search with the intent to help users to quickly identify the most suitable package departure/date at glance. The following changes have been introduced:

It can now be configured whether the default results screen is the Overview screen or Availability.
Lighter monthly calendar with dashes on the dates with no departures.
Package code precedes Package Name when active on a package.
Service levels field in search panel and results is only show when active in an org. Otherwise days/duration field is shown by default.
Icons can be configured to show if package is primarily on Land (map icon) or Water (Boat icon).
Departure Type filter which allows users to filter the search results based on Departure Type. This is only applicable for packages with Package Departures. Drop down will display all departure types available in the org.
New legends added to show the meaning of each.
Sorting ability has been added. Users can now sort based on the following:
- Availability High-Low, Availability Low-High
- Duration High-Low, Duration Low-High

How to enable:

To configure what icon should be displayed for each package you can use the field

+ Package Type Icon on the package object and add the name of any of the custom icon shown here.

+ * Currently Package Search defaults to the Overview/Results screen. If you would like to configure the availability screen to be the default you can do so by following these steps: ** Go to Setup → Lightning App Builder → find the Package Search app page, Clone the page and edit your newly created Package Search page.

When you have the new Package Search page open, click on the Package Search component and you should see the options on the right hand side as shown on the picture above.
Change the Default Tab to Show to Availability.
Additionally you can set the Departure Selection Behaviour to either Open Expanded Details if you’d like to be able to expand on departures/dates in the availability ribbon or Navigate to Results Tab.
Save and Activate the page.
Please note, in order to use the Package Search lightning page just created you will need to create a flow that uses this new page and associated button. For more information on this, please refer to our release notes for Duomo Minor 1 → Launch Options for Package Search. A Community article on this topic will be following soon!

Package Search - Availability Screen - Expanded Details [Package Search Pilot]

Part of Package Search Pilot - Colosseum Minor 1. Contact your Customer Success Manager to ask for assistance.

In addition to availability screen improvements we have added the result details to the availability screen with some improvements. This is especially applicable for packages with package departures. The following enhancements have been introduced:

Indicator of Available / Total passengers for a given departure. Please note, at the moment the Total number is a placeholder and will not reflect the actual total number allowed for the departure, to be added in our upcoming releases.
For Travel Dates we now show both From and To date for package start and package end.
A placeholder section for Package Notes - Stay tuned for our upcoming releases to see Package notes rendered here.
Activity and Minimum Age shown for each package.
If a cruise service is included in the package we show the ship name.
A new Cruise Price Summary
- Which shows prices for each Cabin Type available for the package
- Availability is shown for each Cabin Type to give users insights in the available spots for each Cabin Type
- The pricing shown respects the room configuration searched for.

Package Search - Search Panel improvements [Package Search Pilot]

Part of Package Search Pilot - Colosseum Minor 1. Contact your Customer Success Manager to ask for assistance.

We continue to evolve our Package Search pilot. In this release we introduce a new design and color palette for our Search Panel. Along with a new look we have made the following improvements:

Ability to search by Package Code. The field will require minimum of two letters and searches with a ‘contains’ criteria.
A change was made so that an OR relationship is present between Package Name and the newly introduced Package Code field.
Ability to search by Activity Level, which is a multi pick-list and an OR relationship will be present if more than one value is selected for search.
A change was made to the date range field so that when a From date is picked the To date will auto-set to the last day of the month, which can be overwritten as needed.

Data Model Changes (Reserved for Future Use)

In this release, we are introducing new metadata related to several areas of the platform which will enable new functionality that we will be introducing in upcoming releases. This metadata will be introduced and only available to design partners for this feature. If you are not one of the design customers for the feature, no action is required.

For a full overview of new metadata introduced as part of this release, please refer to our Core Data Model Changelog.

Bug Fixes

Amadeus PNR Import: null input to JSON parser error

Resolved the issue of null input to the JSON parser when performing an Amadeus PNR Import.

Feature: PNR

Related Support Ticket: KHELP-10013, KHELP-10392

Package Editor: Categories field not showing existing values when editing package

The ‘Categories’ field on the Package Editor page now displays existing values when a package is being edited.

Feature: Package Editor

Related Support Ticket: KHELP-10385

Unable to add KaptioTravelMinOccupancyc to Price Categories Fieldsets

We have fixed the issue where users where unable to add the Min Occupancy fields to any Price Category field set.

Feature: Services

Related Support Ticket: KHELP-10477

The Wetu refresh and update notification also displays for non-Wetu content

We have fixed an issue where the notification for refreshing content from a third party would appear incorrectly.

Feature: Content

Refresh and update notification and content update fail when logged in as a Sales Agent

We have fixed an issue where the notification wouldn’t appear when refreshing content from third party.

Feature: Content

Error when adding Category to Package Search criteria

We’ve fixed an issue that caused an error when selecting a category in the Package Search filter. This error only occurred when Package Search was accessed from an Account/Contact.

Feature: Package Search

Package Search Panel - Package Name and Package Code, OR relationship

We fixed an issue so that the current behaviour is an OR relationship between Package Name and the newly introduced Package Code field.

Feature: Package Search

'Clear All Filters' not clearing Package Code from the search criteria

We resolved an issue to ensure that using 'Clear all Filters' in the Package Search also clears the Package code field.

Feature: Package Search

Minor Changes

Copying sell price of removed FPH to imported PNR (back-end)

We resolved an issue where the reseller commissions of FPH were not copied to the PNR flight. Now during PNR import, the price category itinerary service gets the price from the price category FPH. Additionally, the add-on itinerary service adds up all other itinerary services' prices from FPH.

Feature: PNR

Related Support Ticket: KHELP-9287

Check for new content when creating a document

In this release we have added a new enhancement to the Wetu integration. Once you create a new document that contains content records which are linked to Wetu, we will check for a newer version of the content than the one Kaptio Travel has stored. If there is a newer version of the content available, it will be automatically fetched and updated before the document is created.

Feature: Content

Max number of rooms restriction in Package Search lifted

When Package Search is launched from Account or Contact users are now able to search for up to 20 rooms oppose to 4 rooms prior to this release.

Feature: Package Search

Package Search LWC needs to support custom lightning app/pages for Package Search

A new parameter has been added to the Package Search launcher control. This enables the control to redirect users to a custom Package Search page and supports the scenario when configuration is required on the Package Search Lwc.

Feature: Package Search

Header not showing when Package Search opens in the Availability Screen

We have made a change that when you access Package search, Availability screen, and a search has not been executed, the header (which shows Results/Availability buttons) will be visible in the Package Search results.

Feature: Package Search

Show 'No Packages Found' in Package search Availability Screen

We have added a 'No Packages Found' message that appears when a search on the Package Availability screen returns no results.

Feature: Package Search

Search Button in Package Search Panel should be visible without scrolling

We’ve updated the Package Search search button so it is always visible at the bottom of the search panel. This change eliminates the need to scroll, regardless of the browser window’s height.

Feature: Package Search

Availability Screen - Line to separate Package search result rows

A line has been added to separate the results on the Package Search Availability screen.

Feature: Package Search

Related Tags: Eiffel Releases