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: Determining that a people activity's task has been skipped



TARGET: B4P

DESCRIPTION:

There does not appear to be any reliable way for a process definition to check if a previous activity has been skipped.  Section 4.8 states: "The people activity goes to final state Obsolete if the task is skipped." However, there is no way for a process to include a condition that checks the state of a people activity.

PROPOSAL:

Add a new XPath extension function called getState, with the following entry in the table of extension functions:

getState

Returns the current state of the people activity, which will be one of: "INACTIVE", "RUNNING",
"COMPLETED",
"OBSOLETE",
"TERMINATED"

In

people activity name (xsd:string)

Out

the current state (xsd:string)


The state transition diagram in section 4.8 should also remove the transitions to the "closed" state.  They are currently unlabeled, which appears to mean that the transition to "closed" happens immediately, preventing anyone from ever seeing the states 4 states that precede "closed".



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