- In the navigation pane of Dev Studio, click Records.
- Expand the Process category, and then click Case Type.
- In the list of case type instances, select the case type that you want to edit.
- On the Stages tab, add a stage to your case type:
- To add a primary stage, in the Primary Stages section, click add primary stage, and then in the text field, enter a stage name.
- To add an alternate stage, in the Alternate Stages section, click add alternate stage, and then in new text field, enter a stage name.
- Configure conditions for skipping a stage:
- To ensure that a case always enters a stage, in the Skip stage list, select Never.
- To skip a stage by evaluating a When rule, in the Skip stage list, select When Rule, and then in the text field, enter a When rule name.
- To skip a stage by using an expression, in the Skip stage list, select Expression, and then in the text field, enter an expression name.
Note: You can configure skip conditions for primary stages only. A case cannot skip the last stage.
- Configure case behavior when a stage is complete:
Choices Actions Move the case to the next stage In the When all processes in this stage are complete section, select Automatically move to next stage. Note: This option is available for primary stages only. Allow users to perform optional actions before moving the case to the next stage In the When all processes in this stage are complete section, select Wait for a user action. Resolve the case
- In the When all processes in this stage are complete section, select Resolve the case.
- In the Resolution status field,
enter a status that a case enters upon resolution.
For example: To display a successful resolution status, enter Resolved-Completed.
- Optional: To delete any work that remains after the case resolution, select the Delete open assignments check box.
- Optional: To delete any dependent cases after the case reaches resolution, select the Delete open assignments check box.
- Optional: To display a case progress status, in the Set case status on stage
entry field, define the status that a case acquires when
entering the next stage.
For example: To display a status for an insurance case that enters a stage of reviewing gathered insurance data, enter Pending-Review. Tip: You can reuse existing statuses or enter a new value.
- Optional: To provide enough information to process a case, in the
Requirements section, define the requirements that the
case needs to meet before entering the next stage:
- To validate data, in the Validation field, enter validation that the case needs to pass before entering the next stage.
- To assign time frames to the stage and ensure that users resolve work in a timely manner, in the Service level field, enter a service-agreement rule.
- To ensure that the case has at least one attachment before entering this stage, in the Attachments required for stage entry section, click Add required attachment, and then select an attachment category.
For example: You can validate format of personal details that users provide or require a document with an expertise of damage of insured goods.
- In the Automatically launched processes section, define
processes that occur in the case without additional triggers:
The Create stage has a default CreateForm_Default automatically launched process. For more information about the Create stage, see The Create stage.
- Click Add process.
- In the Process field, enter a process that you want to run.
- In the Start process list, define whether a process runs always, when a When rule evaluates to true, or when an expression evaluates to true.
- In the Start Step list, define whether the
process runs after the previous step or upon a stage entry.The first process in a stage always runs upon a stage entry.
- Optional: To apply time frames for users to resolve the process, in the Service level field, enter a name of a service-level agreement rule that you want to use.
- Optional: To add more processes, repeat steps 9.a through 9.e.
For example: The following figure shows a sample configuration for a process that starts after a When rule evaluates to true and that users need to resolve within a goal and deadline defined by a service-level agreement rule:
- Optional: To increase flexibility and provide additional processing in a case, add an
- In the Optional Processes section, click Add process.
- In the Process field, enter a name for the process that you want to use.
- In the Visible list, define whether a process runs always, when a When rule evaluates to true, or when an expression evaluates to true.
- Optional: To add more processes, repeat steps 10.a through 10.c.
For example: You can add an optional process to review an insurance claim by a manager if an insurance amount exceeds a specific value.
- Optional: To allow users to perform out-of-sequence tasks that do not influence the main
events in the case, in the Optional actions section, add an
- Click Add action.
- In the Local Action field, enter an action that you want to use.
- In the Visible list, define whether a process always runs, when a When rule evaluates to true, or when an expression evaluates to true.
- Optional: To add more actions, repeat steps 11.a through 11.c.
For example: You can add an optional action responsible for updating the personal details of a customer. If necessary, a customer service representative (CSR) can update the details without interrupting the main case processing.
- Click Save.
Adding stages through a rule form is suitable for advanced developers. If your use case does not require advanced configurations, populate your case types by using the Case Designer tool, which helps you visualize your business processes in a low-code way. For more information, see Adding a stage to a case life cycle.