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: NEW ISSUE: State transitions: Loop on "inProgress" status?


Title: NEW ISSUE: State transitions: Loop on "inProgress" status?

Hello all,

as decided in today's working session on sub-tasks and routing patterns, we want to create official TC issues for the remaining open issues we've collected.

Fifth -


Issue: State transitions: Loop on "inProgress" status?

Proposed by: sub-task / routing pattern working session team

Target: WS-HT

Issue Description:
WS-HT specification, chapter 4.7 Human Task Behavior and State Transitions

To enable sequential processing of a single task by multiple processors, the status & action model could be enriched by a loop on the "inProgress" status.

Proposal:
Do not add such a loop, as a next processor of a task, which is sequentially processed by multiple people, would usually expect that the task reaches his inbox in status "Reserved". In this case the same state transition applies as for delegation of an "inProgress" task.


Best regards, Hannah




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