You are here:
Flow Version Properties
A flow version’s properties consist of its label, description, interview label, and type. These properties drive the field values that appear on the flow’s detail page.
Required Editions
| View supported editions. |
To change the properties of a flow version, open it in Flow Builder. Then click 
.
| Property | Description |
|---|---|
| Flow Label | The label for the flow version. The label appears in the flow detail page and list views. When a user runs this flow, the header displays the flow label. You can edit the label for inactive flows and flow versions. |
| Flow API Name | The API name for the flow. The API name is used to refer to this flow from other parts of Salesforce, such as in a URL or Lightning web component. An API name can include underscores and alphanumeric characters without spaces. It must begin with a letter and can’t end with an underscore. It also can’t have two consecutive underscores. The API name appears on the flow detail page. You can’t edit the API name after saving the flow. |
| Description | Differentiates the flow version from other versions. The description appears in the flow detail page and list views. You can edit the description for inactive flows and flow versions. |
| How to Run the Flow | Determines the context that the flow runs in. You can choose to always run flow in system context with sharing or system context without sharing. By default, the context that the flow runs in depends on how the flow is launched. |
| Type | Determines which elements and resources are supported in the flow and the ways that the flow can be implemented. The type appears in the flow detail page and list views. In flow version properties, the type appears in the Advanced section. For details, see Flow Types. Flow Builder doesn’t support saving a new version as a different flow type. To change a flow’s type, save it as a new flow. Before you change the flow type, make sure that the flow contains only the elements, resources, and functionality that the new flow type supports. You can fix some, but not all, compatibility issues in the new flow. |
| Source Template | Enter the label of the template this flow is based on. |
| Show a progress indicator on screen elements | Select to add a progress indicator that shows a user what stage they're inwhile running the flow. Available only for screen flows. |
| Template | Specifies whether the flow is a template. When a template is installed from a managed package, the subscriber can view the flow and save it as a new, editable flow. Non-template flows that are installed from managed packages can only be activated and deactivated. Suppose that your company needs a flow that differs slightly for each country where you do business. You can create or install a template for the base flow and then clone it to create each country-specific flow. Even if you don’t use managed packages, you can use this field to clearly identify the base flow. |
| Original Flow | Label of the original packaged flow that this flow overrides. When active, this flow runs instead of the packaged flow. |
| Overridable | When selected, users can create a linked, customizable version of this flow. The customized version inherits changes from the original flow while maintaining customizations. Only one active customized version can exist per original flow. |
| API Version for Running the Flow | Determines which versioned run-time behavior improvements the flow adopts. Changing this field requires the Manage Flow permission. Before you select a new API version, review all run-time improvements that were delivered between the currently selected API version and the new API version. You can find all flow and process run-time improvements for an API version in the Salesforce Release Notes. By default, when you create a flow, it runs in the latest API version. If an existing flow is saved as a new flow or flow version, the existing flow’s run-time API version is used in the new flow or flow version. The run-time API version doesn’t change as future Salesforce releases roll out. You decide when, if ever, to change the API version for running each flow version. This field lets you test and upgrade your flows one by one, and at your own pace. You can even opt to never adopt versioned updates for one or all your flows. |
| Interview Label | The label for the flow’s interviews. An interview is a running instance of a flow. This label appears in the following areas.
You can edit the interview label for inactive flows and flow versions. By default,
the interview label contains the flow name and the Use a text template to reference
multiple resources in the label. For example, |
