Variables
Overview
During the process execution, form data will be stored in process variables. The form identifiers filled in the Task Settings of user tasks and the Global Settings of processes will be used as variable names.
INFO
If variables are set repeatedly, the previously set values will be overwritten.
Default Variables
| Variable Name | Description |
|---|---|
| initiator | User ID of the process initiator |
| instanceId | Process instance ID |
| ${form}_recordId | Record ID of form data, where ${form} is the form identifier. For example, if the form identifier is set to test, the variable name is test_recordId |
Task Variables
Turning on the Store form data as task variables switch in task settings will generate a task variable based on the current form data. This task variable is only visible under the current task node.
The variable name is ${form}_task, where ${form} is the form identifier.
Usage scenario: When a task is rejected back to the current node in subsequent nodes, the task variable will be read as form data.
Process Variables
The scope of process variables is an entire process instance, and their lifecycle is consistent with the process instance.
Process variables are set using script functions and automation steps in Script Tasks and Service Tasks.
Process variables can be used in places that require filling in expressions, such as Multi-Instance Loop, user task Assignment, and Due Date. They can also be referenced in the flow expression of Conditional Sequence Flows.
For detailed operations, please refer to Set Workflow Variables

