Decision Nodes

About Decision Nodes

Decision nodes (also called terminal outcome nodes) mark the final outcome of a workflow and set the dossier's completion status.

When a workflow reaches a decision node, it records the final outcome and marks the workflow as completed. The dossier's status field is set based on which decision node is reached.

The available decision nodes are:

APPROVE – Sets dossier status to approved
REJECT – Sets dossier status to rejected
NEEDS ATTENTION – Sets dossier status to needs attention

Important: Decision nodes don't stop other workflow nodes from executing. If service nodes (email, SMS, etc.) are connected to run in parallel with or before a decision node, they complete their execution. The decision node only sets the final outcome after all other processing is done.

APPROVE

The APPROVE node approves the submission and ends the workflow.

This node is commonly used when the workflow has reached a successful final outcome.

REJECT

The REJECT node rejects the submission and ends the workflow.

This node is commonly used when the workflow has reached a final outcome where the submission should not be accepted.

NEEDS ATTENTION

The NEEDS ATTENTION node marks the dossier as needing attention and ends the workflow.

This node can be used when the workflow should finish, but the result still requires manual attention or follow-up.

Settings

Decision nodes currently include the following settings:

Node Name
Description

These settings control how the node is named and described in the workflow builder.

Workflow Requirements

A workflow should typically end with at least one decision node (approve, reject, or needs attention) to set a clear final outcome. However, workflows can also end with other terminal-style nodes such as Redirect or Display Screen without a decision node.

When multiple branches exist in a workflow, different branches can route to different decision nodes. For example:

A successful path → Approve node
A rejection path → Reject node
An ambiguous path → Needs Attention node

Terminal Behavior

Decision nodes are terminal in scope (they end the workflow execution and mark completion), but they do NOT prevent other nodes from running. Any service nodes (email, SMS, etc.) that are scheduled to run concurrently or before the decision node will complete their execution. The decision node simply sets the final status after all other processing has finished.

If the end user should see a final message before the workflow completes, use a Display Screen node before the decision node.