Loading...

XML

Word

Printable

AT:

Exact semantics:

with this feature it will be possible to make a sequential multi instance activity parallel for the lifetime of the newly created instances
when an instance of the miBody already exists:
instantiating an inner activity as a child of an existing mi-body instance will: create an additional concurrent instance in case of parallel MI and update the mi variables numInstances, numActiveInstance; increment the loop counter variable and set it on the new execution; throw an exception in case of sequential MI
instantiating an inner activity will as a child of an instance higher in the scope hierarchy: create all scopes (including the miBody) as usual, create the mi-body execution structure as if it was entered via sequence flow (i.e. with parallel MI, there is always a concurrent execution even though there is only one inner instance), create the mi variables (nrOfInstances set to 1), create the loop counter variable for the first instance

is related to

CAM-3604 Foreign Key Constraint errors due to incorrect flush ordering

CAM-3819 I can start the "Multi Instance Body" of an activity in Cockpit using PI-Modification

CAM-3821 I can select a MI-Body activity instance as ancestor in cockpit process instance modification

CAM-3455 Refactor Multi Instance and related PVM constructs

I can modify a process instance's execution state with multi instance & loops