cancel
Showing results for 
Search instead for 
Did you mean: 

Proper way to model multiple instance call activity

wolpert
Champ in-the-making
Champ in-the-making
Not sure this is the correct place to ask this…

I'm using Explorer for model development, and I'm trying to model a situation where a call activiti is executed multiple times (multi-instance). The goal is to execute multiple call activities (not embedded sub-processes, but processes that exist on their own) and have the calling (parent) process wait for all these executed processes to complete. So, my questions are perhaps two-fold:

1) Can this be modeled correctly via Explorer (or graphically at all)?
2) Is there an example of this you can point me to?

Thanks
5 REPLIES 5

jbarrez
Star Contributor
Star Contributor
1) how do you mean using Explorer? Explorer is the task mgmt app.
2) There is definitely unit test of calling a call activity in a multi instance in the source code. I do not remember if the default behavior is to wait or to continue when calling the process.

ronald_van_kuij
Champ on-the-rise
Champ on-the-rise
you could create an embedded subprocess with al callactiviti and e.g. a receive task and make that multi instance

wolpert
Champ in-the-making
Champ in-the-making
Yikes, I didn't mean explorer, I meant the eclipse designer… so yeah, this is the wrong forum. 🙂

I'll keep trying, if I don't get anywhere when 5.7 comes out, I'll post in the correct forum. Thanks

wolpert
Champ in-the-making
Champ in-the-making
So, just to close this thread…. and answer my own question, In activiti designer you can create the call activity, then go to the 'multi-instance' tab for that activity and start setting variables. It won't change how the model looks, but the xml is correct.

I'm not sure how a 'multi-instance call-activity' "should" look in a BPMN diagram, but at least I can make one.

ronald_van_kuij
Champ on-the-rise
Champ on-the-rise
I'm not sure how a 'multi-instance call-activity' "should" look in a BPMN diagram, but at least I can make one.

Like a normal call activity but with two vertical dashes at te bottom. As is described in te specs