Activities are assigned to a subprocess. At runtime, activities are assigned to a group of users using a work item. Activities consist of a name and an optional abbreviation.
Basic data
The following settings are maintained in the basic data:
Activation and changeability
Status control
Dynamic multiplication
Priority
Various settings that can be inherited (e.g. protocol)
In the basic data, only whether the agents can be extended is set. The indicator whether agents can be changed is only informative and is set automatically if either the agents can be extended or at least one agent assignment exists that allows the activation to be changed.
The Role setting can be used to control object navigation. For this purpose, a so-called navigation role is assigned to the activity, which can then be used as a criterion for navigation in objects.
Agent
At least one agent should be assigned to each activity. Agents do not have to be defined if either the agents can be extended (see Basic Data ) or the activity only contains tasks that are executed automatically in the background.
For the agents, you can define whether these are activated and whether the activation can be changed at runtime. It is also possible to control the activation of agents dynamically using filters.
The maintenance of agents is described in the Members chapter.
Possible agents
Once editors are extensible, additional users can be added to the process. The permitted users can be restricted with possible agents. If roles are used as possible agents, this role, any included roles, and all users contained in the role can be added at runtime.
The possible agents can be restricted dynamically using filter, see Formular editor.
Excluded agents
Agents can be excluded from processing an activity - for example, because they have performed the task to be checked or are the initiator of the process. Excluded agents are not sent a work item and cannot execute the activity and its tasks either as agent or as responsible, even if the user is directly or indirectly intended as a (possible) agent. However, executing tasks or completing activities as an administrator is possible. Forwarding the activity to an excluded agent is not possible.
The exclusion of agents can take place via role or expression and can be dynamically restricted by means of filter, see Formular editor.
Excluded agents are fixed when the work item is created. It is therefore not possible to exclude agents of tasks in the same parallel sub-process from processing..
Workitem text
Notification of an activity takes place using an SAP Business Workflow work item. A subject and a message must be defined for the notification.
The subject of work items is limited to 100 characters. However, there is no length restriction during maintenance because the final length cannot be determined when using expressions.
Text maintenance is described in the chapter Text editor .
Object List
The functionality and the distribution of the objects is described in chapter Object List of the Process.
Dates
The maintenance and function of dates is described in the chapter Dates.
Notifications
The maintenance and functionality of the notifications is described in the chapter Notifications.
Tasks
Each activity requires at least one Task. The order of the tasks can be changed by drag'n'drop but has a purely visual influence on the sorting in the UI. However, tasks can be processed in any order at runtime.
Container
The containers are described in the chapter Containers and Items.
The most important containers and items are described below:
Container/Item | Description |
|---|---|
HEADER | Kopfdaten |
ITERATION | Number of Iterationen |
CURRENT_AGENT | Current agent, if available |
FINISH_AGENT | Agent who finished the activity |
RUNTIME_STATUS | Current status at runtime |
If an activity can be dynamically multiplied, additional containers are available with which different agent groups of all multiples can be addressed. These agent groups also exist in the subprocess and behave identically.