In this chapter, we have learned about human tasks and human interactions in BPEL processes. Support for human tasks is important, as it enables BPEL processes to include not only system-to-system interactions, but also human interactions.

To include a human task into the BPEL process, we first need to create a human task definition, where we have to specify various aspects of the human task, such as title and outcome, and human task payload that defines the data that is sent to human task and is received as an outcome. We need to assign the human task to a specific user or a group of users. We might also want to set the deadlines that will define when a human task must be completed. Finally, we can configure the notifications that will define who to notify if the human task is not completed in the specified time or if an error occurs.

Next, we have to add the human task invocation to the BPEL process with a specific human task activity. We also need to handle the outcomes and provide the corresponding activities to handle the various outcomes.

To be able to show the human task to the user, the task form is required. Oracle SOA Suite provides the ability to autogenerate task forms, which simplifies the development considerably.

After deploying the BPEL process and the task forms to the server, we have to use the worklist application to show and complete the human task.

Now that you have learned how to handle human tasks, we move ahead to learning events and event handlers in BPEL. We will see how BPEL processes can react to events, such as messages and timers. Stay tuned!