Considerations for Working with Stage Management

Consider these points when you work with Stage Management.

• Set up the picklist values for the reference object to configure stages and record types to suit your business process.
• Stage Management doesn’t support Autolaunched Flow with pause elements.
• You can create up to 20 active stage definitions, with each step definition limited to 20 steps.
• The Enterprise Edition orgs have a limit of 100,000 stage transition plans per month, while the Unlimited Edition orgs have a limit of one million transition plans per month. When transition plans are defined at both the stage transition and target stage levels, stage management runs a joint transition plan. For higher usage of the transition plan, contact your account manager.
• Transition entry criteria can have up to five rules.
• Each record type of a reference object can have only one active definition.
• The generation and execution of the transition plan occur asynchronously and depend on resource availability.
• When defining a stage transition, add criteria and conditions to evaluate whether field values are null. Evaluation behavior differs based on the criteria level.
  • Parent Criteria: Null operators aren't available in the Formula Builder. Numeric null values are treated as 0. Comparison operators (>, >=, <, <=) evaluate a null field as 0.
  • Child Criteria: SQL evaluates existing child records. Null values aren't treated as 0. If no child records exist, the criteria evaluate to True.
• Stage Management supports objects that include Case, Opportunity, Application Form, Application Form Product, Applicant, Care Program Site, Collection Plan, Claims, Research Study Candidate, Care Program Enrollee, Dispute Item, Information Verification, Party Profile, Party Financial Asset, Work Order, Work Order Line. In addition, objects from the Automotive, Insurance, Manufacturing, Nonprofit, Public Sector, and Education clouds are supported.
• The Omniscript and Screen flow steps aren't completed automatically, go to the task to manually complete the steps.
• Stage Management doesn't support Service Type integrations.
• You can assign manual tasks only to users or queues; you can't assign manual tasks to groups.
• The Stage Management managed package isn’t supported for ISVs.
• When you define the conditions for a parent object, you can access all its lookup fields. For standard lookup fields, you can select related fields. For example, for the Application Form parent object, select related fields such as ApplicationForm.Account.AccountSource. However, polymorphic fields only support field IDs. For example, for the Owner polymorphic field, you can select only field IDs such as ApplicationForm.OwnerId.
• For objects with a self-lookup field, set conditions to make sure that the evaluation is accurate. The self-lookup field acts as a reference to the parent object criteria. If the self-lookup field isn't set, the condition evaluates to false. In the child object criteria, the self-lookup field identifies all child objects whose IDs match the parent object IDs. For example, to close a case only if all related child cases are closed, set the lookup field for the case child object to ParentId, and set the condition to Stage=Closed.
• 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.
• Assigning a stage definition to a record with stage assignments associates the stage definition with the record. The stage definition will be used for all future stage transitions and won’t change, even if the record is updated.
• Define manual sharing or custom Apex sharing logic for fulfillment steps and orchestration plans according to your business needs for community users.