WSO2 Business Process Server v3.1.0 Documentation

##### Overview

- Home
- Release Note
- WS-BPEL Compliance
- License

##### Downloads

- Releases

##### Installation Guide

- Installing WSO2 BPS

##### Quick Start Guide

- Modeling the process
- Deploying the process
- Testing the process

##### User Guide

- Deploying BPEL Processes
- Deploying Human Tasks
- Managing BPEL processes
- Managing BPEL process instances
- QoS for BPEL processes
- Securing BPEL processes
- Invoking secured partner services
- Versioning
- Management API

##### Human Task Guide

- Human Tasks Quick Start Guide
- Deploying HumanTasks
- Managing Tasks
- Developing a Human Task Artifact
- Human Task Management and Configuration
- Human Task Concepts

##### Administrator Guide

- External data sources Configuration
- Registry Configuration
- Events
- Unified Endpoints
- BPEL Extensions
- Transaction Factory Configuration
- Message Exchange Interceptors
- OpenJPA specific properties
- JMS Transport Configuration
- Process Instance Cleanup Tasks
- Process Hydration and Dehydration
- Enabling Peer-to-Peer(P2P) Communication
- Setting up a BPS Cluster

##### Best Practices

- Process Deployment Best Practices

##### Concepts

- Process Versioning
- Process instance events
- Partner links

##### WS-BPEL Extensions

- Activity Failure and Recovery
- Extension Activities and Extensible Assign Operations
- XPath Extensions
- Iterable ForEach
- Flexible Assigns
- BPEL4People Extension

##### Samples

- HelloWorld
- If-Else
- ForEach
- While
- Repeat Until
- Flow and Links
- Pick
- Synchronous and Asynchronous Service Invocations
- Fault Handling
- Split
- XslTransform
- Compensation Handler
- Event Handler

##### Resources

- FAQ
- External Articles
- Library
- Source Code

##### Community

- Forum
- Mailing Lists

##### Project Information

- Issue Tracking

# BPEL4People Extension Activity

The BPEL4People extension allows a BPEL process to invoke a remote human task service. The syntax of the BPEL4People extension activity is as follows.

                    <extensionActivity>
                        <b4p:peopleActivity name="TestTASKPeopleActivity"
                                            inputVariable="b4pInput"
                                            outputVariable="b4pOutput">
                            <b4p:remoteTask partnerLink="b4pPartnerLink"
                                            operation="approve"
                                            responseOperation="approvalResponse">
                            </b4p:remoteTask>
                        </b4p:peopleActivity>
                    </extensionActivity>

A list of configuration elements in the extension activity

- name
  The name of the extension activity. You can put any identification name here.
- inputVariable
  The input variable for the human task service. The human task service would be invoked with this input variable.
- outputVariable
  The response element relieved when the human task is completed.
- partnerLink
  The partner link for the remote human task.
- operation
  The operation to be invoked in the remote human task.
- responseOperation
  The callback operation of the process which would be called by the human task once the task is completed.

For a remote human task invoke and provide elements have to be provided in the deploy.xml file.

    		<provide partnerLink="b4pPartnerLink" correlationFilter="b4p:b4pFilter">
    			<service name="apprv:ClaimServiceCB" port="ClaimPortCB"/>
    		</provide>
    		<invoke partnerLink="b4pPartnerLink">
    			<service name="apprv:ClaimService" port="ClaimPort"/>
    		</invoke>

Note: The correlationFilter property has to be set to b4p:b4pFilter for the responses to be correlated to the process instance.