Overriding parameters that are specified in the BPMN interchange format

[GoogleCodeExporter]

BPMN interchange format already has the capability to specify parameters for 
items such as loopCardinality, in the case of MultiInstance Activity or 
loopCondition for the sequence Looping Activity.

Do we want to allow these types of parameters to be overridden using PAF data? 
If so we will need to define additional Control parameters.

The advantage of overriding it in the PAF is that we have control over the data 
format where as if the BPMN interchange format is used, we have less control.

Original issue reported on code.google.com by jhor...@lanner.co.uk on 13 Mar 2012 at 3:54

[GoogleCodeExporter]

This context for this issue was to be able to change the looping parameters for 
the StandardLoopCharacteristics and MultiInstanceLoopCharacteristics of an 
Activity.

Proposal - StandardLoopCharacteristics BPMN parameters:

- loopMaximum -> the existing maxTriggerCount parameter could be used in this 
case.
- loopCondition -> a new "condition" parameter could be introduced to the 
ControlParameters perspective.

Proposal - MultiInstanceLoopCharacteristics BPMN parameters:

- loopCardinality -> a new "condition" parameter could be introduced to the 
ControlParameters perspective.

Original comment by jhor...@lanner.co.uk on 23 Jul 2012 at 1:46

[GoogleCodeExporter]

Using the maxTriggerCount in the way specified above would cause issues for the 
use case when the Activity does not have in-coming sequence flow. 

In this case there would be a conflict:
- Should the maxTriggerCount limit the number of tokens to be created
- Should it be used to control the looping (assuming the activity has 
StandardLoopCharacteristics or MultiInstanceLoopCharacteristics)

Original comment by jhor...@lanner.co.uk on 2 Aug 2012 at 9:11

[GoogleCodeExporter]

The overloading of BPMN parameters is differend to version 2.0

Original comment by sringue...@trisotech.com on 20 Sep 2012 at 7:41

• Changed state: WontFix