To configure the human task case branches, an <if>
activity needs to be added to the BPEL process. Fortunately, the JDeveloper has done this for us. If we look at our BPEL code, we will see that the <if>
activity with the appropriate branches has been added:
All we need to do is specify the corresponding activities for each branch. We have to specify the activities for the APPROVE outcome, the REJECT outcome, and for all other situations where the outcome is not selected (for example, if a human task has expired).
In our process, we will do the following:
for else
branch, we will copy the corresponding text (Rejected or Error) to SelectedBookstoreLocation
in the output
variable.We have added the activities to handle the human task outcomes. In our case, we have added the assign activities to update the process output accordingly. After the added assigns, the process should look like this:
The task form is used to display the content of the task to the user. In general, any custom user interface can be used. Oracle SOA Suite also provides a generic worklist application, the Oracle BPM Worklist application. In Oracle SOA Suite 12c, we can create a task form using the Oracle Application Development Framework (Oracle ADF). When creating the task form, we have two options:
.task
file for the human task.As ADF is out of the scope of this book, we will just show how to autogenerate the task form using a wizard.