NEW ISSUE: Override capabilities for a B4P peopleActivity calling a task defined with a routing pattern or composite content

["Petereit, Hannah" <hannah.petereit@sap.com>]

Title: NEW ISSUE: Override capabilities for a B4P peopleActivity calling a task defined with a routing pattern or composite content

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.

Second -

Issue: Override capabilities for a B4P peopleActivity calling a task defined with a routing pattern or composite content

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

Target: B4P & WS-HT

Issue Description:
WS-HT specification, chapter 4.5 Elements for People Assignment

Proposed people assignment syntax (see BP-28)

<htd:potentialOwner>
  fromPattern+ 
</htd:potentialOwner>

The potentialOwners element must be overwritable on people activity level. Putting fromPattern expressions (-> indicating a routing pattern task) inside the potentialOwner element will make the fact, whether a task is a routing pattern task or not, overwritable as well.

The following scenarios should be supported:
a) Human task definition defines a routing pattern task, but potential owner assignment should be context-based
b) Human task definition defines a simple task, may be "transformed" into a routing pattern task via overwrite mechanisms; -> then also output aggregation needs to be defined via overwrite mechanisms

Best regards, Hannah