You are here:
Add an On-Demand Step Definition
Mark a step definition as eligible for on-demand execution so users can run the associated task outside the planned stage transition. Define the name, step type, and the criteria that determine when the step is available.
Required Editions
| Available in: Lightning Experience |
| Available in: Financial Services Cloud. View edition availability. |
| User Permissions Needed | |
|---|---|
| To mark a step definition as eligible for on-demand execution and manage on-demand reasons: | Stage Management Design User |
In Object Manager, add picklist values to the Adhoc Entry Reason field on the Stage Transition Entry object so users can select a reason in the Record Stage Overview component. Create a stage definition and add stage transitions before you add an on-demand step. See Create a Stage Definition and Set Up Stage Transitions.
Most business processes are planned in advance. Some scenarios, such as a regulatory deadline, a customer request, or an error correction, fall outside that planned flow. An on-demand step definition is a step that you mark as eligible so users can run its task immediately for the record’s current stage. After you add the step, users with the Stage Management On-demand User permission can run the eligible tasks.
- From Setup, find and then select Stage Definitions.
- Open the stage definition that you want to update, and then click Set Up Stage.
- Click Add On-Demand Step.
-
Enter a name and an API name, and then select a step type.
Step types match the types that you use for planned step definitions, such as Autolaunched Flow, Integration Definition - Auto, Manual Task, Screen Flow, Integration Definition - Manual, Milestone, and Omniscript. See Add Step Definitions.
-
In Add Criteria and Conditions, specify when the step is eligible
for on-demand execution.
- Use Expression Set: Select an expression set that determines whether the step is available. Create the expression set with the Fulfillment Condition usage type, and include the isExecuteStep Boolean variable as a local variable. See Use Expression Sets to Control Step Execution.
- Use Inline Condition: Define conditions in the builder that must be met before users can run the step on demand.
- Save your changes.
A lending admin adds an on-demand step that runs a document verification integration. The admin names the step Verify Identity Documents, selects Integration Definition - Auto as the step type, and uses an inline condition so the step is available only when the application form is in the Risk Screening stage. A user can then run the verification immediately when a regulator requests updated identity checks.
Define the reasons that users select when they run an on-demand task, such as Regulatory Requirement, Customer Request, or Error Correction. Then assign the Stage Management On-demand User permission to users who run those tasks. See Run Tasks On Demand.
