How a Callactiviti can access the parent process variables?

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

purna_cherukuri

Hi,

I am trying to use CallActiviti in my BPMN2.0 process.  But I found it mandatory to pass the input variables to call Activiti as it runs in a child execution. 
Is there a way to pass whole set of parent execution's variables to Callactiviti without mentioning each and every one in bpmn2.0 xml?  Or is there a way to tell Callactiviti to share the variables from it's parent execution without mentioning all the variable names in my process definition?  

We have a large set of variables to pass through, and I am finding it as a maintanence issue if we hard code the variable names in process definition.  Please suggest me on this.

frederikherema1

Where do you want to use the process-variables? If you look on how activiti handles this, indeed a child-execution is created in the process-instance. In an expression or in a JavaDelegate you have the "execution" object available. If the variable is NOT defined on the execution itself (in this case, the callActivity execution), the parent is consulted. This goes up the execution-tree until a variable is found…

So just calling execution.getVariable("myVar") from within the callActivity execution will get you the values in the process…

The reason why the IN and OUT's are there, is because of the BPMN 2.0 spec. So this will only work in the activiti-engine, and is not explicit ally part of the spec