There are a few final touches we want to add into to the process to complete it:
System Participants
Lets Let's add a new condition to the our sample Leave Application process flow. The new scenarios are that when When either the supervisor or the HOD rejects a leave application, a rejection notice gets is sent to the requestor. If the HOD approves the application, an approval notice gets is sent to the requestor. After either mail email is sent, the process ends. To do this
To put our new condition into effect, we'll need to add a System participant. System participants are used when an automated task is required that doesn't which does not involve human interaction is required. Mails Emails being sent out automatically will qualify as a task for a system participant. The biggest difference between system and regular participants are that in system participant swimlanes, tools are usually used as opposed to activitiesis an example.
An important point to note, however, is that System participants use tools for their tasks instead of activities which regular participants use.
To add a system System participant in the process, create a new participant in your process. Double-click on the participant, rename the name to System and most importantly, the Participant label and in the resulting dialog box, type "System" in the Name field and then set the participant type to "System".
Tools
Tools are similar to activities but are usually mapped to plugins rather than forms. They represent the sort of activities that will be carried out by as automated tasks that require no without human interaction.
In our particular casesample process, we want will need to add 2 two new tools to the system System swimlane and then map the them correctly to our previous activities.
A few things Points to note:
1. Note the use of the otherwise transition. We could just have easily create the new transitions On the Otherwise transition: creating a new transition to carry the condition supervisorApproval=='no' is an option, etc but one that won't does not fall in line with best practices. This wayBy using the Otherwise transition instead, we ensure can be sure that all eventualities are catered for or at the very least covered and that the process execution will be not get stuck midway.
2. Note also in the final decision route that the expression
...
will require a new workflow variable to be created. Make sure you create the necessary workflow variable in your process properties window.
Process
...
Guide
There is a Process Guide at the bottom left-hand corner of your workflow designer that will analyze Workflow Designer that analyzes your process on the fly for critical or warning items. Pay attention when there are red crosses. That usually means that there are fatal They point out errors in your workflow that will may likely cause your deployment to fail.
Start and
...
End Bubbles
The last things you usually add to your process are start and end bubbles. We don't ever want our process to start from nowhere or to end abruptly so the initiating Start and End bubbles are usually added last to processes. Initiating and terminating bubbles are important to mark where a process might begin or where it might end. We wouldn't want our process to start from nowhere or to end abruptly.
To include a start and end bubblesbubble, you can manually place them on either drag-and-drop them onto your process and join them to the transitions by handproceeding and from the preceding activities by manually adding transitions, or you can simply click on the "Insert missing start and end bubbles" icon.
Process
...
Update/
...
Deployment
One thing to note is that your workflow designer can run as a client. This means you can save drafts of your processes onto to your localhost and amend them at any time until you believe are satisfied that they are ready for production. Once such a time occurs however, access
When a process is ready for deployment, select Deploy from the File menu option and then select Deploy (, or update if the process has previously been deployed).
