Please disable Adblockers and enable JavaScript for domain CEWebS.cs.univie.ac.at! We have NO ADS, but they may interfere with some of our course material.

[Info]
Workflow Execution
• Assignment 4a - Modell
• Assignment 4b - Runtime
• Assignment 4c - Worklist
• Assignment 4d - Logging

Workflow Execution (up)

Use the following workflow engine: 
 
Make sure all software you write runs on: 
 
Use one (or many) of the following technologies – your choice:  
 
For UI’s ist HTML/JS is obligatory (subdirectory public_html on almighty.cs.univie.ac.at). 

Assignment 4a - Modell (up)

Port your process to CPEE (including data flow) und use the timeout servive. 
 
Include the data flow from Aristaflow 3a, as shown on tuesday and thursday.  
 
Solution approach 1 (~ 2 minutes): 
 
Solution approach 2 (~ 10 minutes): 
 
Submit the following files: 
 
WARNING: 0 POINTS if Matnr is not included in Attribute info. 

Assignment 4b - Runtime (up)

For every task write a Web-Service. 
 
2nd Edition: Really do what it says above. 
p.s. man kann jederzeit sein Signavio Modell anpassen (Labels duerfen nicht umbenannt werden, aber Tasks entfernt oder Manual/Automatic Label veraendert werden). 
 
Important: 
 
Abzugebende Dateien: 
 
WARNING 1: 0 POINTS if Matnr is not included in Attribute info. 
WARNING 2: 0 POINTS if it is not runnable on one of the servers mentioned above. 

Assignment 4c - Worklist (up)

A Worklist is a program that allows process actors (i.e. humans) to interact with a process (the person that klicks execute in the CPEE Cockpit is not a process actor). 
 
To realize a worklist, every human task (at least 4 tasks with a hand or a human in your Signavio model!) is REQUIRED to have EXACTLY the following additional  
parameters: 
 
Of course there is MOST POSSIBLY additional input parameters. Each task should be realized as asynchronous task: 
 
  1. When the task is called, save all parameters and tell the CPEE that you will answer later. 
  2. Show the Task List for the users (assigned to the role). 
  3. When a user takes the task, show him or her the form (with the additional parameters so that he/she has context information). 
  4. Gather the users input and send it back to the CPEE. 
Write the following files (only these files): 
 
Additional rules: 
 
How to tell CPEE that you want to answer later? 
 
<?
  $headers = apache_request_headers() ;
  # save $headers['CPEE_CALLBACK'], plus all $_REQUEST parameters
  header('CPEE_CALLBACK: true');
  exit;                                                                                                                            
?>
 
How to send data back to CPEE (by PUT'ing it to the url in $headers['CPEE_CALLBACK'])? 
 
<?
  $opts = array('http' =>
    array(
      'method'  => 'PUT',
      'header'  => 'Content-type: application/json',
      'content' => JSON_DATA
    )
  );
  $context = stream_context_create($opts);
  $result = file_get_contents('http://...', false, $context);
  exit;
?>
 
Submit the following 4 files: 
 
WARNING 1: 0 POINTS if Matnr is not included in Attribute info. 
WARNING 2: 0 POINTS if it is not runable on one of the servers mentioned above. 
WARNING 3: Assume that you need several days, including interaction with others (e.g. Forum) to do this. 

Assignment 4d - Logging (up)

Write a logging facility, which saves all information as «XES 2.x.» file. 
Add the follwing aspect to your testset file (just copy it in below handlerwrapper): 
 
<handlers>
  <handler url="http://wwwlab.cs.univie.ac.at/~XXXXXX/logging/logging.php">
    <events topic='activity'>calling,failed,manipulating,done</events>
  </handler>
</handlers>
 
http:// has to point to your logging service in your account (use EXACTLY the format given above, just change XXXXXX to your username). 
 
Pro TIP: Save all incoming information as you did for the worklist (headers and $_REQUEST) in a random file. Then you can check what data you get. 
 
Tailor the list of <events> so that it suits your needs. Possible events can be found under «http://cpee.org:9298/1/notifications/topics» 
 
Use your testset from Assignment 4c. The result should be a valid XES File. 
 
Add event dispersing (hardcoded location) to the worklist so that it contributes to the events in the XES File. The worklist should send the following events: 
 
The events from the worklist should also show up in the XES File. 
 
Additional rules: 
 
Submit the following 3 files: 
Last Change: 17.01.2017, 12:10 | 1221 Words