- The invocation of an operation.
- A step in a business process.
- An entire business process.
Activities can be decomposed into sub activities if necessary and does not have to be atomic.connections available in DCR Graph are:
|Condition||A condition between two activities ensures that the second activity cannot be executed unless the first is excluded or has been executed at least once.|
|Response||A response, or goal, ensures that once the first activity has been executed the other activity becomes a goal, that must eventually be executed or excluded|
|Include||The include relation includes other activities upon execution|
|Exclude||The exclude relation excludes other activities upon execution|
|Milestone||The milestone relations blocks the second activity if the first is currently a goal (response) and included|
|Spawn||The spawn relation spawns a new sub-process|
- single-instance sub-process - meaning it is just a process embedded inside the parent graph
- multi-instance sub-process - which can be spawned to run separately of the parent graph
Sub-processes can either be created within the parent graph or created as it's own graph and linked into the parent graph using the import graph capabilities.simulated, either by one person playing all the roles or by several people each playing some of the roles found in the graph. This enables users to obtain a better understanding of how the graph works, simply by playing the graph as a computer game. The portal even offers "friends" that can be used to play certain roles, at the moment two friends are offered.
- Aggressive user - the aggressive user executes all activities that are enabled
- Lazy user - the lazy user only executes activities that are enabled and pending