...
At the start event all general process information will be defined.
...
Reference | Attribute Name | 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(USER_NAME), group(GROUP_NAME) is entered. | ||||||
| Owner | Here a group or a user who “owns” the process in the system is entered, e.g. user(USER_NAME), group(GROUP_NAME) 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, e.g. user(USER_NAME), group(GROUP_NAME) is entered. | ||||||
| Count Critical | Count Critical must be activated for calculating Critical Path Method (CPM) . | ||||||
|
Form | Here the definition of the Create a |
formis entered. | ||||||||
| Section Definition | Here theSection Handling of the |
form is entered. |
| Info |
|---|
|
...
At the swimlane the responsible group / user for all activities in this lane will be defined.
...
Reference | Attribute Name | Attribute Description | ||||||
|---|---|---|---|---|---|---|---|---|
| Assignee | Here a group or a user who is responsible for working on the tasks is entered, e.g. user(USER_NAME), group(GROUP_NAME) is entered. |
Attributes at activities
General configuration options
Open the 'Automation data' of an activity of type 'Send' via double-click.
Reference | Attribute Name | Attribute Description | ||||||
|---|---|---|---|---|---|---|---|---|
| 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. | ||||||
| Script task | 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
...
Click on the plus icon next to 'Tasks' in the area 'Manual/User task'. A new row will be added.
In the newly created row some fields must be inserted. Data can be entered into the corresponding cell by double-clicking.
Reference | Attribute Name | Attribute Description | ||||||
|---|---|---|---|---|---|---|---|---|
| TaskName | Name of the task. | ||||||
| Role Assignment | The role assignment of the activity can be overridden for this task. | ||||||
| Description | Further instructions for processing the task can be given here. This description will be displayed as soon as the task is generated by the system. | ||||||
| Links | Links can be added here, which are displayed to the user when editing the task. |
Add events to an activity
...
Open the 'Automation data' of an activity of type 'Send' via double-click. Enter the recipients, the subject and the content of the email.
Reference | Attribute Name | Attribute Description | ||||||
|---|---|---|---|---|---|---|---|---|
| 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 | ||||||
| Body | 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
...
2.Necessary ActionHandlers can be parameterized in the new row. The basic settings for an event can always be found on the associated documentation page (RenameInstanceHandler).
...
Reference | Attribute Name | Attribute Description | ||||||
|---|---|---|---|---|---|---|---|---|
| EventType | Specifies whether the ActionHandler should be executed when the activity is reached (input node) or when it exits (output node). | ||||||
| ActionName | Can be chosen freely. Serves for a better overview of the list of events. | ||||||
| ActionClass | Defines which ActionHandler is to be executed. It can be copied from the wiki page. | ||||||
| Parameters | Depending on the ActionHandler, "Parameters" must be passed. The description can be found on the wiki page. In this context, the parameter 'mandatoryFields' and a freely chosen variable name has to be entered. |
3. You can add one or more actionhandlers according to your processes.
...
In order for the system to be able to clearly assign which of the two paths to be taken, it is necessary to maintain attributes at XOR Gateways. This parametrization is only possible in conjunction with a smartformform. If no ActionHandler is assigned to this Gateway, the system automatically creates a popup so that the decision can be made:
...