OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

bpel4people message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [bpel4people] NEW ISSUE: B4P spec doesn't support skipping participantsin routing


TARGET: WS-HT, General

DESCRIPTION:  WS-HT should support a skip condition that allows any of 
the patterns to be skipped in the potential owner list. Depending on 
some condition, a potential owner could be skipped to work on a task 
although the user is part of the routing pattern definition.

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

PROPOSAL: Each task routing pattern (single, sequential or parallel) 
might have an optional skip condition. If this condition evaluates to 
true, the potential owner will be skipped.

Syntax

The syntax for skip condition is shown in the tSequential and tParallel 
schema definitions of the task routing pattern proposal.

Example

In the example below, the sequential pattern will be skipped if the 
claim account is less than 50000.

  <htd:potentialOwners>
    <htd:sequential name="Claim Processing Agents" 
skipCondition="htd:getInput("ClaimApprovalRequest")/amount < 50000">
      <htd:list>               
        
<htd:from>htd:getInput("ClaimApprovalRequest")/claimProcessingAgents</htd:from>
      </htd:list>
    </htd:sequential>
    <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>
</htd:potentialOwners>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]