Overview
A Rule node serves as a control and decision point in a workflow. This is the intermediate step that merges branches, listens for events, and branches on conditions. The node dictates how the execution proceeds based on defined logic.
To access the Node Editor navigate to Control Center -> Process Studio -> Workflows -> select the target Workflow Template and click the Rule node.
Prerequisites
- A Workflow template must be created.
- A Starting rule must be configured on the canvas.
Required Permissions
- Admin permissions with Workflow configuration access.
Key Components
The Rule node evaluates an execution in three stages:
- Merged Steps Validation: Validates whether All or Any of the previous steps are completed to activate the rule.
- Event Listening: Waits for a system event to continue with the subsequent actions.
- Conditionals Evaluation: Evaluates the path conditions to direct the execution into the correct path.
Convergence Logic
When multiple branches connect to a Rule, the convergence must be defined:
- ALL: Waits for every upstream branch to arrive before continuing.
-
ANY: Continues as soon as the first upstream branch arrives. The branches that did not win remain active. Tasks associated with those branches still exist and can be worked, but closing them does not advance the execution.
Note: Convergence can be switched even if only one inbound path exists, though it has no practical effect.
Rule Scope
If a workflow is triggered by a related object, the scope of the rule determines how events are monitored:
- Broad Listening: The rule listens for events on any record of the object.
- Trigger Record Only: The rule listens only for events on the record that triggered the execution. This setting forces the Event Triggered object to match the trigger object of the starting rule. Conditions on that object resolve against the field values of that specific record.
Conditions and Paths
- Outbound paths are evaluated in order, and the order is fixed by creation.
- The order cannot be changed.
- Only the first matching path is followed during the running workflow.
- Each rule can have one or more paths.
- When Conditions are disabled, the rule has a single default output.
Configuration Steps
- Open the Rule Editor.
- Enter or change the name in the Name field.
- Select All or Any from the dropdown menu to define whether all or any of the previous steps must be completed before the rule is activated.
- Select Broad Listening or Trigger Record Only under the Rule Scope section.
- Enable the Event Triggered toggle to configure an Object and an Event Type to be monitored.
- Enable the Conditions toggle to configure conditional paths.
- Configure a condition to evaluate a field value.
- Click + PATH to add a new condition path.
- Click Save to save the setup.
Validation
Executions can be monitored from the global list at Control Center -> Process Studio -> Workflows -> Running tab or from the contextual Workflows view of a specific Project or Lead record.
Troubleshooting
Stalled Execution at ALL Convergence
- Problem Description: An execution is stalled indefinitely at a Rule node.
- Possible Causes: Upstream exclusivity allowed only one branch to reach a rule configured with ALL convergence. The platform editor prevents direct connections of exclusive paths into an ALL rule, but indirect exclusivity is not caught automatically.
- Resolution Steps: Stop the execution manually to clear it. Update the workflow template to use ANY convergence for those exclusive branches.