Process components

The following section introduces some new concepts and terminology that are used within Process Designer. More detailed information about each of these items is found later in this chapter.

Each process can consist of the following components:

A start point

Start points enable you to create an automatic action instance before defining a process Start status. For more information about start points, see Start points.


Statuses are the stepping stones that the process progresses by. Each process must have a Start status and End status. The Start status is the status at which the process starts, and a new instance of the relevant business object is created. The End status is the status at which the process becomes read-only. We recommend that when you create a new process, first add the Start and End status before adding the other process components.

For more information about statuses, see Statuses.

Action instances

Action instances define what a user can do at a specific stage of the process. There are three types of action instance:

When you are designing a process, you sometimes need to make changes to either an object or a window that is used by the process. You can do this from the process diagram by right-clicking the required Action icon, then clicking either Modify Action Window or Modify Action Object. The object or window for the action appears in the appropriate designer. Some actions may have multiple windows associated with them. In this instance, a dialog appears from which you can select the required window.


Assignments are one of the most important components of a process. They ensure that the process is always on at least one user’s Workload List, and has constant visibility. You can assign processes to roles, groups or users. This usually occurs automatically. You should have at least one assignment for every process.

There are two types of assignment:

For more information about assignments, see Assignments.

Using Process Approver, you can configure an e-mail to be sent that includes a link to the appropriate process in Web Desk. For more information, see Process Approver.


Tasks are sub-processes. Each task can have its own process consisting of assignments, action instances and so on, and each task has a Start and End status. For example, you can specify who will implement and complete the task and you can schedule when they must complete the task. For more information, see Tasks.


A precondition is a condition that must be true in order to make available the action instance that follows it. For example, all Tasks must be complete before the Resolve action becomes available. For more information, see Preconditions.


Each decision has a negative and a positive outcome. If the outcome is negative, the process goes to one stage in the process, and if the outcome is positive, the process advances to a different stage in the process. For more information, see Decisions.

Process rules

Every process must have a Start and End status and at least one action. You must link all the process nodes before the system can validate the process or you can activate the process. For more information, see Validating and activating processes.