Overview
A Rule Node serves as a control and decision point in a Workflow.
How It Works
The Rule Node works as follows:
|
Merged Steps Validation:
|
|
|
System Event Trigger:
|
|
|
Output Path Validation:
|
Previous Steps Completion
Users can configure a Rule to control when it can be activated, based on the status of earlier steps.
Users can choose between two setups:
| Type | Description |
| All | All previous connected steps must be completed before this rule can activate. |
| Any | Any of the previous connected steps must be completed before this rule can activate. |
Path
Additionally, users can configure the possible Paths the Rule can have. Each Path represents a possible outcome or branch based on WHEN Conditions.
A Condition is composed of WHEN conditional blocks.
- WHEN the condition is TRUE → the workflow continues through the corresponding path.
- WHEN the condition is FALSE → the following path condition is evaluated.
For more information on WHEN Conditionals please read: How it works the WHEN Conditional.
For more information on configuring Rule Nodes please read: How to Configure a Rule Node.
How to Configure a Rule Node
To configure a Rule node follow these steps:
Here's an interactive tutorial
- In the Workflows Editor, locate the Rule node and click on its card. The Rule Editor panel is displayed.
- Enter or change the rule Name.
Previous Steps
- In the displayed dropdown, select if All or Any of the previous steps MUST be completed before the rule is activated.
- If only one inbound connection is required, this setup is not required.
- If no inbound connections exist the No Previous Steps Connected. Connect at least one step to this rule in the workflow canvas message is displayed.
- The list of Nodes connected to the rule input, is displayed along with the type of node.
Trigger Event
- Enable the Event Triggered toggle to configure an Object and the event that will be monitored. (Optional).
Configuring a trigger event is optional. The rule can evaluate conditions immediately after the previous steps are completed.
Conditions
- Enable the Conditions toggle switch to configure WHEN Condition(s) that will define the node output(s).
- Each starting rule can have one or more Paths.
- The Paths are evaluated simultaneously, and only the first matching Path will be followed during the running workflow.
- Click the ellipsis icon next to the WHEN Conditional to copy the setup from a configured Template
Listed templates are saved WHEN Conditions, as outlined in step 10.
OR
- Configure a WHEN Condition to evaluate a field value against the condition.
- Click the
next to the WHEN condition
- Select an Object.
- Click the
next to the Object’s name.
- Select a Field or a Relationship and then a Field.
- Click the
next to the Field’s name.
- Select an Operator.
- Click the
next to the Operator’s name.
- Enter the Value.
Optional: Build Multiple Conditions (AND / OR)
- Click the
next to the entered value.
- Select the AND or OR operator to build another Conditional, and configure it as outlined in step 7.
Delete elements within a WHEN Conditional by clicking the icon on the displayed label.
- (Optional) Click +PATH to add a new WHEN Conditional and configure it as outlined in step 7.
- (Optional) Click the ellipsis icon
next to the built WHEN Conditional to save the WHEN Conditional as a template. Once saved, it can be reused as outlined in step 7.
Save
- Click SAVE to save the setup. The rule was edited successfully message appears.
- The SAVE button is enabled when all the mandatory fields have been completed in the Rule Editor view.
- The rule card is updated displaying the output points according to the configured paths, and the Draft status is removed after the setup is valid.