BPMN Task Marker - Multi Instance Configuration
The Multi-Instance Task Marker can be aither Sequential or Parallel, both options have the following xAPPnow Low Code Configuration possibilities:
-
Loop Cardinality: An integer attribute which specifies the amount of instances, e.g. if the attribute resolves to 3 on runtime, three instances are created.
-
Loop Collection: A list of objects, where element is a single object of the same type. An instance will be created for all elements in the list, where the BO mapped to element will contain the object for which the instance is created. This is mutually exclusive to Loop Cardinality
-
Loop Element: if Loop Collection is used, the current element of the list for this instance is saved here.
-
Loop Completion Condition: an expression, which should resolve to true. If it is evaluated to true, each remaining instances are destroyed
Multi-Instance sequential
Multi-Instance Sequential: the next instance is created after the previous ends
Multi-Instance parallel
Multi-Instance Parallel: All instances are created directly and can be executed in parallel.
As it is possible to select either Sequential or Parallel. If a Multi Instance is executed, the following systemData.process. variables are available in the parent scope of the instances, e.g. the process or subprocess, in a script:
-
nrOfInstances: The total number of created instances of the multi instance
-
nrOfActiveInstances: The current number of active instances. For sequential, this will always be 1
-
nrOfCompletedInstances: The number of already completed instances
-
loopCounter: The index of the current for each loop for the specific instance
