Jump Task to Target Node
Parameter Configuration
| Parameter | Description |
|---|---|
| Process Instance ID | Workflow instance ID. Dynamic content can be specified using expressions to get context variables |
| Task ID | Task ID. Dynamic content can be specified using expressions to get context variables |
| Jump Node | ID of the node to jump to. Dynamic content can be specified using expressions to get context variables |
| Remarks | Remarks or approval comments filled in when completing the task, displayed in the process information |
Usage Instructions
- Jump Node
Node ID can be obtained by clicking on the node in the Workflow process designer in the Application Designer
After jumping from the current node to the target node, all tasks belonging to the current node will be automatically marked as
Completed
Usage Scenarios
Workflow tasks jump to specified nodes, which can reduce the design of decision gateways or end nodes
- In cross-application scenarios, after other applications publish app events and this application listens to the published events, workflow tasks jump to specified nodes
- After triggers such as scheduled tasks, form listeners, and button controls, workflow tasks jump to specified nodes
- For application API interfaces, after third-party calls, workflow tasks jump to specified nodes