...
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) . | ||||||
| Smartform | Here the definition of the Create a smartformis entered. | ||||||
| Section Definition | Here theSection Handling of the smartform is entered. |
| Info |
|---|
|
...
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. |
...
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 |
...
1.First, the activity must be selected and the automation properties opened. The first thing to add in the popup is a new event (see figure).
...
2.The ActionHandler must now Necessary ActionHandlers can be parameterized in the new row. The basic settings for an event can always be found on the associated documentation page (YearIDGenerator). The picture shows the parameterization for generating a number. 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.
...
Reference
...
Attribute Name
...
Attribute Description
...
...
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. For renaming an instance name after process start, add a new ActionHandler. According to the documentation, only one parameter has to be added to this handler (instanceName). The value of the parameter can be used to specify how the name of the new instance should be composed. Static values can be entered or values from variables. To access such variables, the mask "$ {... ..}" must be used. In this case, we want to access the previously created process variable "newNumber".
...
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.
...
| Note |
|---|
Please consider that the order is important when ActionHandlers build on each other. |
Attributes at XOR Gateways
...
Open the 'Automation data' of the XOR Gateway via double-click. Enter a decision handler, like '
com.dooris.bpm.actionhandler.VariableDecisionHandler' into the field 'HandlerClass' and add the variable name that contains the value of the decision.
Additionally, parameterization is required at the outgoing sequence flows. Each sequence flow must be given the value that the variable (doc_hardwareNecessary) assumes when making a decision. Open the 'Automation data' of a sequence flow via double-click and insert the value of the variable into the field 'ID'. This must be done for each outgoing sequence flow.
...