You can also access this tutorial in German and French.

 

In this video we will deploy the workflow that we have edited in the last three videos on the YAWL Engine. We start a case and follow its status from the points of view of the administrator and the various users.

You can find the supplementary in the zip file below.

Hello, welcome back to the YALL tutorials. In the last three videos, we have entered all the information we needed for a workflow specification in YAWL. The control flow perspective, the data perspective, and the resource perspective. So now we are ready to finally deploy our own workflow on the YAWL engine. So we'll do that using the control center and the administrator account on the one hand and then we will go through our case step by step using different user accounts and I will show you how the work is being distributed by the YAWL system. So let's dive into it! Okay, so now you can see on this screen two browser windows on the left hand side we have the administrator so we are already logged in with the admin user. Remember this that this is admin and password is YAWL - Y A W L - all in capital letters. So on the left hand side, this is the administrator on the right hand side, we will log in with our users. So let's first go to the cases tab in the control center. And you can see currently, there are no specifications loaded. What we have to do now is, we have to first choose a file and we will go to our user here and we will find the application for leave. So we have selected the .yawl file and we upload it now. So you can see application for leave version is 0.4. So the YAWL editor is automatically increasing the version numbers as we save the specification and we have the explanation example application for leave. So we will launch our first case here. We have to select the application first. So select the application and launch case. Okay, so now I can see I have launched the case and it has the case ID 4 and I can go to the admin queues and see what happens and I can go to the Worklisted tab here and see that "Submit leave request", which is the first work item in our case, is assigned to two users: Liana Hayes and Lila King and that's what I would expect. So now I can go to the right hand side and I can login with Liana Hayes -  lha - password pass and I can see "Submit leave request" here in my offered queue. I accept and start, go to the started tab and press view edit and then I put in my data: first name, last name and then I put in nine of September until nine of October and I go to Munich and yes the reason is Oktoberfest. So then I complete the work item. Now going back to our administrative view, let's refresh here. We can now see "Approve leave request" which is assigned to Rosa Maine and Ray Rees. These are the two users we have created in our last video with the role approver in the offered stage. So on the right hand side, I log in with the user Ray Reese - let me log out first - so log in with Ray Rees, passport pass and now "Approve leave request" is in the offer queue. I accept and start, go to the started tab and click view edit. Now I can see all of the data that have been entered in the previous tasks in read-only mode - they are grayed out - and I can approve the leave and I can say the rejection reason is none. It's not rejected is accepted and I complete going back to our administrative view, refresh and see "Note approval" and "Note approval" is now assigned to one. That's what we would expect because we said we want to assign or offer it to the completer of the first task in this workflow. So if we go now back to the other browser where we have been logged in with this user that did the first step we can refresh here and we now see in the offered tab that we have "Note approval". We accept and start it, go to the started tab and click view edit and now we have "Note approval" here with the approved leave check mark set. All the data we have entered is valid. We can see them again and we press complete and now we are done. Because this was the last task in our workflow and if we go back to the admin queue and refresh, the lists are empty here and if we go to the cases we can see there are no running cases. So our first case has been completed successfully.

So this concludes our tutorial on how to execute a workflow on the YAWL engine. See you next time!