Can we automate the propagation of a new shared process configuration?
We are looking at implementing the 'blue-green' propagation of process configuration changes that Sumant and others outline in the excellent article on managing process sharing. Basically, a process configuration gets branched, tested then re-introduced in an orderly fashion (vs changes the master and hoping that change that you just made to 100 project areas was correct.)
In the spirit of enterprise management, is there a way to programmatically batch update my child processes to pick up my new ready-for-production master ?
In the spirit of enterprise management, is there a way to programmatically batch update my child processes to pick up my new ready-for-production master ?