Afaik there is no out of the box implementation for dynamically calling subprocesses in 7.1.2 but this is an interesting question.
If you have a defined set of parallel executions which don’t change for different instances you can just draw parallel paths in Designer, those are executed in parallel by PRE (Amount of parallelity is defined by the thread count of the process transition trigger, default is 10).
If the number of “threads” is dynamic, I can think of 2 alternatives (there are more for sure)
-
Call the subprocesses by publish subscribe out of the model by publishing starter documents. If you do not need to join back after the steps for the different threads are done, that’s all and this a quite easy approach If you need to come back to a common thread, yo need to join the answers using a subsequent receive step with a correlation service. This receive step must not be allowed to start the process and the original starter needs a fitting correlation service too. You will also need to find a solution to recognize when all answers arrived, but how this can be done depends on your process.
-
You may implement a service which spawns threads in IS and use this as process step. In a service it’s easier to recollect the running threads. In the threads the logic may be performed or again a process be triggered with a request reply pattern.
Hope this help, please share your results if you find a solution.
[/list]
[/list]
#webMethods#BPM#webMethods-BPMS