Duomo - Patch 1 (18.5)
Bug Fixes
When opening certain Packages in Package Search, an error is showing
We fixed an issue in Package Search where an error displayed if a Package (with Package day locations configured) was expanded to view the day by day summary.
Feature: Package Search
Related Support Ticket: KHELP-10276
Error when trying to manage Supplier Invoices using Bulk mode
We fixed an issue with the Bulk Invoice Allocation function that displayed an error on creation of a Supplier Invoice.
Feature: Supplier Invoices
Related Support Ticket: KHELP-10216
Rail Booking Failure when using Multi-Segment
A Rail booking issue was fixed where rail bookings were failing to confirm when attempting to book multiple segment rail journeys.
Feature: Rail Service Search
Related Support Ticket: KHELP-10212
Content Editor Issues
With the release of Duomo Major, Kaptio introduced updates to allow developers to get the Id of the document template used to generate the document in custom document components. This update resulted in a regression issue where saving a document or a document template threw an error if they contained a classic custom document components. This issue is now fixed but customers intending to use the template Id in their custom document component will need to
-
Check the “Is Advanced” checkbox on their component. This can be done at Kaptio Settings ⇒ Content Components ⇒ Edit next to your component.
-
Update the custom component to implement KaptioTravel.AbstractContentComponentHandler instead of KaptioTravel.IComponentHandler
-
Update the custom component’s to have the init() function receive a map containing multiple paramters and pass it onto their class variables.
public override void init(Map parameters) { Boolean isValid = parameters != null && String.isNotBlank( (String) parameters.get('templateId')) && String.isNotBlank((String) parameters.get('initId')); if (isValid) { itineraryId = Id.valueOf((String) parameters.get('initId')); templateId = Id.valueOf((String) parameters.get('templateId')); } }
See example of an Advanced Custom Component
Feature: Content
Related Support Ticket: KHELP-10285
Minor Fixes
Setting for timeouts
In this release we have added a timeout configuration for API calls. The default/minimum is 60 seconds (60000 milliseconds) but this can be increased if required to a maximum of 2 minutes (120000 milliseconds). This was included to ensure Packages with many API Components can be added to an Itinerary successfully before a timeout occurs.
Feature: Package Search