--- schema_version: "1" id: 81a651715d3d0203983629fc9f35a84bcd34828c83390fc0a4cc3e2efb34e8f0 title: Step Flow Approval Processes Resource collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_automated_approvals_ref_resources_step.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_automated_approvals_ref_resources_step.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 0c79ff01c713f1991b31b98dd07ef363643a0f53b1a8dde655b5f8d8813612bf description: Organize the work done in a flow approval process stage. products: - Flow Builder - Salesforce Platform release: "264" --- # Step Flow Approval Processes Resource Organize the work done in a flow approval process stage. ### Required Editions

View supported editions for Flow Approval Processes.

Flow approval processes have approval steps and background steps. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png) Note The Step resource in Flow Approval Processes isn't related to the discontinued Step element in flows. ## Background Steps Background steps call autolaunched flows and run without user interaction. At run time, the orchestration run associated with a flow approval process automatically determines whether the autolaunched flow runs synchronously or asynchronously.

Field	Section	Description
Label		Helps you identify the element on the canvas.
API Name		Automatically populated if empty when you fill out the Label field and press TAB. 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		Helps you remember what this resource does. When editing an element, appears after you click .
Condition	Select When to Start the Step	Identifies the method used to determine whether a step is ready to start. When the stage starts, the step starts The step starts when its stage starts. When another step is marked Completed, the step starts The step starts after another step is completed. When the specified requirements are met, the step starts The step starts when the specified requirements are met. When the specified evaluation flow returns True, the step starts The orchestration run associated with a parent approval submission runs a specified evaluation flow to determine if the step can be started. The orchestration run doesn’t start the step until the specified evaluation flow’s `isOrchestrationConditionMet` output variable returns true.
Step Name	Select When to Start the Step	Specifies a step that must be marked completed before the current step can start. Available whenCondition is set to When another step is marked Completed, the step starts.
Requirements to Start Step	Select When to Start the Step	Determines the logic that evaluates whether the step can be started. All Requirements Are Met (AND) All specified requirements must be met for the stage to be started. Any Requirement Is Met (OR) Any of the specified requirements can be met for the stage to be started Custom Logic Is Met The specified requirement logic must be met for the stage to be started.
Requirement Logic	Select When to Start the Step	Determines the logic that evaluates whether the step can be started. Condition is set to When the specified requirements are met, the step starts. Requirements to Start Step is set to Custom Logic Is Met.
Resource	Select When to Start the Step	The resource evaluated by this requirement. Available when Condition is set to When the specified requirements are met, the step starts.
Operator	Select When to Start the Step	The operator to use to evaluate the resource. Available when Condition is set to When the specified requirements are met, the step starts.
Value	Select When to Start the Step	The value to compare the specified resource to, using the specified operator. Resource and Value must have compatible data types. Available when Condition is set to When the specified requirements are met, the step starts.
Evaluation Flow	Select When to Start the Step	Specifies the flow that determines if the step can start. Available when Condition is set to When the specified evaluation flow returns True, the step starts.
Action	Select an Action to Run	Specifies which autolaunched flow to run for a step.
User Type	Select Who to Run the Action As	Determines the context that the step is run in. Automated Process User A Selected User A User Specified by a Resources at Run Time
User	Select Who to Run the Action As	Specifies the user to run the step as. Available when User Type is set to A Selected User.
User Resource	Select Who to Run the Action As	Specifies a variable that at run time contains the user to run the step as. Available when User Type is set to A User Specified by a Resources at Run Time.

## Approval Steps Approval steps call screen flows and require user interaction.

