--- schema_version: "1" id: c349d96638c3483ad5f37c2bde77cdde0cd722f2a3d3783f204eb079f54e168e title: Make Decisions in a Flow Approval Process collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_automated_approvals_build_logic_conditions.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_automated_approvals_build_logic_conditions.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: f6faec73966dcf7aae85896213347ad575d638719b6a8d8abc2fe2baa5dbbfb6 description: Use Decision elements to create conditions that control what stages are executed in a flow approval process. products: - Flow Builder - Salesforce Platform release: "264" --- # Make Decisions in a Flow Approval Process Use Decision elements to create conditions that control what stages are executed in a flow approval process. ### Required Editions

View supported editions for Flow Approval Processes.

User Permissions Needed
To open, edit, or create a flow approval process in Flow Builder:	Manage Flow
To see the Manage All Flow Approval Processes tile:	Approval Designer

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. At run time, the conditions are evaluated in the order you specify.. 1. In the flow approval process, click ![Add element](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/orchestration/orchestrator_fbuilder_circleplus.png)where you want to insert the element, and then select **Decision**. 2. Enter a label, API name, and description. 3. Select the type of decision logic to use for the Decision element. - To determine which outcome runs based on traditional logic expressions and explicitly defined data from your flow approval process, select **Define Manually (Default)** - To dynamically determine which outcome runs based on AI evaluating data from your flow approval process, select **Define with AI (Advanced)**. 4. If you selectedDefine Manually (Default), define the conditions and outcomes for the element. Outcomes for a Decision element with manual 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 associated with a parent approval submission takes. 1. Enter a label and an outcome API name. The outcome API name must be unique within the flow approval process. 2. Define the condition requirements to use for the first outcome.

Option Behavior for Decision Outcomes

All Conditions Are Met If one of the conditions is false, the flow approval process evaluates the next outcome’s conditions.

Any Condition Is Met If one of the conditions is true, the flow approval process immediately takes this outcome’s path.

Option	Behavior for Decision Outcomes
`All Conditions Are Met`	If one of the conditions is false, the flow approval process evaluates the next outcome’s conditions.
`Any Condition Is Met`	If one of the conditions is true, the flow approval process immediately takes this outcome’s path.
`Custom Condition Logic Is Met`	If you select this option, provide the condition logic by entering up to 1,000 characters. Use: Numbers to refer to each condition `AND`, `OR`, or `NOT` to identify which combination of conditions must be true Parentheses to group parts of the string together If you enter `AND`, it’s the same as if you selected All Conditions Are Met. If you enter `OR`, it’s the same as if you selected Any Condition Is Met. If you enter any other logic, make sure that you include a number for each condition. For example, for `1 AND NOT(2 OR 3)`, the flow evaluates whether the first condition is `true` and neither the second nor third condition is `true`.

Custom Condition Logic Is Met

If you select this option, provide the condition logic by entering up to 1,000 characters. Use:

Numbers to refer to each condition
AND, OR, or NOT to identify which combination of conditions must be true
Parentheses to group parts of the string together

If you enter AND, it’s the same as if you selected All Conditions Are Met. If you enter OR, it’s the same as if you selected Any Condition Is Met. If you enter any other logic, make sure that you include a number for each condition.

For example, for 1 AND NOT(2 OR 3), the flow evaluates whether the first condition is true and neither the second nor third condition is true.

3. Define the logic conditions for the first outcome.

Column Header	Description
Resource	Options: Select an input variable or automatic output from a stage or step. Select a Decision element. Select a global variable.
Operator	The available operators depend on the data type selected for `Resource`. See Flow Approval Processes Operators in Decision Elements.
`Value`	Resource and Value in the same row must have compatible data types. Options: Select a flow approval process resource, such as an input variable or automatic output from a stage or step. Select a global variable. Enter a literal value. When you add or subtract a number from a date value, the date adjusts in days, not hours.

Column Header

Description

Resource

Options:

Select an input variable or automatic output from a stage or step.
Select a Decision element.
Select a global variable.

Operator

The available operators depend on the data type selected for Resource. See Flow Approval Processes Operators in Decision Elements.

Value

Resource and Value in the same row must have compatible data types.

Options:

Select a flow approval process resource, such as an input variable or automatic output from a stage or step.
Select a global variable.
Enter a literal value.

When you add or subtract a number from a date value, the date adjusts in days, not hours.

5. If you selected Define with AI (Advanced), define the instructions and outcomes for the element. 1. For Decision Instructions, enter text that describes what decision the element makes. Include resources from the flow approval process to improve AI accuracy. 2. Enter a label and an outcome API name. The outcome API name must be unique within the flow approval process. 3. For Outcome Instructions, enter text that tells AI when to take the outcome. Include resources from the flow approval process to improve AI accuracy. 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 associated with a parent approval submission takes. 6. (Optional) To add a decision outcome to a Decision element, click ![The new outcome button](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/decision_element_add_outcome_button.png). Repeat the steps appropriate for the Decision element type to configure the outcome. For manual conditions, see Step 3b. For AI conditions, see Step 4b. 7. (Optional) To reorder a decision outcome in a Decision element, click ![The reorder icon for a decision outcome](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/decision_outcome_reorder_icon.png) and drag the item to its new location. You can’t move a decision outcome with conditions to the last position on the list because the default outcome is always last. 8. (Optional) To improve the readability of the Decision element, rename the default outcome. 1. Under Outcome Order, select **Default Outcome**. 2. Enter a label.