...
Login to Adonis in order to create the first process model that can be published to the system.
After login into Adonis, the following screen will appear:
...
Create a new business process diagram
A new diagram can be created by clicking on the icon 'Create Business Process Diagram' in the modul 'Design & Document'.
A new diagram will open. Enter a diagram name.
...
Create and edit a process modell
...
For modelling a pool select the pool element in the shape library. Via click into the modeling area the pool is created in the process model. Rename the Pool into 'Onboarding'.
The same approach is done to model the swimlanes. In order to rename the swimlanes, the desired element has to be selected and then clicked. Now it is possible to individualize the label. In this case the pool stands for a superior company and the lanes stand for departments in this company. On the one hand there is the Human Resources Department (“HR”) and on the other hand, there is the IT department (“IT”).
Model a start event
...
For modelling a start event select the start icon in the shape library. Via click into the modeling area the start event is created in the process model and can immediately be renamed.
Model an activity
...
Via the fast modeling feature of Adonis this can be done. Select the start event and a symbol preview will be displayed. Select the task symbol. Via drag and drop, the task can be placed in the desired position in the process model.
The labeling can be done immediately.
Model an AND Gateway
...
Select the three dots to the right of the activity and choose the symbol 'Non-exclusive Gateway'.
Now, two new activities can be placed into the HR and the IT lane. The HR department gets the task to “organize the desk”, meanwhile the IT department should take care of “creating a network account”.
A forking AND gateway has to be closed at the end, so that the process is able to go on with the next tasks. Therefore a new AND gateway have to be added to the diagram and placed at the point where the parallel part should end. For connection the activity 'create network account' and the AND-Gateway, click on the symbol 'Create relation' and click on the AND-Gateway.
The HR department now gets the task to “organize the desk”, meanwhile the IT department should take care of “creating a network account”.
Model a XOR Gateway/Exclusive Gateway
...
In order to extend the process, a XOR Gateway has to be added after the AND Gateway.
To clarify what kind of decision has to be made, this XOR can immediately be labeled like all the other elements (e.g. “Hardware necessary?”).
It is necessary to label the transitions in order to clarify which way belongs to which decision. Edit the outgoing sequence flows via double click and enter 'Yes' or rather 'No' into the field 'Name' in the 'General information'.
If hardware is required, the IT department is also given the task of ordering it. Otherwise, the personal file can be archived immediately.
Model script or mail node
...
For changing the type, highlight the activity symbol, click on the wrench icon and choose the activity type 'Script'. The procedure for modeling mail nodes is identical, only here is the activity type 'Send'.
Model an end event
...
Insert an end event after the last activity of the process.
Save a process model
...
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. |
...
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. |
...
Open the 'Automation data' of an activity via double-click. Enter a processing time for this activity into the field 'Duration' in the area 'Manual/User task'.
The format in which the duration has to be entered: HMM - like 830 = > 8 hours 30 Minutes.
Add tasks 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. |
...
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 |
...
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.
...
Deployment to the system
The publishing (deployment) of the process to the system can be realized by choosing the option 'Deploy process' from 'Import/ExportAutomate' in the the modell's menu. For this, the user needs the role of workflow-designer in the the system to be able to publish the model.
...
Automatically, Adonis starts the deployment check. If there are any errors, a messages appears and the validation area will be opened. Here, all errors will be listed.
...