[#BP-11] Initialization of process generic human roles in b4p

OASIS BPEL4People TC

Initialization of process generic human roles in b4p

Created: 18/Apr/08 07:43 AM Updated: 30/Jul/08 11:33 AM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Description

« Hide

SUBMITTED BY: Mark Ford
TARGET: B4P, Section 3.1 Generic Human Roles

DESCRIPTION: The b4p:peopleAssignments element is a required extension
element according to the syntax on line 292-294 in the B4P spec.

This element is defined on line 375:

<b4p:peopleAssignments>
  <htd:genericHumanRole>+
    <htd:from>...</htd:from>
  </htd:genericHumanRole>
<b4p:peopleAssignments>

With a detailed example on line 384

<b4p:peopleAssignments>

  <b4p:processInitiator>?
    <htd:from ...>...</htd:from>
  </b4p:processInitiator>

  <b4p:processStakeholders>?
    <htd:from ...>...</htd:from>
  </b4p:processStakeholders>

  <b4p:businessAdministrators>?
    <htd:from ...>...</htd:from>
  </b4p:businessAdministrators>

</b4p:peopleAssignments>

The initial syntax indicates that at least one role must be present. The
example immediately following it shows them as optional. My understanding is
that you have to provide at least one but it's up to you to pick which one
you want to declare in your process.

Can the initialization of these roles make use of instance data within the
process, either in the form of an expression or as arguments to a logical
people group? It seems like they wouldn't be able to since their
intialization is during the process scope's intialization which occurs prior
to the execution of the create instance activity. If there isn't any access
to instance data, then the definitions are essentially using static data. If
this is the case, then why do we require their declaration? It seems that
the infrastructure could handle the assignment of users to these roles. The
only one that doesn't fit well is the process stakeholders since that
intialization would likely require access to the process instance data.

PROPOSAL:

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Luc Clement [30/Apr/08 11:52 AM]

Approved as Opened 20080430

[ Permlink | « Hide ]

Dave Ings [09/Jun/08 10:11 AM]

Extracted from 6/9 meeting minutes:

Dieter Koenig: Assigning people to process-related generic human roles happens after BPEL process initialization (see [WS-BPEL 2.0]). A BPEL4People processor MUST initialize process-related generic human roles after the end of the initial start activity of the process and before processing other activities. If that initialization fails then the fault b4p:initializationFailure MUST be thrown by a BPEL4People processor.

Dieter Koenig: (this will become the new section 3.1.2 Initialization Behavior

Gershon Janssen: Martin moves a motion: Resolve issue 11 to replacing the last paragraph of 3.1.1 with a new paragraph 3.1.2 as defined above.

Gershon Janssen: Frank seconds the motion. Accepted by unanimous consent.

[ Permlink | « Hide ]

Dave Ings [10/Jun/08 08:33 AM]

Clarifying comment:

... and before processing other activities or links leaving the start activity.

(editors can clean this language up).