Which Start Node(s) of Process used for Call Activity?

Camunda 7 Topics Discussion & Questions
1

I have couple of question regarding the callable process[Called from call activity].

  1. Can we defined Multiple Start Node for the Callable Process?
  2. Which Node will be used to start the process from the Call Activity?
  3. Do we have any specific marker for Callable Process?
  4. Will Separate instance be created for callable process?
  5. How can we cancel all CallableProcess on Parent Process abort?
2

Hi Ganesh

  1. Im not sure, but given this is a subprocess, my personal best practice would be not to define multiple start events. Your calling process can pass in context via process variables and your subprocess can take different routes based on context.

  2. Not sure what you’re asking here, perhasp see 1 above…

  3. Not that Im aware of, I usually use a naming convention so its clear its intent is as a subprocess. Also set the isStartable flag to false so it doesnt appear in Tasklist start menu.

  4. Yes a subprocess instance will be created, linked to the master process instance. You can navigate between them in cockpit.

  5. I believe this is built in. If you cancel the master, then child instances will be cancelled. (Note this may be based on operator choice, eg either via API or cockpit, to propagate cancellation)

regards

Rob

3

Thanks for your reply.
Please share the code snippet for isStartable flag.

We Should use only one Start node for the callable subprocess.
But what will be the behaviour if we use Multi Start Node[None + Msg].

4

Hi,

The startable flag is a property on the properties panel in Modeler. It determines if the process appears in tasklist’s start menu or not.

I suspect if you have two start events in your model, call will use the none start event semantics. You could easily do a sample process to confirm…

regards

Rob