Similar to the if statement in programming languages, it determines the subsequent flow direction based on the result of the configured condition.
The Condition node has two modes: "Continue if true" and "Branch on true/false". You must select one of these modes when creating the node, and it cannot be changed in the node's configuration afterward.

In the "Continue if true" mode, when the condition's result is "true", the workflow will continue to execute subsequent nodes. Otherwise, the workflow will terminate and exit prematurely with a failed status.

This mode is suitable for scenarios where the workflow should not proceed if the condition is not met. For example, a form submission button for submitting an order is bound to a "Before action event". If the stock for the product in the order is insufficient, the order creation process should not continue but should fail and exit.
In the "Branch on true/false" mode, the condition node will create two subsequent branches, corresponding to the "true" and "false" results of the condition. Each branch can be configured with its own subsequent nodes. After either branch completes its execution, it will automatically merge back into the parent branch of the condition node to continue executing the following nodes.

This mode is suitable for scenarios where different actions need to be performed depending on whether the condition is met or not. For example, checking if a piece of data exists: if it doesn't, create it; if it does, update it.
Currently, three engines are supported:
In all three calculation types, variables from the workflow context can be used as parameters.