Activities

Abstract Activity

An abstract activity is an activity that has no specific type. You can use it when the exact type of an activity is not important, for example when designing a draft of a process model. You can later convert the abstract activity to one of the other activity types such as human activity, automated activity, and so on. For more information about abstract flow objects, see Two Perspectives Approach .

Human Activity

A human activity is an activity in the process that is performed by a person. A task needs to be assigned to the human activity. When the process is at the point of the human activity, the assigned task is shown, for example, in the universal worklist, and can be executed by a person. For the task, input and output data mappings need to be defined. For more information, see Modeling Human Activities , Working with Tasks and Managing Processes and Tasks with the Process Desk .

Automated Activity

An automated activity is work that is performed by a system. To make the automated activity work, a service interface definition and an operation need to be assigned to the automated activity. In addition the input and output data mappings need to be defined. For more information, see Modeling Automated Activities

Referenced Sub-Process

A referenced sub-process is an activity in the process that is a graphical representation of another independent process. When the process flow reaches the referenced sub-process, the other independent process is called. The parent process and the referenced sub-process communicate through input and output data mappings. For more information, see Modeling Sub-Processes .

Embedded Sub-Process

An embedded sub-process is a compound activity that is defined as a flow of other activities. The embedded sub-process is dependent on the parent process and cannot be executed standalone like the referenced sub-process. The embedded sub-process has a local process context, which is not visible for the parent process. You can further embed another sub-process in an embedded sub-process and another one down the line, and so on. Therefore you can have multiple parent processes, but only one root process at the top.

Mapping Activity

A mapping activity can be used to transform complex data from data objects in the process context into more simple data. Rules set can be used as a transform in a mapping activity. To make the mapping activity work, the mappings between the data objects in the process context need to be defined.

More information: Transforming Complex Data to Simple Data with Mapping Activities , Working with Rules

Reporting Activity

A reporting activity is used to collect data from the process context, and you can perform process analytics on this data. The reporting activity references a reporting data source and indicates where in the process data is gathered for reporting. An input mapping needs to be defined for the reporting activity to specify which data from the process context is collected by the reporting activity. For more information, see Modeling Reporting Activities .

Notification

A notification is used to send e-mail notifications from the process. You need to specify the recipients and you can parameterize the subject and message texts that are sent.