End Node
Overview
The End node defines a termination point in the workflow process. When workflow execution reaches an End node, the process instance terminates immediately. Unlike the Start node, which must be unique, a workflow process can have multiple End nodes to represent different completion paths or outcomes.
Node Properties
The End node configuration includes properties for identification and visual layout:
| Property | Type | Description |
|---|---|---|
| Name | Text |
The name that identifies this End node. This field is particularly important when a workflow contains multiple End nodes, as each node must have a unique name. |
|
Target position
|
Dropdown |
Defines the position where transition arrows enter the node. Available options are:
This is a visual property that helps organize the workflow diagram layout. |
| Id | Number |
Unique identifier assigned to the node. This value is automatically generated by the system and uniquely identifies the node within the process definition. |
Important: When a workflow contains multiple End nodes, each node must have a distinct name. Two End nodes cannot share the same name within the same process definition.
Multiple End Nodes
Workflows can contain multiple End nodes to represent different completion scenarios or outcomes. For example, a document approval workflow might have separate End nodes for "Approved", "Rejected", and "Cancelled" outcomes. When the workflow execution reaches any of these End nodes, the process instance terminates.
The End node only accepts incoming transitions (target). It cannot have any outgoing transitions (source), as it represents the termination of the workflow execution.
Behavior
When an End node is executed:
- The workflow process instance terminates immediately
- No additional nodes are executed after reaching an End node
- The End node does not initialize or modify any context variables
- The workflow status is updated to reflect completion
End nodes provide a clean way to terminate workflows and can be named descriptively to indicate the outcome or reason for completion, making workflow analysis and reporting more meaningful.
