Generally, any process comprises a number of steps, which lead towards the overall goal. Workflow process consists of a number of workflow activities. The workflow activity is a piece of work that will be done by combination of resources and computer applications.
Table 6.18. Activity attributes
Name | M/O | Description |
---|---|---|
Name | O | Text used to identify process activity. |
Performers | O | Link to entity workflow participant. May be an expression. Default: Any Participant. |
Start mode | O | Describes how the execution of an Activity is triggered. |
Finish mode | O | Describes how the system operates at the end of the Activity. |
Deadline | O | Specification of a deadline and action to be taken if it is reached. |
Priority | O | A value that describes the initial priority of this activity when the execution starts. If this attribute is not defined but a priority is defined in the Process definition then that is used. By default it is assumed that the priority levels are the natural numbers starting with zero, and that the higher the value the higher the priority (e.g.: 0, 1, ...). |
Limit | O | Expected duration for time management purposes (e.g. starting an escalation procedure etc.) in units of DurationUnit. It is counted from the starting date/time of the Process. The consequences of reaching the limit value are not defined in this document (e.g. vendor specific). |
Icon | O | Address (path- and filename) for an icon to represent the activity. |
Documentation | O | The address (e.g. path - and filename) for a help file or a description file of the activity. |
Description | O | Textual description of the activity. |
Activities are associated with their performers (which are workflow participants), and application assignments. Optional information about activity may be associated with: starting and stopping manner, usage of specific workflow relevant data, preconditions for starting and postconditions for finishing the activity.
The following diagram illustrates the generic structure of activities:
Activities and other activity-like objects are inserted using buttons on graph's "Toolbox" toolbar.
Although it is possible to create a new activity through the property panels, the usual way to do it is through the graph component.
The following table shows the picture of how the graph represents a certain XPDL activity type, and short description of each type of the activity:
![]() | Start event activity - the place where the process begins. |
![]() | End event activity - the place where the process ends. |
![]() | Manual (No implementation) activities are atomic (Generic Activities). They are the smallest units of work, although even this activity may produce more than one work item for its performer. |
![]() | Task-Application activities are atomic (Generic Activity). They are the smallest units of work. |
![]() | Subflow is another activity type. It implements a whole new workflow process. Process definition within the subflow is entirely independent from the first one (where subflow activity resides). It has its own set of activities, internal transitions, participants, application definitions and other workflow relevant data. When clicking on the box with the "plus" sign, the graph of the sub-flow gets shown. |
![]() | An activity may be a block activity that executes an activity set , or map of activities and transitions. Activities and transitions within an activity set share the name space of the containing process. When clicking on the box with the "plus" sign, the graph of the activity set gets shown. |
![]() | Dummy (route) activity does nothing on its own. This type of activities is used for exclusive synchronization and constructing complex and sophisticated "exclusvie" transitional conditions |
![]() | Dummy (route) activity does nothing on its own. This type of activities is used for parallel synchronization and parallel (unconditional) branching |
Icons for inserting different types of activities from the graph
toolbox are the same as the ones included in the previously explained
picture of the activities in the graph. Graph's toolbox icon for
inserting Start event activity into the graph is and for inserting End event activity into is
. For the manual activity, there is a toolbox
icon
, for Tool activities
, for subflow activities
, for block activities
and for route activities
(for exclusive gateway route activity) and
(for parallel gateway route activity). Once
selected, mouse cursor will show what type of object you'll insert.
Activity is created using some default values for their properties,
which typically are to be changed. Right clicking the object in the
graph shows a context menu, and there is item representing action for
getting property panel. Different than others, Block and SubFlow
activities have additional menu item "descend into..." which is used
to display the graph of the referenced ActivitySet/Workflow
Process.
Beside this, TWE offers a special feature to select an Icon for particular activity. When you open activity's property panel, for the Icon entry you can select some of the additional Icons we offer (this list can be easily extended by putting more icons in tweactivityicons.jar file). The selected icon will appear instead the default one.
In this section are explained various property panels concerning different types of activities: activities without implementation (manual), sub-flow, route, tool and block activities. All information are organized in several tabs: general, type, transition restriction, simulation information, and extended attributes.
![]() | Tab has tree parts. First part contains activity id, name, performer (can be a reference to a participant or an expression), start mode (can be automatic or manual) and finish mode (can be automatic or manual). Second part shows all deadlines and also offers toolbar buttons with options to handle list of deadlines. Third part contains priority (describes initial priority for activity), limit (expected duration - for time management purposes), icon (reference to the icon representing this activity), documentation (reference to an external document) and description. Fields icon and documentation have drop down list to select one of the offered icons. If selected, this icon will replace the original one representing this activity within the graph. (the list of available icons can be extended by putting additional icons within the tweactivityicons.jar file) |
This tab contains some specific data concerning the particular
type of an activity. For activities without implementation (manual)
this tab doesn't contain any specific
data.
Block activity type property panel contains information about activity set id, which is a reference to defined ActivitySet (re-usable block of activities and transitions which shares the context of the workflow process where defined). A block activity | ![]() |
![]() | Task-application activity property panel enables to define a reference to the application required for enactment engine to run, in order to perform the activity. Basically, this tab allows you to pick the desired application by selecting it from the combo-box, and then allows definition of actual parameters (variables or expressions) to pass to the referenced application depending on its formal parameters. |
Subflow
Firstly, attribute id should be set. Id defines workflow process that will be executed. In TWE you are setting this attribute by picking the one of the WorkflowProcesses defined within the combo box. Beside the combo, you have a shortcut to display the properties of the WorkflowProcess selected within the combo. Then, execution (mode) attribute should be set. Synchronous execution mode suspends execution of calling process until sub-flow is finished. Asynchronous mode, spawns a new thread of execution for sub-flow process, which is then executed at its own pace, independently from calling workflow process. While entering actual parameters that will be passed to subflow process, TWE shows the list of corresponding formal parameters of the referenced sub-process. | ![]() |
![]() | When gateway (routing) activity is selected, type tab allows to change the gateway type from parallel to exclusive or vice-versa. In the case of exclusive gateways with more than one outgoing transition from the gateway, the order of calculating outgoing transition conditions is important. This order is determined in XPDL by the order of TransitionRef elements within its TransitionRefs collection. From here, you can control that order. The way of doing it is to simply change positions of the target activities (the activities that outgoing transitions are leading to) within the given list. |
Here are defined various information about simulation: whether the activity is instantiated once or multiple times, cost, waiting and working times and duration. | ![]() |