A background step launches an active autolaunched flow and has no user interaction. You
can control when a background step is ready to start. Use background steps to carry out actions
that are related to an approval submission but aren’t part of an approval work item. For
example, use a background step to update records or trigger additional notifications related to
the approval.
Each background step references an active autolaunched flow. When the orchestration run
associated with the parent approval submission is running, it automatically determines
whether the step’s flow is run synchronously or asynchronously. An orchestration run
associated with an approval submission processes a background step asynchronously when the
step’s underlying flow contains 1 or more Action, Subflow, or Wait elements.
When a background step’s flow runs synchronously, the orchestration run associated with the
parent approval submission immediately resumes when the flow is completed.
When a background step’s flow runs asynchronously, the step publishes a Flow Orchestration
Event platform event. That event causes the orchestration run associated with the parent
approval submission to evaluate the status of the current stage and each step with a status
of Not Started or In Progress contained within the stage.
When to Start the Step
To control when a background step starts, select a condition.
Step Condition
Requires
When the stage starts, the step starts
—
When another step is marked Completed, the step starts
The name of the step that must be completed before the step can start
When the specified requirements are met, the step starts
Up to 10 requirements that determine whether the step can start
When the specified evaluation flow returns True, the step
starts
The name of the active evaluation flow that determines whether the step can
start
Running Context of an Action Called by a Background Step
By default, an active autolaunched flow called by a background step runs in the context of
the automated process user. To run a background step in the context of a different user, use
the Select Who to Run the Action As section in the background step's Properties panel. To
control the system context’s record-level access, use the How to Run the Flow advanced
option of the autolaunched flow referenced by the step.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.