topic Version mapping between Parent and Child workflows in Alfresco Archive

Version mapping between Parent and Child workflows

sandeepkhatri01 — Thu, 12 Dec 2013 17:26:40 GMT

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

Re: Version mapping between Parent and Child workflows

frederikherema1 — Fri, 13 Dec 2013 08:17:32 GMT

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.

Re: Version mapping between Parent and Child workflows

sandeepkhatri01 — Sun, 15 Dec 2013 09:45:24 GMT

Thanks. I did some queries on Activiti Schema and reached to conclusion. I'll again validate my understanding by deploying some more workflow

Re: Version mapping between Parent and Child workflows

frederikherema1 — Mon, 16 Dec 2013 07:41:26 GMT

Please share any thoughts/solutions around this topic.