<aside> 💡 This document provides an Administrator with the information required to either install the package into a new org or upgrade an existing version of the package.

</aside>

If you are on an older version than 16.0, you can jump over 16.x and go straight to 18.x but you still need to follow all the steps outlined in the Deployment Guide for Borobudur

If you are using “Classic custom document components” see the optional upgrade steps below. Otherwise, no additional steps are needed for the install of Duomo Major 18.3 and you can follow the Kaptio Salesforce Package Installation Guide

<aside> ⚠️ Kaptio has identified a scenario when performing the Duomo upgrade where the first installation attempt will fail for some orgs. The failure message will contain a reference to a background job that needs to be run before the upgrade can be re-attempted in 3-4 hours. The background job involves a required schema update in the form of a new field for PassengerItineraryUnitAssignment records.

This is a feature of the Salesforce platform when performing upgrades to managed packages and our recommendation is to allow for extra time for Salesforce to complete the background job prior to reattempting the upgrade. Based on indications from completed upgrades, this process may complete within 1-2 hours of the initial upgrade attempt (for ~450,000 records).

Please ensure to factor in this time when scheduling your upgrades as part of your deployment schedule. Should the upgrade continue to fail when reattempting the upgrade 4 hours after the initial attempt, please reach out to Kaptio Support for assistance

</aside>

<aside> 📄 Optional steps for Classic custom document components

With the release of Duomo Major 18.3, 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 in version 18.6

These steps are optional and only required for customers intending to use the template Id in their custom document component

1. Check the “Is Advanced” checkbox on their component. This can be done at Kaptio Settings => Content Components => Edit next to your component.
2. Update the custom component to implement KaptioTravel.AbstractContentComponentHandler instead of KaptioTravel.IComponentHandler
3. 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<String, Object> 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

</aside>

Release notes

Release notes for Duomo can be found https://release-notes.kaptioapis.com/latest-releases/-/6bhNFuuWS9cUFBiC26s7xn