...
For many elements, the caption may be altered by double-clicking on it. In the first step, the command 'Create personal file' should be executed. For this, a activity node for one of the two options must be created, which takes place after the starting event. This activity node must then be connected to the starting event via a transition.
...
Reference | Description | ||||||
|---|---|---|---|---|---|---|---|
| Pool shape | ||||||
| Description of the pool to reflect the greater organizational unit | ||||||
| Swimlane reflecting subordinated organizational units | ||||||
| Start event of the process model | ||||||
| First activity of the process model | ||||||
| Transition between elements of the process model to reflect the direction of the process |
Model an AND Gateway
Using an “AND” junction, multiple process steps will be completed at the same time. All of the given process steps must be completed before the process continues past this parallel-splitting of the process. In this example process, a parallel conjunction, with multiple concurrent activities, takes place after the first activity is completed.
...
By clicking on an empty position within the diagram, the process attributes may be edited. Now, the rolls must be assigned. Lastly, the role distribution must be defined within the swim lanes. This is also done using the attribute menu, found by clicking within the desired swim lane.
...
Attributes | Attribute Description | ||||||
|---|---|---|---|---|---|---|---|
Description | Description of the process, which will later be shown in the system (tooltip and process report). | ||||||
Starter
| Here a group or a user, who is allowed to start instances of a process definition, e.g. user(john.doe), group(pm) is entered. | ||||||
Owner
| Here a group or a user who “owns” the process in the system is entered. “Owner” means that this person is responsible for the process. | ||||||
Deployer
| Here a group or a user as workflow-designer who as workflow-designer is allowed to deploy the process in the the system system is entered. |
Form | Here the definition of the smart form is entered. |
Attributes at start event
The system specifications show only a portion of the attributes, which can be changed using the attribute editor. In any case, only a few of the attributes have any noticeable effect.
...
Attributes | Attribute Description | ||||||
|---|---|---|---|---|---|---|---|
Name
| Description of the process, which will later be shown in the system (tooltip and process report). | ||||||
Starter
| Here a group or a user, who is allowed to start instances of a process definition, e.g. user(john.doe), group(pm) is entered. | ||||||
Owner
| Here a group or a user who “owns” the process in the system is entered. “Owner” means that this person is responsible for the process | ||||||
Deployer
| Here a group or a user who as workflow-designer is allowed to deploy the process in the system is entered. | ||||||
Form Definition | Here the definition of the smart form is entered. |
Attributes at swimlanes
In addition each swimlane needs to be assigned to a user or group. The 'Attribute' can be altered by clicking on the swimlane header and altering the respective properties on the right side.
...
In essence, every activity must have a unique name and at least one task attached to it. Optional working time may also be included. Firstly, the activity attributes 'Create personnel file' is edited. For this, the activity must be marked and the attribute bar must be used. The previously-given name will be adopted in this window.
...
Attribute Name | Attribute Description |
|---|---|
Name | Description of the activity |
Duration | Here the duration in which the tasks of this activity must be completed can be entered. |
Tasks | Basically every activity must have its own unique name. If no task is explicitly defined for the activity, the system generates a task with the name of the activity. With the aid of the automation properties menu one or more tasks may be added for an activity. |
Events | Here events can be entered. Events or ActionHandler are special functions that are executed as soon as a specific process step is reached or left. |
Add processing times to an activity
...
To achieve this click on the drop-down 'No values' next to Tasks. A pop-up window appears. By clicking on “add” a new task can be entered. Any number of tasks may be created, all of which must be completed before the activity is counted as complete. This step must be followed for all activities.
...
Attributes | Attribute Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
Name | Description of the process, which will later be shown in the system (tooltip and process report). | ||||||||
Duration
| Entering and changing of time durations.
| ||||||||
Task
| Using the dialog behind the points, multiple tasks may be given for a single activity. | ||||||||
Events | Here, so-called ActionHandlers for the activity may be integrated. |
Add events to an activity
...
The activity will change to a mail node with a envelope symbol on the upper left of the node. In the 'Attributes (Mail Node)' the parameter can be added.
...
Attribute name | Attribute Description |
|---|---|
Name | The Description of the Node can be altered here. |
To | The recipients can be defined here. On the one hand, groups and user definitions (group (NAME_DER_GRUPPE) / user (NAME_DES_USERS)) can be used again. The email can also be sent to the current processor of the Swimlane "HR". In addition, fixed e-mail addresses or distribution lists can also be used here (e.g. it-asset@yourcompany.com). |
Subject | The subject of the email can be freely assigned. In this example, a variable is also referenced (the name of the process run). These variables can be used in the subject or in the text and are always masked with a $ {…}. As soon as the email is sent, the variable placeholders are replaced by their actual value. Further information on the variables can be found on this page: VariablesHelper |
Text | The email text can be designed in any way. Variables can also be used. The sending of HTML email and other settings are explained on this page: Mail Nodes |
Attributes at script nodes
...
The ActionHandler must now be parameterized in the next view. The basic settings for an event can always be found on the associated documentation page (YearIDGenerator). The picture shows the parameterization for this example. The event generates a consecutive number and saves it in a variable called "newNumber". The number can then be addressed in the second ActionHandler using this name.
...
Attribute name | Attribute Description |
|---|---|
Event Type | Specifies whether the ActionHandler should be executed when the activity is reached (input node) or when it exits (output node) |
Action Name | Can be chosen freely. Serves for a better overview of the list of events |
Action Class | Defines which ActionHandler is to be executed. It can be copied from the wiki page. |
Mandatory Fields | Depending on the ActionHandler, either "Mandatory fields" or "Parameters" must be passed. The description can be found on the wiki page. No parameters are required for this ActionHandler. You only have to enter something in "mandatory fields". |
Parameters | See above. |
Ok | Saves the attributes to the script node of the process model |
The event has to be saved in the script node of the process model. A new event must then be created (RenameInstanceHandler) for the current example. However, parameters are required for this ActionHanlder. To do this, click into the empty row belonging to the column 'Parameters' after having added a new event. A pop-up will appear where the required parameters can be added.
...