You are here:
Configure Conditional Branching in Agentforce Operations
Set up conditional branching so stages in a workflow start only when specific conditions are met in Agentforce Operations.
Required Editions
| License Required |
|---|
This feature is a workspace that’s external to your Salesforce org and requires an Agentforce Operations license. To purchase an Agentforce Operations license, contact your Salesforce account executive. |
| Role or Access Needed | |
|---|---|
| To edit a blueprint in Agentforce Operations: | Admin role, Creator role, or a user with Edit access for the blueprint |
- Create a blueprint or edit an existing blueprint.
- In the blueprint, click + Add stage.
- Enter a stage name.
- For Start, select Based on specific workflow conditions or Based on specific stage conditions. With these options, you can use values from earlier fields to control when the stage starts.
- If you selected Based on specific stage conditions, select a previous stage to tie the condition to.
-
Add your first condition.
- Select a field from a prior stage.
- Select an operator. For example, Is equal to.
- If applicable, enter or select the value needed for the condition to be met.
The operators available depend on the field type. For example, number and currency fields supportgreater than or equal to,less than or equal to, andequal to.
TipUse
is emptyto create a branch that runs only when a field has no value. For example, when an optional field wasn't filled out by the user. -
Select if the new condition must also be true or if the new condition can be true instead
of the previous condition.
- If the new condition must also be true, select and.
- If the new condition can be true instead of the previous condition, select or.
-
To add a nested layer of conditions, click + Add condition group and
add the nested conditions.
Condition groups make it possible to build more complex logic by grouping conditions together. You can't add a condition group inside another condition group.
When the workflow runs, Agentforce Operations uses the data from earlier inputs to determine what happens:
- Stages where conditions are met start automatically after the selected previous stage.
- Stages where conditions aren't met are skipped.
Løste denne artikel dit problem?
Giv os besked, så vi kan forbedre os!

