Skip to main content

Node Validation vs. Flow Conditions

Overview

Users often confuse Flow Conditions with Node Validation. This article uses examples to explain how each feature works and how they differ.

  1. Node Validation determines whether data can be submitted from the current node to the next step.

  2. Flow Conditions determine which downstream node(s) the submitted data is routed to.


Application Scenarios

1. Flow Conditions are mainly used when a workflow has multiple paths. They determine which path the workflow follows based on the submitted data.

2. Node Validation checks whether the data meets the requirements to proceed to the next node.


Node Validation

The key purpose of Node Validation is to determine whether data can be submitted to the next node. Data that meets the specified conditions can proceed, while data that does not meet them cannot be submitted and remains at the current node.

Use Node Validation when only data that meets certain conditions should be allowed to proceed.

For example, when submitting a vehicle use request, the end date must be later than the start date (the time range must be greater than 0). Otherwise, the form cannot be submitted.


Flow Conditions

The key purpose of Flow Conditions is to determine which node(s) the data should flow to. When data is submitted from the previous node, it is routed to all nodes whose Flow Conditions are met.

Use Flow Conditions when data needs to be routed to different nodes based on specific conditions. For example, if Condition A is met, the data flows to Node 1; if Condition B is met, it flows to Node 2.


I have finished reading. 🏆

👉I can't wait to APPLY CHECKBOX FIELDS.

👉I need more HELP in Discord Forum.

Did this answer your question?