You are here:
Decision Flow Orchestration Resource
Evaluate a set of conditions, and then route users through the orchestration based on the outcomes of those conditions. This element performs the equivalent of an if-then statement.
Required Editions
| View supported editions for Flow Orchestration. |
| field | Description |
|---|---|
| Label | Identifies the name for this element on the canvas. |
| API Name | The requirement for uniqueness applies only to elements and resources within the current flow approval process. Two items can have the same API name, provided they're used in different flow approval processes.An API name can include underscores and alphanumeric characters without spaces. It must begin with a letter and can't end with an underscore. It also can't have two consecutive underscores. |
| Description | A description of what the element does within the orchestration. |
Select Decision Logic
Select the method that the Decision element uses to determine which outcome to run.
| Method | Description |
|---|---|
| Define Manually (Default) | Define logic to evaluate explicitly defined data from your orchestration and determine which outcome runs. Outcomes for a Decision element with manually defined conditions are evaluated in the order that they’re listed. Therefore, the order that you define your outcomes in can impact the outcome that the orchestration run takes. |
| Define with AI (Advanced) | Write instructions for AI to dynamically evaluate data from your orchestration and determine which outcome runs. Outcomes for a Decision element with AI conditions are evaluated simultaneously. Therefore, the order that you define your outcomes in has no impact on the outcome that the orchestration run takes. |
Describe the Decision
This section is shown when you select Define with AI (Advanced).
| Field | Description |
|---|---|
| Decision Instructions | A description of what decision the element is making. Include resources from the orchestration to improve AI accuracy. |
Outcomes for Define Manually (Default)
For each path that the orchestration can take, create an outcome. For each outcome, specify the conditions that must be met for the orchestration run to take that path. To relabel the path to take if no outcome’s conditions are met, click Default Outcome.
| Field | Description |
|---|---|
| Outcome Label | Identifies the connector for this outcome on the canvas. |
| Outcome API Name | The requirement for uniqueness applies only to elements and resources within the current orchestration. Two items can have the same API name, provided they're used in different orchestrations.An API name can include underscores and alphanumeric characters without spaces. It must begin with a letter and can’t end with an underscore. It also can’t have two consecutive underscores. |
| Condition Requirements to Execute Outcome | Determines whether the orchestration takes this outcome’s path. Sets logic and conditions for each outcome that determine if the orchestration follows its path. |
| When to Execute Outcome | Available on record-triggered orchestrations. Determines whether this outcome’s path is taken based on whether the triggering record is updated to meet the condition requirements. For example, the opportunity update that triggered the orchestration to run changed its stage to Closed Won from any value that isn’t Closed Won. |
Outcomes for Define with AI (Advanced)
For each path that the orchestration run can take, create an outcome. For each outcome, enter information that tells AI when to take the outcome. To relabel the path to take if AI determines that no conditions are met, click Default Outcome.
| Field | Description |
|---|---|
| Outcome Label | Identifies the connector for this outcome on the canvas. |
| Outcome API Name | The requirement for uniqueness applies only to elements and resources within the current orchestration. Two items can have the same API name, provided they're used in different orchestrations.An API name can include underscores and alphanumeric characters without spaces. It must begin with a letter and can’t end with an underscore. It also can’t have two consecutive underscores. |
| Outcome Instructions | An explanation that tells AI when to take the outcome. Include resources from the orchestration to improve AI accuracy. |
Usage for Manual Conditions
When a Decision element offers two possible outcomes, the default outcome is only followed if the conditions for the first outcome aren’t met.
If a Decision element has more than two possible outcomes, the system evaluates them in the order they’re listed. For each outcome:
- Its conditions are checked.
- If the conditions are true, the path associated with that outcome is run.
- If the conditions are false, the system moves on to evaluate the conditions of the next outcome in the list.
If none of the defined outcome conditions are met, then the default outcome path runs.
Usage for AI Conditions
AI Decision isn't supported for record-triggered orchestrations.
At run-time, the decision instructions are combined with all outcome instructions, and AI determines which outcome to take. Because AI evaluates all conditions simultaneously, the order that you define your outcomes in has no impact on the outcome that the orchestration run takes.
