To create reusable process

[aravindhrs]

Hi @Minisha_M ,

You can configure the multi-instance characteristics to the Call Activity. A multi-instance activity is a way of defining repetition for a certain step in a business process. In programming concepts, a multi-instance matches the for each construct: it allows execution of a certain step or even a complete subprocess for each item in a given collection, sequentially or in parallel.

---

Three vertical lines indicate that the instances will be executed in parallel , while three horizontal lines indicate sequential execution.

• nrOfInstances : the total number of instances
• nrOfActiveInstances : the number of currently active, i.e., not yet finished, instances. For a sequential multi-instance, this will always be 1
• nrOfCompletedInstances : the number of already completed instances

---

You can configure your bpmn model like below (multi-instance sequential execution):

---

Here the collection variable processList contains array of ProcessDefinitionKeys . Element variable or iteration variable called someSubProcess which holds the ProcessDefinitionKey of the subprocess needs to be invoked.

<bpmn:callActivity id="Activity_0vpe19a" name="OCR" camunda:asyncBefore="true" calledElement="${someSubProcess}">
      <bpmn:incoming>Flow_0ymomiv</bpmn:incoming>
      <bpmn:outgoing>Flow_0uhiduz</bpmn:outgoing>
      <bpmn:multiInstanceLoopCharacteristics isSequential="true" camunda:asyncBefore="true" camunda:collection="${processList}" camunda:elementVariable="someSubProcess" />
</bpmn:callActivity>

Refer this post:

Start the subprocess parallel with values from paraent workflow

@vemulabujji From your parent process, collect the results as list as you mentioned result list =[“PI”,“DV”,“SI”,“PA”] . After the service task create a multi-instance call activity to start the subprocesses in parallel as per the below model. lets say your result list variable is subProcessList=[“PI”,“DV”,“SI”,“PA”] and assign a element variable as subProcesskey to loop through the list elements and it will be assigned to the calledElement attribute of call activity. (refer the diagram) [ima…

Completion condition in multi-instance activity:

Start the subprocess parallel with values from paraent workflow

Completion condition is optional, it means if completion condition is not given, then all the multi instances are expected to complete in-order to execute the next activity in the process, so still that execution token will waits in the multi-instance activity until all the instances completes. When the completion condition satisfies, and if few multi instances are still active, then those instances are deleted and the process continues to execute further activities in the process. for more d…