2021 14.1 Release
New Metadata
Below you will find a list of metadata introduced in this release. Please ask your Salesforce Administrators to review this section as part of the release readiness process for your org.
| Type(field/object) | Name | Label | Description | Permissions |
|---|---|---|---|---|
Object |
|
Business Unit Connect Authentication |
Defines credentials to be used for search and book of land services of a land supplier in a specific business unit. |
CRUD - Admin |
New Metadata Reserved for Future Use
Below you will find a list of new metadata that is being introduced in this release that will be reserved for future use. No action is required on your Salesforce administrator for this metadata.
| Type | Name | Description |
|---|---|---|
Field |
|
The time of the most recent booking or cancellation request sent to the API supplier |
Deprecated Metadata
Below you will find a list of metadata that was deprecated as part of this release. Kaptio regularly deprecates and removes metadata from our Managed Package as part of overall maintenance of our solution.
Please note that data and metadata is never deleted in a client”s org without specific action by the customer. When a client upgrades to the new release, any deleted components are still available in the client”s org. The components are displayed in the Unused Components section of the Package Details page. This section ensures that subscribers have the opportunity to export data and modify custom integrations involving those components before explicitly deleting them. For example, before deleting custom objects or fields, customers can preserve a record of their data from Setup by entering Data Export in the Quick Find box and then selecting Data Export.
Please review and adjust any customisations (apex code, workflows, process builder etc.) related to this metadata.
As part of the release readiness process where we are deprecating fields or functionality, we have to ensure we provide relevant information in the release notes and have a dedicated knowledge base article that explains:
-
Why we are deprecating the feature
-
How it potentially affects the customer
-
What alternatives there are (if any)
It is the duty of the entire release readiness team to ensure that this practice is in place for all future releases.
| Type | Name | Comment |
|---|---|---|
Field |
|
The IsChild field of the Passenger object is only used in the Flight Placeholder screen in the Builder, but there is no need for it there. That field shall be deprecated, and the Flight Placeholder screen shall show the occupant type of the passenger channel role instead. |
Field |
|
See above |