Before one can run the process, we will need to Publish the App first. By publishing the App, we are effectively making the Processes and Userviews in the App accessible to all users.
Click on "Not Published" to open the Manage App page, then click on Version control. Select the current version and click on Publish.
Figure 1: Application Version Control
- Go to "Setup User".
- Edit users "cat" and "clark" to assign a password to each of them.
- Log out as "admin" and log in as "cat".
Based on the Sample Organization Chart described earlier, we can try to run the process by logging in as Cat and then as Clark for the Approval activity.
Select Published Processes under Run Apps.
Figure 2: Run Apps
Launch the Leave Application Process.
Figure 3: Published Processes
When asked for confirmation, confirm that you would like to launch the process. You will then be brought to the first activity's form, "Submit Leave Application", like the one shown below.
Complete the form and click on the Complete button to submit it.
Figure 4: Running the Leave Application Process
The performer's HOD, clark, will be next in line to attend to the process.
Figure 5: Viewing the Process Chart
You may login as clark and check his Inbox for new Tasks.
Figure 6: Task Inbox
Open the task. We are now looking at the second activity named "Approve Leave". As there's no form mapped to this activity yet, the system will show all the workflow variables defined in this process for development/debugging purposes.
Figure 7: Viewing an Activity Without Form Attached
To verify whether the routing works or not, in the "Approve Leave" activity, type "Approved" in the "Status" field.
Figure 8: Verifying Process Flow by Setting Workflow Variable Directly in Activity without Form Linked
Complete the activity and log in as cat to check on the next task. If the process is configured properly, you should be able to see "Leave Approved" in the new task's activity name.