You are here:
Variable Flow Approval Processes Resource
Store a value that can be changed throughout the flow approval process.
Required Editions
| View supported editions for Flow Approval Processes. |
| Field | Description |
|---|---|
| API Name | The requirement for uniqueness applies only to elements and resources within the current flow approval process. Two items can have the same API name, provided they're used in different flow approval processes.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. |
| Description | Helps you differentiate this variable from other resources. |
| Data Type | Determines the types of values that the variable can store. You can’t change the data type of a previously saved variable.
The Record data type can store multiple field values for one record. The Apex-defined data type can store multiple field values for one Apex class. |
| Allow multiple values (collection) | When selected, the resource is a collection variable. You can store a list of values in collection variables. Collection variables can store only values that are compatible with their data type. When the data type is Record, the collection variable can only store values for the associated object’s records. For example, store multiple email addresses in a collection variable, and reference the collection variable to send an email. |
| Object | The object whose field values you can store in the variable. You can’t change the object of a previously saved variable. Available only when the data type is Record. |
| Decimal Places | Controls the number of digits to the right of the decimal point up to 17 places. If you leave this field blank or set it to zero, only whole numbers appear when an approval submission based on your flow approval process is made. Available only when the data type is Number or Currency. |
| Availability Outside the Flow | When a variable is available for input, it can be set at the start of the orchestration run associated with a parent approval submission, such as when a person submits a record for approval from a Lightning page. Each autolaunched flow approval process contains a minimum of 3 variables:
Disabling input or output access for an existing variable can break the functionality of applications and pages that call the flow approval process and access the variable. For example, you can access variables from URL parameters, processes, and other flows. This field doesn’t affect how variables are used within the same flow approval process. |
| Default Value | Determines the variable value when the orchestration run based on the flow
approval process starts. If you leave this field blank, the value is
Not available for Picklist and Multi-Select Picklist variables. |
