Loading
Stage Management
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Add Step Definitions

            You are here:

            1. Salesforce Help
            2. Docs
            3. Stage Management

            Add Step Definitions

            Use stage transition rules to add user access control and to define a transition plan for each stage and stage transition. Select the type of permissions to specify the users who can perform the stage transition. Add the criteria and conditions to run the step definitions.

            Required Editions

            Available in: Lightning Experience
            Available in: Automotive Cloud, Education Cloud, Financial Services Cloud, Health Cloud, Insurance Cloud, Life Sciences Cloud, and Manufacturing Cloud. View edition availability.
            User Permissions Needed
            To configure stage management: Stage Management Design User
            1. To add a stage transition for the source stage, in the Stage Management console, click + Add Stage Transition.
            2. In Transition To, select the target stage.
            3. Click Add Stage Transition Rules.
            4. To add user restrictions, select Validate Permissions.
              Note
              Note You can restrict stage transitions to users or queues by using User or Custom Permission. The User Permissions option shows only the restricted user permissions.

              Assign a queue to both the Task and Fulfillment steps. If a queue is assigned to only the Task or Fulfillment step, the tasks won't be executed.

            5. To specify the stage transition rules, select Add Criteria and Conditions.
            6. Define the rules for transition by using these criteria: All Conditions Are Met (AND), Any Condition Is Met (OR), or Logical Expression Is Met.
              Note
              Note For each stage transition, you can define up to 5 rules. Each rule can have up to 5 conditions by default. To increase the number of conditions per rule up to a maximum of 20, contact Salesforce Customer Support or your Account Executive.
            7. To notify users when criteria aren't met, add an error message.

              You can provide a unique error message for each criterion.

              For example, add messages such as “Parent account isn't approved” or “Applicant associated with this application form isn’t processed.”
            8. Add a step definition.
            9. Enter a name and developer name.
            10. Select one of these step types.
              • Autolaunched Flow: Specify the API name of the flow. For example, set up an autolaunched flow to trigger an approval process with tasks assigned to approvers. See Set Up Autolaunched Flow.
              • Integration Definition - Auto: Select an integration definition to be run automatically. For example, automatically start an integration callout for Anti-Money Laundering (AML) screening based on the information provided in the application form. See Create an Integration Definition.
              • Manual Task: Assign a manual task that the users or queues can perform. For example, assign the document verification tasks to your mid-office agents to manually verify the uploaded documents. Assign tasks to users or queues associated with the reference object, such as Last Modified by ID or Created by ID, by selecting the Associated Users or Queues dropdown.
              • Screen Flow: Enter the developer name of the screen flow, and then select the user or group to perform this task. For example, add a screen flow to validate if the risk assessment is complete. See Flow Element: Screen.
              • Integration Definition - Manual: Assign a user or a queue to perform manual integration callouts. See Create an Integration Definition.
              • Milestone: Add a milestone to track the progress towards a specific stage in a business process. For example, track the completion of documentation validation for a party profile record by using milestone. Your users can track the progress in the Record Stage Overview Lightning web component.
              • Omniscript: Specify the developer name to launch an Omniscript. For example, launch an Omniscript to verify the name in the address proof and match with Party Profile name. See Create an Omniscript.
              Note
              Note You can add up to 20 step definitions.
            11. Add an expression set to determine whether to run or skip the step definition execution.
            12. Add step dependencies.
            13. Save your changes.
            Example
            Example

            To set up a step definition for a customer onboarding business process, we use the Application Form object. To transition from the Application Intake stage to the Risk Screening stage, a criterion is that the applicant must fill the required fields on the application form. Here, add a condition in the Add Criteria and Conditions section to make sure that all fields on the application form are completed.

            In the Risk Screening stage, assign a mid-office agent to validate the documents. Assign the agent as the user in the Validate Permissions section. In the Add Step Definition section, create a step definition to start employee verification by using Integration Definition as the step type.

            See Also

             
            Loading
            Salesforce Help | Article