Hello, On our project we maintain some Processes that work 'sequentially' for entire month, and when a new month begins, they start a new cycle. Now let's imagine we want to deploy a new release, taking effect in the next month not to corrupt current outcomes. Then we have to remember to do it. If there are more deployments to recall, it starts to be complex. I suggest to consider some delayed deployment, so an admin can import a release / Process / Object, selecting the time when it takes effect. Then nothing to remember, just it will take effect itself. Regards, Pawel
... View more