LinkedIn
Copied!

Table of Contents

Steps in a case life cycle

Version:

Only available versions of this content are shown in the dropdown

A step in your case life cycle represents a single assignment in your business process. By adding a step, you define a task that a user, your application, or an external application performs to move a case closer to resolution.

A step is the most granular element of your business process and represents one action in your case. A step can be a user action, such as collecting information from a customer, or an automated action that an application performs, such as sending an email after a business process reaches a resolution. To save resources and speed up application development, you can select from a wide variety of automated steps. For greater flexibility, many steps offer additional configuration options, so that you can meet your precise business needs. For example, in a step to send emails, you specify a receiver or a group of receivers, a subject, and a message content. Because steps represent single actions, use verb and noun combinations to name steps.

The following figure presents a set of related steps:

Visualization of actions in a business process

When you visualize your work by adding steps to a case life cycle, you clearly communicate what actions your business process requires to reach a resolution, and you organize your work in the most efficient way.

  • Step types

    A step is the most granular element of your business process and represents a single action. Each step in a process has a type, based on the functionality that the step provides. By using a variety of step types, you can make your cases more interactive and ensure that your business processes include all relevant and necessary actions.

  • Adding single steps to processes

    Model your business process with basic tasks that users or automations resolve, by adding steps to your case life cycle. When users complete steps, your case moves closer to its resolution and to achieving your business goal.

  • Collecting information from a user

    Gather the information that your business process requires by creating an assignment to collect that data from users. For example, a customer service representative can enter personal details and income information from a client during the loan request process.

  • Adding instructions to assignments

    Provide users with guidance on how to complete their tasks by adding instructions to assignments. When you add instructions for completing steps, you give users independence, and accelerate case resolution.

  • Requesting approval from users

    Ensure that your business processes meet your organization policies and requirements by requesting approval from users. After reviewing case details, users can approve or reject a case and bring the case closer to resolution.

  • Adding an automated step to a process

    Save time and design more efficient business processes by adding preconfigured steps to your case types. When you include a precofigured step in your case life cycle, you provide an automation that an application performs to bring a case closer to a resolution.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.