Flow Templates
You can create a flow template when an integration flow has common steps but requires workspace-specific customization.
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 other integration flows, which will display as Managed. 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 and instead only apply to new integration deployments.
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.
Add Flow Templates to a Feature
When flows share common steps across different deployments, create a template for per-workspace customization.
Use
the Call a Flow flow step to add the template to your
flow. Changes to the template will affect only new users of the flow
template.
Create a Flow Template
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.
Integration builders can edit flow templates globally within the integration or locally within a customer workspace.
Was this helpful? Give us feedback.