nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Behavior of CallActivity when deploying new versions

ndt

Hi

If i have a deployment with a process (process1) containing a CallActivity starting another process (process2) then deploy a new version of these processes, what will the existing process instances of process1 start when reaching the CallActivity starting process2. The version from the old deployment, from which the process instance is started, or the new version?

The reason that I am asking is that we have this situation where we have added some new parameters to process2 and now all existing instances from the old version is failing when starting(and executing) process2 with the message that the new property does not exist.

Find more posts tagged with

Comments

frederikherema1

A call-activity by default, calls the latest version of the process that is configured in "calledElement".

ndt

A call-activity by default, calls the latest version of the process that is configured in "calledElement".

What are the possibilities for having it call a older version?

frederikherema1

<br> public void execute(ActivityExecution execution) throws Exception {<br>&nbsp;&nbsp;&nbsp; <br> String processDefinitonKey = this.processDefinitonKey;<br>&nbsp;&nbsp;&nbsp; if (processDefinitionExpression != null) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; processDefinitonKey = (String) processDefinitionExpression.getValue(execution);<br>&nbsp;&nbsp;&nbsp; }<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; ProcessDefinitionImpl processDefinition = Context<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .getProcessEngineConfiguration()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .getDeploymentManager()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .findDeployedLatestProcessDefinitionByKey(processDefinitonKey);<br>&nbsp;&nbsp;&nbsp; <br>&nbsp;&nbsp;&nbsp; PvmProcessInstance subProcessInstance = execution.createSubProcessInstance(processDefinition);<br>

You'll have to extend the CallActivityBehavior to use, for example, a fixed processDefinition ID instead of a key in the field processDefinitionExpression (which corresponds to the BPMN calledElement). You can easily alter the ActivityBehaviorFactory used by the latests parser in order to accomplish this. If you're not able to wait for the 5.12 version, you'll have to use a BPMNParseListener and replace the ActivitiyBehaviour yourself when the process us parsed.