Defining a life cycle for a case type

You can define a life cycle for your case type. By organizing your business logic into stages, processes, and steps, you can create the different paths that a case follows from creation to resolution.

Note: Because life cycles are modular, you can iteratively define stages, processes, and steps as you build your application. The following procedure provides one example of the order of steps that you can take.

For each high-level phase that a case can enter at run time, create a stage.
- Create primary stages for expected behavior.
- Create alternate stages for exceptions.
Configure each stage by performing the following steps:
1. Create a process for each logical group of tasks that a case follows when it is in the stage.
  
  Processes can run conditionally, in sequential order, or when a case enters the stage.
2. Define the supplemental actions that a case worker can take while a case is in the stage.
  These actions, such as transferring an assignment, do not move a case closer to resolution.
Configure each process in a stage by adding one or more of the following steps, which users, your application, or an external application perform:
For more information about the functionality that each type of step provides, see: Step types.
Define the supplemental actions that a case worker can take while a case in any stage of the life cycle.

These actions, such as transferring an assignment, do not move a case closer to resolution.

You can test your life cycle by creating a case and processing it.