[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [bpel4people] Issue 90 proposal
I have attached a revised proposal for issue BP-90 - http://www.osoa.org/jira/browse/BP-90 Thanks, Ravi Ravi Rangaswamy wrote: > Below is the proposal for issue BP-90 - > http://www.osoa.org/jira/browse/BP-90 > > 1) Drop Section 3.3. Routing Patterns > > 2) Change section 3.4.6 Routing Patterns as below (addition is a > second example of parallel pattern) > > A Routing Pattern is a special form of potential owner assignment. In > a routing pattern, a Task is assigned to people in a well-defined > order. The standard patterns allow the assignment of a Task in a > sequence or in parallel. Those patterns MAY be used in any combination > to create complex task routing to people. > > Example of specifying sequential pattern: > > <htd:potentialOwners> > <htd:sequence type="all"> > <htd:from logicalPeopleGroup="regionalClerks"> > <htd:argument name="region"> > htd:getInput("part1")/region > </htd:argument> > </htd:from> > <htd:from> > <htd:literal> > <htt:organizationalEntity> > <htt:users> > <htt:user>Dieter</htt:user> > </htt:users> > </htt:organizationalEntity> > </htd:literal> > </htd:from> > </htd:sequence> > </htd:potentialOwners> > > Example of specifying parallel pattern: > > <htd:potentialOwners> > <htd:parallel type="all"> > <htd:from> > htd:getInput("ClaimApprovalRequest")/claimAgent > </htd:from> > </htd:parallel> > </htd:potentialOwners> > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]