Using the Oracle BPM Worklist application

To test the Human Task, we first need to initiate a new process instance. If we look at the trace of the instance, we can see that the instance is still running and is waiting for the FlightTicketApproval human task to complete.

Logging into the BPM Worklist application

To complete the human task, we have to log into the Oracle BPM Worklist application using the following URL: http://host_name:port/integration/worklistapp/, where host_name is the name of the host on which the Worklist application is installed and port is the port number of the SOA-managed server (the default is 8001). Oracle BPM Worklist is a very powerful application, allowing users not only to act on tasks, but also provides the following capabilities and more:

• Customizing the visual appearance and behavior

• Reassign tasks to other users

• Escalate, renew, withdraw, and suspend tasks

• Setting the vacation period to automatically reassign tasks during absence

• Creating reports on task productivity, time distribution, and so on

• Sending of notifications and alerts

However, we will not discuss advanced features in this section. Now, we log in to the BPM Worklist application as the user weblogic, as the task is assigned to this user. The BPM Worklist application opens as shown in next screenshot.

By default, the Inbox worklist view is selected and the user can see all tasks assigned to him in the My Tasks list. In our case, there is only one active task: Flight ticket approval. Remember that this is the name of the Human Task that we set during the creation of the Human Task definition.

If we want to see the task details, we have to select the task. The ADF task form displaying task details opens at the bottom of the screen.

In the upper-left corner there is a task title. We can also see two buttons (Approve and Reject), that present possible task outcomes. In order to complete the task, we have to click on one of those two buttons. In the Contents section we can see the payload of the task, displaying information about the selected flight ticket. At the bottom of the task form we can also see the task history and add comments and attachments.

Completing the task

Now we will complete the task by clicking the Approve button (we will approve the flight ticket). The task is completed and is removed from the My Tasks list.

If we look at the flow trace of the instance, we can see that the instance has successfully completed and that the reservation of the flight ticket has been made.

Testing Human Task expiration

Next, we initiate another instance, but this time we do not complete the task. We instead let it expire (remember that we set the expiration time to 5 minutes). Again the Flight ticket approval task appears in the My Tasks list. However, after 5 minutes, the task expires and disappears from the list. If we look at the instance audit trail, we can see that the instance has completed by executing the otherwise case branch and that no ticket reservation has been made.