handling the outcome of serial/Parallel approval human task

in some cases and to avoid creating many ADF pages for the same functionality (same human Task) you may go to use Complex Human Task also you will include many users or roles as serial or parallel or mix of Both . please see image below :

There is no problem when participant click Approve , where task simply will move to the next participant , on contrast we must stop the whole task and go in alternative path if any participant reject the task , to do that we have to use Early Completion feature and check the three checkboxes explained below .

This Feature allow Task to be ended early and exit when certain condition happened such Reject or Approve and no need to pass through next participants.

Monitoring Composite Applications with Sensors and Oracle BAM (1-3) - Composite Sensors

in this series of articles i will discuss monitoring composite applications using Sensors (composite & BPEL)  , in the last part , i will go in short tour to explain integration with oracle BAM.

Sensors Definition :

A sensor is an Oracle construct that enables users to monitor key execution points or data in their composite application. 

There are two types of sensors:
• Composite application
• BPEL

Sensors are associated with sensor actions that can send data
to different publish types:
• Database
• JMS destination
• Custom (Java)
• BAM  

Composite Sensors :

Composite sensors are defined on service and reference binding components. They provide a method for implementing trackable fields on incoming and outgoing messages.

Composite sensor actions enable you to:
• Specify composite sensor details in the search utility of the Instances page of      a SOA composite application in the Oracle Enterprise Manager Fusion                Middleware Control console. This action enables you to locate a particular          instance.
• Publish JMS data computed from incoming and outgoing messages

Composite ِSensors Actions :
Composite sensors support only two types of sensor actions: 

• Enterprise Manager
•  JMS.

Select Enterprise Manager to make runtime sensor data searchable on the Instances tab of a SOA composite application in the Oracle Enterprise Manager Fusion Middleware Control console. 

Note: When Enterprise Manager is selected, sensor data is sent to the trackable fields tables. When it is not selected, data is not sent. However, in both cases, the Oracle Enterprise Manager Fusion Middleware Control console still displays the fields that enable you to search for composite instances based on that sensor.

The JMS Queue and JMS Topic selections enable the composite sensor data (XML payload) to be used by other consumers, including Oracle Business Activity Monitoring and Oracle Complex Event Processing (CEP). Both selections use the native JMS support provided with Oracle WebLogic Server, and not the Oracle SOA Suite JMS adapter described in the Oracle Fusion Middleware User’s Guide for Technology Adapters. You can view JMS messages in the Oracle WebLogic Server administration console.

SOA Composite Example : 
in this section i will create example to show how Composite Sensors works .

• Create SOA Application from Jdeveloper with name "TestCompositeSensorsApp"
• Create SOA Project And name it "TestCompositeSensorsProj"
• Drop BPEL component on composite 
• Drop Assign Component inside BPEL to simply connect input string to output

• Go to Composite.xml an click composite Sensor Icon 
• Create New Sensor and give name , Expression and Filter 

• click ok and deploy !
• go To EM
• test web service with inputs test,test1,test2,test (4 times)
• Click Flow instances Tab
• in Search option Click Add/remove Filter --> check Flow Instance option
• Add the sensor you want and Search instances