While this requirement is best addressed using configuration mapping or a callable flow, flow templates offer integration builders an additional method for mapping a flow’s field differently for each customer. However, before choosing to use a flow template instead of a configuration mapping, it is important to understand the limitations that this method presents.
When you add a flow template to an integration, a copy is automatically created in each new workspace to which the integration is deployed. This copy is different from a shared standard integration. If you make changes to the template copy within a specific workspace, those changes will only apply to that workspace. Similarly, if you edit the original flow template in the integration, it will not change any of the copies that were already created.
Comparatively, using a flow with either configuration mapping or a called flow allows integration builders to propagate updates across all workspaces where the flow is used.
When you create a flow template, App Xchange adds a Template tag and an icon to the template when it is displayed in a list.
Add a new feature or open the feature you want to add a flow template to.
In the Flow Templates section, select + Add Flow Template and choose the type you are creating.
Create: Create a template from a flow that already exists.
Use Existing: Adds a reference to an existing template in a different feature.
Note: You can add search criteria in the Search Flows or Workspace fields to filter the flows that display.
To use an existing flow, select the checkbox for the flow you want to use.
Select Save.
The flow template is added to the integration feature.
To edit an existing flow template globally, open the flow template in the integration builder. Changes made by the flow author will update the flow across all future workspaces that use it, but not any existing copies.
To edit an existing flow template for a specific customer user, navigate to Customers > Selected Workspace > Flows and select the flow. Open the flow template from within the workspace to make your changes. Saving these changes creates a copy with the Template Copy tag. It does not modify the original flow template.
Was this helpful? Give us feedback.