Active Instances to stick with Old Version of Code - Post Deployment

For this reason we have been implementing a 'version' variable in our process models - this integer is passed from parent to sub processes where you can define processing based on which version the parent model is running under. When you implement changes to the parent, increase the version flag and your sub process can use this logic where necessary: if(pv!version<2,*use old methods*,*use new methods*). Since both running/active parent and new parent processes will use the same sub process version, something such as this manual control is necessary if you need to maintain legacy sub process function for legacy parent processes.

For this reason we have been implementing a 'version' variable in our process models - this integer is passed from parent to sub processes where you can define processing based on which version the parent model is running under. When you implement changes to the parent, increase the version flag and your sub process can use this logic where necessary: if(pv!version<2,*use old methods*,*use new methods*). Since both running/active parent and new parent processes will use the same sub process version, something such as this manual control is necessary if you need to maintain legacy sub process function for legacy parent processes.