Różnice między wybraną wersją a wersją aktualną.

Odnośnik do tego porównania

Both sides previous revision Poprzednia wersja
Nowa wersja
Poprzednia wersja
pl:dydaktyka:dss:lab1 [2017/10/09 21:11]
kkluza [Creating a new process model]
pl:dydaktyka:dss:lab1 [2017/10/12 12:57] (aktualna)
Linia 1: Linia 1:
-====== Lab. 1: Working with the Activiti platform ======+====== Lab. 1: Working with Activiti platform ======
 ===== Signavio Process Editor ===== ===== Signavio Process Editor =====
 +**This part will be required for the next classes!**
 Please sign up for the Signavio Platform: [[http://​academic.signavio.com/​p/​register?​link=0b77d60921ec4ab2ac93286867a9af7d|Registration for the Signavio BPM Academic Initiative]] Please sign up for the Signavio Platform: [[http://​academic.signavio.com/​p/​register?​link=0b77d60921ec4ab2ac93286867a9af7d|Registration for the Signavio BPM Academic Initiative]]
Linia 23: Linia 25:
   password: kermit   password: kermit
-You can also use the temporary server version at our server: http://​​8080/​activiti-explorer/​ui/​+You can also use the temporary server version at our server: ​\\ 
 When logged in, you should have noticed the top bar displaying the menu of 4 icons for administration of: When logged in, you should have noticed the top bar displaying the menu of 4 icons for administration of:
Linia 38: Linia 41:
 So, create a new user for you. Remember about a unique identifier! ​ 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 ==== ==== Creating a new process model ====
Linia 58: Linia 60:
 ==== Modeling a simple process ==== ==== Modeling a simple process ====
-By dragging from the left menu item // Start event // we will start modeling ​the target part of the process. +By dragging from the left menu the // Start event // element, ​we will start modeling the process. 
-At the beginning ​we model a very simplified processas follows: \\ +At the beginning, let'​s ​model a very simplified process as follows: \\ 
-{{en:teaching:bim:lab1:process1-diagram.png|}}+{{  :pl:​dydaktyka:bim:lab1:proces1-diagram.png ​ |}} 
 +As in the case of the process, the attributes for the BPMN elements we can set on the right side of the window. 
 +  * For the //Start event// element: 
 +    * //​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, set the following attributes as in the screenshot: \\ 
 +{{  :​pl:​dydaktyka:​bim:​lab1::​form-properties.png ​ |}} 
 +  * For the //Specify offer// task: 
 +    * //​Documentation//:​ Please add available specification for an offer as attachments. 
 +    * //​Assignments//:​ we have 3 possibilites \\ 
 +      * ''​assignee''​ -- assign a task to a specific user, 
 +      * ''​candidateUsers''​ -- assign a task so that any of the specified 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 notation means that we indicate the person who started the process (initiator) as the task performer.  
 +Moreover, for this task, set the following //Form properties//:​ 
 +  * //​Specifications details// (id: ''​specDetails''​) -- the level of detail of the order specification (as for now, we can set this as a boolean, and later we will convert it to enum, for representing more values like: accurate, sufficient, insufficient). 
 +  * //Person responsible//​ (id: ''​responsible''​) -- person assigned to the formal analysis of the request (responsible for the analysis); this is done for assigning a person and assigning it to the variable. 
 +So far, to test such a simple process, we abandon the further elements of the process. 
 +In the meantime, let's do one of the final tasks: // Approve offer // in which we set only the contractor -- the person assigned to carry out the formal analysis (please use the identifier of the defined variable). 
 +==== Start a simple process ==== 
 +After saving the model, closing the **Activiti Modeler**, go to **Activiti Explorer**. 
 +In the //Model workspace// tab, select your process from the menu, 
 +and from the list //Model action// choose **Deploy**. 
 +You should have been moved to the //​Deployments//​ tab (in **Manage**),​ where you can choose your process (by clicking on its name) in the //Process Definitions//​ \\ 
 +{{  :​pl:​dydaktyka:​bim:​lab1::​proces1-deploy.png ​ |}} 
 +Once deployed, from the //Deployed process definitions//​ tab, you can start your process with the **Start process** button.  
 +The following form should opened: \\ 
 +{{  :​pl:​dydaktyka:​bim:​lab1:​proces1-run1-form.png ​ |}} 
 +Complete the form with any data and click **Start process**. 
 +If everything is like it should be, under the tab **Processes** -> //My instances//,​ you should see the instance of your process. 
 +As the first task was assigned to the user who started the process, click the **Tasks** icon and go to the //Inbox// tab, where a task //Specify offer// should wait for you. 
 +Fill up the //​Responsible//​ field with the name of another user (eg ''​fozzie''​ or some predefined user); check the checkbox //​Specifications details//. Then click **Complete task**. 
 +Now click the **Processes** icon and go to the //My instances// tab to view the diagram, the task list and variables of your process. 
 +Since the //Approve offer// is waiting for another user, we log in to the account of the specified user (if it was ''​fozzie'',​ his password is: ''​fozzie''​),​ and then we finish the task //Approve offer//. 
 +We're going back to our account, checking if in the //My Instances// tab, a process has disappeared. 
 +The historical data of our process is stored in the database, which is quickly available in the //​Database//​ tab (click on the **Manage** icon). Look for the '​ACT_HI_PROCINST'​ table and find your process there. 
 +Because the installation of the Activiti with Activiti Modeler in the lab does not have a permanent database for models, we will save our model on disk. To do this, select //Show all// from the menu //​Deployments//​ and look for our process. Please save your process file (file with extension **.bpmn20.xml**) and view its syntax. Check the additional attributes of the '​process'​ tag as well as additional attributes of other process elements and note which are used by Activiti. 
 +==== Model development ==== 
 +Let's go back to the //Model workspace// page to enhance our model with gateways. 
 +Depending on the level of detail of the offer specifications,​  
 +if it is insufficiently detailed, we will want to ask the tenderer to provide additional information. 
 +To enhance our model, select the appropriate model, and then click //Edit model//. 
 +Please extend the model as in the following diagram: \\ 
 +An important element of the model is the use of appropriate conditions on flows from the XOR gateway (depending on the ''​specDetails''​ variable value). 
 +How to define the appropriate conditions for the gateway, you can check in the [[http://​www.activiti.org/​userguide/​index.html|Activiti User Guide]]. 
 +===== Further development of the model ===== 
 +=== Timer Boundary Event === 
 +Our subprocess consists of two tasks consisting in contacting the customer by email and calling to inform the customer about this email. In a very detailed version, we should have modeled the task of waiting for a response from the customer -- for simplicity, let's assume that when the customer has provided enough information on the phone, the user completes the "Call customer"​ task; otherwise, it will not finish until obtaining sufficient information. 
 +In the standard case, when the deadline for offer submission expires, the subprocess should automatically terminate and terminate the process. To do this, we can extend the process using the ''​Timer Boundary Event'':​ 
 +{{  :​pl:​dydaktyka:​bim:​lab1:​process5-eclipse-example.png?​800 ​ |}} 
 +The ''​Timer Boundary Event''​ element has the following attributes:​ 
 +  * ''​cancelActiviti''​ -- in our case it should be set to **''​true''​** for the subprocess to be interrupted when the event is called, 
 +  * ''​timeDate''​ -- sets a specific date (in the [[wp>ISO 8601]] format) when launching an event, 
 +<code xml> 
 +    <​timeDate>​2012-12-06T17:​00:​00</​timeDate>​ 
 +  * ''​timeDuration''​ -- sets the time that must pass until the event is triggered, e.g. for 3 days: 
 +<code xml> 
 +    <​timeDuration>​P3D</​timeDuration>​ 
 +  * ''​timeCycle''​ -- sets recurring intervals of time to trigger a periodic event, e.g. 5 repetitions,​ each of which lasts an hour: 
 +<code xml> 
 +    <​timeCycle>​R5/​PT1H</​timeCycle>​ 
 +To test the process and not wait too long for effects, I suggest setting the ''​timeDuration''​ to 2 minutes. 
 +Please test your model, and view the process instance diagram during this waiting (it should look similar to the model shown in the diagram below): 
 +{{  :​pl:​dydaktyka:​bim:​lab1:​process5-run-example.png?​800  ​|}}
-As in the case of the process, the same for BPMN elements on the right side we set the attributes.+At this point, the new "Timer job" should appear ​in the **Manage** -> **Jobs** tab. If necessaryyou can manually trigger ​the event with the **Execute** button: 
 + ​{{ ​ :​pl:​dydaktyka:​bim:​lab1:​timer-job.png  |}}
-  * For // Start event event: +=== Task Mail ===
-    * // 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: \\ +
-  * For task // Specify offer //: +One of the tasks in the subprocess should send the mail to the client. \\ 
-    * // Documentation //: Please add available specification for an offer as attachments. +In the full processthis would require some additional information ​to send the email \\ 
-    * // Assignments //: we have 3 choices ​\\ +like what details would you like to know. \\ 
-      * ''​ assignee ''​ - assign a task to a specific user, +But for now, we will just mock this task.
-      * ''​ 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 casewe 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.+There is no mail server configuredbut one can try to send messages to the local address, like ''​student@AML-Lab-316.geist.agh.edu.pl'' ​(check ​the address at your local machine). After sending the email, we can check the terminal with ''​mail'', ​if we have it on the mailbox.
-In addition, for this task we set // Form properties //: +In the e-mailyou can also send some information stored in some variables instances ​of the process.
-  * // 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.+
pl/dydaktyka/dss/lab1.1507583500.txt.gz · ostatnio zmienione: 2017/10/09 21:11 przez kkluza
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0