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:
|
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 |
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, |
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