Specify the signature policy for task participants to use: Select Application Defined MBeans oracle.as.soainfra.config Server: server_

Designing Human Tasks 27-77 To distinguish between events for TaskA and TaskB and ensure that an event is processed only by the intended Oracle Mediator, you can add a static routing filter: xpath20:comparemed:getComponentName, TaskA This only invokes this routing when the sending component is TaskA. 13. If the EDL file was not selected from the file-based MDS connection, accept to import the dependent XSD files when prompted, and click OK. If the EDL file was selected from the file-based MDS connection, you are not prompted. The Oracle Mediator service component is now populated with the business event to which to subscribe. You can also subscribe to other business events defined in the same EDL file now or at a later time. See the following documentation for additional details about business events and callbacks: ■ Chapter 38, Using Business Events and the Event Delivery Network for specific details about business events ■ Sample workflow-116-WorkflowEventCallback, which is available from the Oracle Technology Network: https:soasamples.samplecode.oracle.com

27.3.15 How to Specify Task and Routing Customizations in BPEL Callbacks

In general, the BPEL process calls into the workflow component to assign tasks to users. When the workflow is complete, the human workflow service calls back into the BPEL process. However, if you want fine-grained callbacks for example, onTaskUpdate or onTaskEscalated to be sent to the BPEL process, you can use the Allow task and routing customization in BPEL callbacks option. Make sure to manually refresh the BPEL diagram for this callback setting. To specify task and routing customizations in BPEL callbacks: 1. In the Events section, select the Allow task and routing customization in BPEL callbacks checkbox. 2. Return to Oracle BPEL Designer. 3. Open the task activity dialog.

4. Click OK.

This creates the while, pick, and onMessage branch of a pick activity for BPEL callback customizations inside the task scope activity. For more information about specifying task and routing customizations, see Section 27.4.5.1, Invoking BPEL Callbacks.

27.3.16 Disabling BPEL Callbacks

A user talk activity in Oracle BPEL Designer has an invoke activity followed by a receive or pick activity. Deselecting the Disable BPEL callbacks checkbox enables you to invoke the task service without waiting for a reply. To disable BPEL callbacks: 1. In the Events section, deselect the Disable BPEL callbacks checkbox. 27-78 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite

2. Click OK.

27.3.17 How to Exit the Human Task Editor and Save Your Changes

You can save your human task changes at any time. The task can be re-edited at a later time by double-clicking the metadata task configuration .task file in the Application Navigator. To exit the Human Task Editor and save your changes: 1. From the File main menu, select Save or click the X sign shown in Figure 27–70 to close the .task metadata task configuration file. Figure 27–70 File Closure

2. If you click the X sign, select Yes when prompted to save your changes.

27.4 Associating the Human Task Service Component with a BPEL Process

To associate the human task service component created in the SOA Composite Editor with a BPEL process, follow these instructions. When association is complete, a task service partner link is created in Oracle BPEL Designer. The task service exposes the operations required to act on a task. For more information about creating a human task, see Section 27.3, Creating the Human Task Definition with the Human Task Editor.

27.4.1 How to Associate a Human Task with a BPEL Process

There are two ways to associate a human task service component with a BPEL process: ■ If you have created a human task service component in the SOA composite application, drag a human task activity into the BPEL process in Oracle BPEL Designer. Then, select the existing human task service component from the Task Definition list of the Create Human Task dialog. You can then specify the task title, initiator, parameter values, and other values. ■ If you have not created a human task service component, drag the human task activity into the BPEL process in Oracle BPEL Designer Then, click the Add icon to the right of the Task Definition list in the Create Human Task dialog. This action enables you to specify the name of the new human task service component, the parameters, and the outcomes. The Human Task Editor then opens for you to design the remaining task metadata. After design completion, close the Human Task Editor. To associate a human task with a BPEL process: 1. Go to the SOA Composite Editor. 2. Double-click the BPEL process service component with which to associate the .task file of the human task service component.

3. In the Component Palette, expand SOA Components.

4. Drag a new Human Task activity into the BPEL process.