[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [bpel4people] BP-116: Missing Pre-State / Post-State Specifications forAdministrative Operations
I uploaded a file attachment for BP-116 (?
http://www.osoa.org/jira/browse/BP-116) which shows the proposed two new
columns for the table that defines administrative operations (they were not
readable in my original mail).
Kind Regards
Dieter König
Senior Technical Staff Member, WebSphere Process Server Architect
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions
Phone: +49-7031-16-3426 IBM Deutschland (Embedded
image moved
to file:
pic20020.gif)
E-Mail: dieterkoenig@de.ibm.com Schönaicher Str. 220
71032 Böblingen
Germany
IBM Deutschland
Research &
Development
GmbH /
Vorsitzender des
Aufsichtsrats:
Martin Jetter
Geschäftsführung:
Erich Baier
Sitz der
Gesellschaft:
Böblingen /
Registergericht:
Amtsgericht
Stuttgart, HRB
243294
----- Forwarded by Dieter Koenig1/Germany/IBM on 04.07.2009 16:22 -----.
From: Dieter Koenig1/Germany/IBM
To: bpel4people@lists.oasis-open.org
Date: 29.06.2009 13:50
Subject: [bpel4people] New Issue: Missing Pre-State / Post-State Specifications for Administrative Operations
Target:
WS-HumanTask CD 04 revision 03, section 7.1.4 Operation Authorizations
Description:
Section 7.1.4 introduces client operations for administrative purposes.
Unlike section 7.1.1, which specifies the general-purpose client
operations, the table in 7.1.4 has no columns defining the task pre-states
in which an operation may be called and the task post-state after the
operation is performed.
Proposal:.
Add the following paragraph (copied from 7.1.1) before the table in 7.1.4:
<newParagraph>
If the task is in a predefined state listed as valid pre-state before the
operation is invoked then, upon successful completion, the task MUST be in
the post state defined for the operation. If the task is in a predefined
state that is not listed as valid pre-state before the operation is invoked
then the operation MUST be rejected and MUST NOT cause a task state
transition.
</newParagraph>
In addition, add two columns "Pre-State" and "Post-State" to the table in
7.1.4, with the following content:
+---------------------+ ... +-------------+--------------+
| Operation Name | ... | Pre-State | Post-State |
+---------------------+ ... +-------------+--------------+
| activate | ... | Created | Ready |
+---------------------+ ... +-------------+--------------+
| nominate | ... | Created | Ready |
| | ... | | Reserved |
+---------------------+ ... +-------------+--------------+
| setGenericHumanRole | ... | Created | (no state |
| | ... | Ready | transition) |
| | ... | Reserved | |
| | ... | InProgress | |
+---------------------+ ... +-------------+--------------+
Kind Regards
Dieter König
Senior Technical Staff Member, WebSphere Process Server Architect
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions
Phone: +49-7031-16-3426 IBM Deutschland (Embedded
image moved
to file:
pic03091.gif)
E-Mail: dieterkoenig@de.ibm.com Schönaicher Str. 220
71032 Böblingen
Germany
IBM Deutschland
Research &
Development
GmbH /
Vorsitzender des
Aufsichtsrats:
Martin Jetter
Geschäftsführung:
Erich Baier
Sitz der
Gesellschaft:
Böblingen /
Registergericht:
Amtsgericht
Stuttgart, HRB
243294
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
