3.27 Human Task Editor - Events Page

Use to specify callback classes and enable task and routing customizations in BPEL callbacks. How?

Two types of callbacks are supported:

  • Java callbacks: The callback class must implement the interface oracle.bpel.services.workflow.task.IRoutingSlipCallback. Make the callback class available in the class path of the server.

  • Business event callbacks: You can have business events raised when the state of a human task changes. You do not need to develop and register a Java class. The caller implements the callback using an Oracle Mediator or BPEL process service component to subscribe to the applicable business event in order to be informed of the current state of an approval transaction.

Element Description

State Change Callbacks

Displays the callback states in the task. You can perform the following tasks in this table:

  • Use OnAssigned if the callback class must be called on any assignment change, including standard routing, reassignment, delegation, escalation, and so on. If a callback is required when a task has an outcome update (that is, one of the approvers in a chain approves or rejects the task), this option must be selected.

  • Use OnUpdated if the callback class must be called on any update (including payload, comments, attachment, priority, and so on).

  • Use OnCompleted if the callback class must finally be called when the task is completed and control is about to be passed to the initiator (such as the BPEL process initiating the task).

  • Use OnStageCompleted if the callback class must be called to enable business event callbacks in a human workflow task. When the event is raised, it contains the name of the completed stage, the outcome for the completed stage, and a snapshot of the task when the callback is invoked.

  • Use OnSubtaskUpdated if the callback class must be called on any update (including payload, comments, attachment, priority, and so on) on a subtask (one of the tasks in a group vote and parallel scenario).

Java Class

Click the empty field to enter a value for the selected state. This value is the complete class name of the Java class that implements oracle.bpel.services.workflow.task.IRoutingSlipCallback.

Trigger Workflow Event

Select the checkbox to use business event callbacks. This action disables the Java Class column. Each callback, such as OnAssigned, corresponds to a business event point. When a business event is fired, the event details contain the task object and a set of properties that are populated based on the context of the event being fired.

Allow task and routing customization in BPEL callbacks

Select to send fine-grained callbacks (for example, onTaskUpdate or onTaskEscalated) to the BPEL process.

Disable BPEL callbacks

Select if you want to invoke the task service without waiting for a reply.

Related Topics

Creating Human Tasks in Developing SOA Applications with Oracle SOA Suite

"Using Business Events and the Event Delivery Network" in Developing SOA Applications with Oracle SOA Suite