In a workflow, there are multiple possible ways it finishes, or better known as Finish Points. Each path can lead to a different ending depending on how tasks are completed and how the workflow was configured.
The Completion Rule Node defines the logic that tells the platform when a workflow is considered closed and what that final result means.
This is achieved by organizing Finish Points into Completion Groups and assigning an Outcome Code to each group.
There are two ways to configure the workflow groups:
- When a running workflow reaches any of the finish points within a group, the platform automatically recognizes the workflow as closed and assigns the corresponding Outcome Code.
- Similarly, when a workflow reaches all the finish points within a group, the platform marks the workflow as closed and assigns the corresponding Outcome Code.
This is especially important when some workflows are nested within others. In these cases, the Outcome Code acts as a signal that allows the parent workflow to recognize that the nested workflow has been completed and how the process ended, helping determine the appropriate next step.
Additionally, Outcome Codes provide valuable insight into how and when workflows are completed, enabling firms to better understand and analyze their processes.
Key Concepts
- Finish Points: Any path where the workflow ends. These finish points are automatically identified and listed when you are configuring the Completion Rule.
- Group: Within each group the user can configure the finish points that share the same Outcome Code. Each Group includes:
- One or more Finish Points.
- A condition: Any or All.
- One Outcome Code.
- Conditions: Define whether any or all of the Finish Points in a Group must be completed for the workflow to close.
- Any: The workflow is closed with the specified Outcome Code when any one of the finish points in the group is reached.
- All: The workflow is closed with the specified Outcome Code only when all finish points in the group are completed.
How it works
The Completion Rule Node provides the logic explaining how a workflow ends and what that ending means. It works as follows:
- Finish Points are Identified. Automatically the Finish Points in the workflow are identified.
For example: This diagram outlines an example of a workflow with 6 identified finish points.
Configure the Groups:
Allows to define how a workflow is closed. The user must configure these Groups. Each group allows to:
- Associate one or more Finish Points.
- Assign an Outcome Code.
- Define the completion condition: Any or All.
Once a workflow meets the condition defined in a group, the platform closes the workflow with the corresponding Outcome Code.
For example: For the displayed diagram, the groups were configured as follows:
Group 1:
- Outcome Code: “Outcome Code 1”.
- Condition: Any (Any of the elements should be completed).
- Finish Points:
- Finish Point 2.
OR
- Finish Point 4.
OR
- Finish Point 6.
Group 2:
- Outcome Code: “Outcome Code 2”.
- Condition: And (All of the elements should be completed).
- Finish Point 1.
AND
- Finish Point 3.
Group 3:
- “Outcome Code 3”.
- Condition: And (All of the elements should be completed).
- Finish Point 5.
- The Workflow is Closed:
Once a running workflow meets the condition defined in a group, the platform closes the workflow and assigns the corresponding Outcome Code.
For example, based on the diagram and the configured groups:
If the workflow reaches Task 2, Path 2 (Finish Point 4):
This finish point belongs to Group 1 and the workflow is closed with the “Outcome Code 1”.
In another scenario, if the workflow reaches the Task 1, Path 1 (Finish Point 1) AND the Task 2, Path 1 (Finish Point 3):
As all the finish points in the Group 2 were reached, the workflow is closed with the “Outcome Code 2”.