--- schema_version: "1" id: 9b950bec4acbe020e2f15707db239cca336bf9907bf716e94131aac45de78995 title: Define Requirements for Stages and Steps 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_requirements.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_automated_approvals_build_requirements.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: e765ea6099354b6969a7c70c4f8326df4c9ce8974737126dfb2ea9fb98ba18cb description: Use requirements to resume an orchestration run when a record changes. Define up to 10 requirements to determine when a step is ready to start or when to mark a stage or an approval step as completed. products: - Flow Builder - Salesforce Platform release: "264" --- # Define Requirements for Stages and Steps in a Flow Approval Process Use requirements to resume an orchestration run when a record changes. Define up to 10 requirements to determine when a step is ready to start or when to mark a stage or an approval step as completed. ### 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 AND Approval Designer

User Permissions Needed

To open, edit, or create a flow approval process in Flow Builder:

Manage Flow

AND

Approval Designer

Before you begin, add a Stage element to your flow approval process or a Step resource to a stage. 1. In the Properties panel, select the condition that you can use to create up to 10 requirements to start a step or complete a stage or approval step. | To Use Requirements to | Select | | --- | --- | | Start a step | **When the specified requirements are met, the step starts** | | Complete a step | **When the specified requirements are met, the step is marked Completed** | | Complete a stage | **When the specified requirements are met, the stage is marked Completed** | 2. Set up the logic for the requirements.

Option Behavior for Requirements

All Requirements Are Met If one of the requirements is false, then the requirements aren’t met.

Any Requirement Is Met If one of the requirements is true, then the requirements are met.

Option	Behavior for Requirements
`All Requirements Are Met`	If one of the requirements is false, then the requirements aren’t met.
`Any Requirement Is Met`	If one of the requirements is true, then the requirements are met.
`Custom Requirement Logic Is Met`	When you select this option, provide the requirement logic by entering up to 1000 characters. Use: Numbers to refer to each requirement `AND`, `OR`, or `NOT` to identify which combination of requirements must be true Parentheses to group parts of the string together If you enter `AND`, it’s the same as if you selected All Requirements Are Met. If you enter `OR`, it’s the same as if you selected Any Requirement Is Met. If you enter any other logic, make sure that you include a number for each requirement. For example, for `1 AND NOT(2 OR 3)`, the flow evaluates whether the first requirement is `true` and neither the second nor third condition is `true`.

Custom Requirement Logic Is Met

When you select this option, provide the requirement logic by entering up to 1000 characters. Use:

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

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

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

3. Define up to 10 requirements. A change to a record referenced in a requirement can trigger the orchestration run to evaluate the status of the current stage and the outstanding steps within it. Some requirement resources don't trigger condition evaluations. For information on requirement resources that don’t trigger condition evaluations, see Events for Record-Change-Triggered Flow Approval Processes in [Considerations for Flow Approval Processes](https://help.salesforce.com/s/articleView?id=platform.automate_automated_approvals_considerations_orchestrations.htm&release=264.0.0&type=5 "Consider entry and exit condition requirements, events triggered by record changes, input values, and email notifications when you design and use flow approval processes.").

Column Header	Description
Resource	Options: Select a flow approval process resource. Select a variable. Select a record variable field. Select automatic output from a step. Select a Stage element's status. Select a Step resource's status. For record-triggered flow approval processes, select the $Record global variable. Select a global variable.
Operator	The available operators depend on the data type selected for Resource and work the same as operators used for Decision elements. 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 a variable or automatic output from a step. Select a global constant 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 a flow approval process resource.
- Select a variable.
- Select a record variable field.
- Select automatic output from a step.
Select a Stage element's status.
Select a Step resource's status.
For record-triggered flow approval processes, select the $Record global variable.
Select a global variable.

Operator

The available operators depend on the data type selected for Resource and work the same as operators used for Decision elements. 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 a variable or automatic output from a step.
Select a global constant
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.