[bpel4people] NEW ISSUE: B4P spec doesn't support single approvalrouting pattern

[Ravi Rangaswamy <ravi.rangaswamy@oracle.com>]

TARGET: WS-HT, General

DESCRIPTION: WS-HT should support a single routing pattern aligned with 
other routing patterns. In the current WS-HT spec, people assignments 
are singular in notion, but it doesn’t fit with any overall support for 
patterns. The potential owners in the single pattern can either be done 
through logical people groups, literals or an expression.

RELATED ISSUES:
· Support for routing patterns and policies
· Support for sequential routing pattern
· Support for parallel routing pattern

PROPOSAL: Provide a mechanism to assign the task singularly to 
users/groups by introducing a single routing pattern. If there are 
multiple potential owners than one can claim the task and become the 
actual owner. After the actual user completes the task, the single 
pattern completes.

Syntax

<xsd:complexType name="tSingle">
<xsd:complexContent>
<xsd:extension base="tExtensibleElements">
<xsd:sequence>
<xsd:element name="from" type="tFrom"
minOccurs="0"
maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="name" type="xsd:string"
use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>


Examples

In the example below, assuming that the task input ClaimApprovalRequest 
has 3 claimProcessingAgents children – jlondon, jstein, wfaulk, the task 
will be assigned to jlondon, jstein and wfaulk. One of them acquires the 
task and then the task completes.

<htd:single name="Claim Processing Agents">
<htd:from>
htd:getInput("ClaimApprovalRequest")/claimProcessingAgents
</htd:from>
</htd:single>

In the example below, the task will be assigned to user achrist.

<htd:single name="Claim Processing Review">
<htd:from>
<htd:literal>
<htd:organizationalEntity>
<htd:users>
<htd:user>achrist</htd:user>
</htd:users>
</htd:organizationalEntity>
</htd:literal>
</htd:from>
</htd:single>