Version mapping between Parent and Child workflows

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.

sandeepkhatri01

My understanding of Activiti says that –
Once I deploy the parent and child workflows, Activiti creates a mapping between parent workflow version and child workflow version.  On redeploying/editing the child workflow new version of child workflow is created. However, parent workflow still points to old version as mapping as already been created on first deployment.

Parent workflow doesn't point to latest version of child workflow unless parent workflow is redeployed.

Is my understanding correct ? If yes, Then I want to control this behavior. I want My parent workflow to always point to latest version of child workflow. Is this can be achieved ?

Or Is there any better way to manage this ?

frederikherema1

I guess you're referring to a call-activity. The call-activity will always start the LATEST version of the referenced process-definition (that is, the latest process-definition deployed for the key that is configured).

So only redeploying the called-process (child) will cause all NEW parent-processes to use the new deployed versions. All running processes, which are currently executing the child-process, will keep using the old child-process. Existing parent-processes which have not yet reached the point where the call-activity is, will also use the new child-process, once the call-activity is executed.

Hope this enlightens you. Not sure how you got to the above conclusion, userguide states:

Note that the process definition of the subprocess is resolved at runtime. This means that the subprocess can be deployed independently from the calling process, if needed.