Field	Section	Description
Label		Helps you identify the element on the canvas.
API Name		Automatically populated if empty when you fill out the Label field and press TAB. 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		Helps you remember what this resource does. When editing an element, appears after you click .
Condition	Select When to Start the Step	Identifies the method used to determine whether a step can be started. When the stage starts, the step starts The step starts when its stage starts. When another step is marked Completed, the step starts The step starts after another step is completed. When the specified requirements are met, the step starts The step starts when the specified requirements are met. When the specified evaluation flow returns True, the step starts The orchestration run associated with a parent approval submission runs a specified evaluation flow to determine if the step can be started. The orchestration run doesn’t start the step until the specified evaluation flow’s `isOrchestrationConditionMet` output variable returns true.
Step Name	Select When to Start the Step	Specifies a step that must be marked completed before the current step can start. Available whenCondition is set to When another step is marked Completed, the step starts.
Requirements to Start Step	Select When to Start the Step	Determines the logic that evaluates whether the step can be started. All Requirements Are Met (AND) All specified requirements must be met for the stage to be started. Any Requirement Is Met (OR) Any of the specified requirements can be met for the stage to be started Custom Logic Is Met The specified requirement logic must be met for the stage to be started.
Resource	Select When to Start the Step	The resource evaluated by this requirement. Available when Condition is set to When the specified requirements are met, the step starts.
Operator	Select When to Start the Step	The operator to use to evaluate the resource. Available when Condition is set to When the specified requirements are met, the step starts.
Value	Select When to Start the Step	The value to compare the specified resource to, using the specified operator. Resource and Value must have compatible data types. Available when Condition is set to When the specified requirements are met, the step starts.
Evaluation Flow	Select When to Start the Step	Specifies the flow that determines if the step can start. Available when Condition is set to When the specified evaluation flow returns True, the step starts.
Action	Select an Action to Run	Specifies which screen flow to run for a step.
Approver Type	Select the Approver	Identifies the type of approver to assign the step to. User Group Queue Resource
User	Select the Approver	The name of the user to assign the step to. Available when Approver Type is set to User.
Group	Select the Approver	The name of the group to assign the step to. Available when Approver Type is set to Group.
Queue	Select the Approver	The name of the queue to assign the step to. Available when Approver Type is set to Queue.
Resource	Select the Approver	The API name of the variable that contains the username of the user, the API name of the public group, or the API name of the queue to assign the step to. At run time, the orchestration run associated with a flow approval process determines the type of assignee in the specified resource and dynamically resolves it. Available when Approver Type is set to Resource.
Customize approver notification email	Select the Approver	Indicates whether to send the assigned approver a custom email notification when the approval work item associated with this step is created.
Subject	Select the Approver	The subject text of the custom email or the API name of a text template that contains the subject text at run time.
Body	Select the Approver	The body text of the custom email or the API name of a text template that contains the body text at run time.
Record ID	Select the Record to Approve	Specifies the ID of the record to be approved where the Work Guide displays the screen flow to the assigned approver.
Condition	Select When to Complete the Step	Identifies the method used to determine whether a step can be marked as completed. When the assigned user has completed the action, the step is marked Completed The step is marked Completed when someone has approved or rejected the approval work item associated with the step. When the specified requirements are met, the step is marked Completed The step is marked Completed when the specified requirements are met. When the specified evaluation flow returns True, the step is marked Completed The orchestration run associated with a parent approval submission runs a specified evaluation flow to determine if the step can be marked Completed. The orchestration run doesn’t mark the step Completed until the specified evaluation flow’s `isOrchestrationConditionMet` output variable returns true.
Requirements to Start Step	Select When to Complete the Step	Determines the logic that evaluates whether the step can be marked as Completed. All Requirements Are Met (AND) All specified requirements must be met for the stage to be completed. Any Requirement Is Met (OR) Any of the specified requirements can be met for the stage to be completed Custom Logic Is Met The specified requirement logic must be met for the stage to be completed.
Resource	Select When to Complete the Step	The resource evaluated by this requirement. Available when Condition is set to When the specified requirements are met, the step is marked Completed.
Operator	Select When to Complete the Step	The operator to use to evaluate the resource. Available when Condition is set to When the specified requirements are met, the step is marked Completed.
Value	Select When to Complete the Step	The value to compare the specified resource to, using the specified operator. Resource and Value must have compatible data types. Available when Condition is set to When the specified requirements are met, the step is marked Completed.
Evaluation Flow	Select When to Complete the Step	Specifies the flow that determines if the step can be marked as completed. Available when Condition is set to When the specified evaluation flow returns True, the step is marked Completed.

## Step Statuses

Step run Status	Description
Not Started	The step hasn't met its entry condition.
In Progress	The step was started.
Completed	The approval step met its exist condition The background step's flow was completed. The step was completed when its associated stage encountered an error.
Discontinued	The step was in progress when its associated stage completed. The step was in progress when the orchestration run associated with the approval submission encountered an error. The step was in progress when its associated stage encountered an error.
Error	The step encountered an error. The autolaunched flow associated with a background step encountered an error. The screen flow associated with an approval step encountered an error.