|
|
pl:dydaktyka:dss:lab1 [2017/10/09 23:11] kkluza [Creating a new process model] |
pl:dydaktyka:dss:lab1 [2019/06/27 15:50] |
====== Lab. 1: Working with the Activiti platform ====== | |
| |
===== Signavio Process Editor ===== | |
| |
Please sign up for the Signavio Platform: [[http://academic.signavio.com/p/register?link=0b77d60921ec4ab2ac93286867a9af7d|Registration for the Signavio BPM Academic Initiative]] | |
by selecting: //I agree that anonymized versions of all models I create using this platform can be made available for research purposes.// | |
| |
To log into the editor, please select **Academic Login** on the [[http://www.signavio.com/bpm-academic-initiative/|Signavio BPM Academic Initiative]] page. | |
| |
[[http://www.manning.com/rademakers2/|{{ http://www.manning.com/rademakers2/rademakers2_cover150.jpg}}]] | |
===== Activiti BPM Platform ===== | |
| |
Auxiliary materials for the laboratory: | |
* [[http://www.activiti.org/userguide/|Activiti User Guide]] | |
* a book [[http://www.manning.com/rademakers2/|Activiti in Action]] | |
| |
For the needs of today's classes you can deploy Activiti platform from the website: | |
[[https://www.activiti.org/download-links]] (the lab is prepared for Activiti version 5) | |
on the Apache Tomcat or JBoss Application Server. Then, you can launch the Activiti Explorer | |
in your browser: http://localhost:8080/activiti-explorer, | |
and then sign in to your account: | |
login: kermit | |
password: kermit | |
| |
You can also use the temporary server version at our server: http://192.168.1.145:8080/activiti-explorer/ui/ | |
| |
When logged in, you should have noticed the top bar displaying the menu of 4 icons for administration of: | |
* // Tasks // - tasks, | |
* // Processes // - processes, | |
* // Reports // - reports, | |
* // Manage // - other issues, such as users, groups, database management, or process implementations. | |
| |
==== Creating accounts ==== | |
| |
In the Groups tab (Manage menu), look at the existing user groups. | |
As an administrator user, we can use the default ''kermit'' user for a while, | |
but we will need a non-admin user. | |
| |
So, create a new user for you. Remember about a unique identifier! | |
Assign your user to some groups but not the Admin group. | |
| |
==== Creating a new process model ==== | |
| |
For better understanding of the BPM platform, we will create a very simplified model of the offer management process. | |
| |
From the menu, select **Processes**. You should see 3 tabs: | |
- // My instances // -- to observe the existing instance of the process, | |
- // Deployed process definitions // -- to run processes deployed on the Activiti platform, | |
- // Model workspace // -- to create new models and deploy or edit existing process models. | |
| |
In the // Model workspace // tab, click on the // New Model // button and create a new process model using the Activiti Modeler. Give your model a name and a description. | |
| |
In the ** Activiti Modeler ** application window, set the process attributes (on the right side of the window). | |
The key elements are: the process identifier (//Process identifier//) and the process name (//Name//), as | |
using them we will be able to distinguish our process from other processes or processes of other users. | |
Please also fill in the author's field (//Process author//). | |
| |
==== Modeling a simple process ==== | |
| |
By dragging from the left menu item // Start event // we will start modeling the target part of the process. | |
At the beginning we model a very simplified process, as follows: \\ | |
{{en:teaching:bim:lab1:process1-diagram.png|}} | |
| |
As in the case of the process, the same for BPMN elements on the right side we set the attributes. | |
| |
* For // Start event event: | |
* // Documentation //: Start proceeding with an offer. | |
* // Initiator //: initiator (this will hold the user who initiated the process) | |
* // Name //: Offer received | |
* // Form properties // - click on ... and in a new window we set the following screenshot: \\ | |
{{en:teaching:bim:lab1::form-properties.png|}} | |
| |
* For task // Specify offer //: | |
* // Documentation //: Please add available specification for an offer as attachments. | |
* // Assignments //: we have 3 choices \\ | |
* '' assignee '' - assign a task to a specific user, | |
* '' candidateUsers '' - assign a task so that any of the users can execute it, | |
* '' candidateGroups '' - assign a task so that any user belonging to the assigned group can execute it. \\ | |
| |
In our case, we only set the variable '' assignee '' to the value of '' $ {initiator} '' - this means that as the task performer, we indicate the person who started the process. | |
| |
In addition, for this task we set // Form properties //: | |
* // Specifications details // Specification (specDetails) - The level of detail of the order specification (until we set it as a boolean), then we will want to convert that to enum (accurate, sufficient, insufficient). | |
* // Person responsible // (id: '' responsible '') - person assigned to the formal analysis of the request (responsible for the analysis); Here you will assign that person and assign it to the variable. | |
| |
| |