A process with a multi-instance activity. In the process, an order is created. Each order contains several line items that need to be checked separately. This is achieved by a multi-instance task that is instantiated for each line item. There is also a video that shows the execution and how to define a multi-instance activities and the required data.
The example shows how to use multi-instantiated tasks in Bonita BPM. The goal is to create multiple instance of the same activity, how to manage different environments for each instance, how to assign each instance to a different user, how to get results form each instance and how to put a condition over that multi-instantiated task.
This process provide a sample of multi instantiation feature.
It uses a multiInstantiator called SplitString you can find in the multiInstantiator contributions.
The use case is very simple :
An user enter a list of guest for his/her party then the system multi instantiate a task for each guest to send them a mail (simulated).
Demo using Multipleinstances and mysql connector and using table control.
Manager invite some peoples to evaluate an department,they fill the forms,and return to manger.
This process provides a sample of multi instantiation feature with execution of a sub-process.
(Inspirited by "Multi instantiation sample")
Use Case:
* A list of values is split into a list.
* A subprocess is executed for each element of that list
* Each step writes a message into the console which lets you track the execution.
Tried multi-instantiator with 5.2 works fine.. Please see the usecase and the attached bar.. As usual what i have provided is only a simple example and obviously can be improved further. But i leave that to you ;-)
UseCase
My Usecase is that.. When you start the Main process with a list of usernames (comma seperated) for example (john, jack, james)
This multiInstantiator works with a String input variable. According to the separator you define, it splits it into a serie of tokens. It instantiates the task n times passing to each of those tasks one token.
It is also possible to define a threshold (in pourcentage) to control how many tasks must be realized to continue the process (by default 100% - all of them).
