Thanks for answer, Mauricio.
I will explain more what is the concern for us and why we want a specific behavior:
1. When calling CallActivity the efect is that the engine creates a separate process.
2. In the "upper process" we have a non sequential "multi-instance-loop" that may contain multiple elements and we want process those elments in "pseudo-parallel" so one of them will not block the other while waiting for events. At the same time we don't want to process two jobs from the "upper process" at the same time since that may cause conflicts while writting data to external systems and accessing "upper process" variables.
So the question is: will the "upper process" notice that at it's lower level CallActiviti is running and will it maintain the "one job per tick for process" behavior? Or will both "upper process" and new process from callActiviti process their jobs at the same time?
If what we want to do can be done by setting parameters at bpmn level we would gladly hear how to set everything to achieve the desired behavior.