Attatching Revision Schemes to Vault Lifecycles and not Categories

[ThomasSwanson]

I have seen several post on here about Changing categories and the manual process that has to occur after that to make sure the files then have the correct lifecycle and revision scheme. 

I have seen more post about having two revision schemes one for Production and one for Development and having to keep those straight. 

How about this for a solution.

Attach the Revision schemes to the Lifecycles.

That way you can define when a part changes state it can change revision scheme types.   This would all you to put everything (Dev Wip, Dev Released, Prod Wip, Prod Released) all in one lifecycle, and have the lifecycle change the revision scheme when moving from Dev to Prod.  This way the user just changes state and you don't have to worry about coming back and changing this.

[ryan]

Many customers use different revision schemes within their lifecycles and it would be great if vault could change the revision scheme automatically as part of a lifecycle transition.  

Today, users have to make the change manually which is aggravated by the fact that you cannot change the assigned revision scheme from within an Add-in (assigned revision scheme can only be changed from within Vault Explorer).  In past implementations I have always lamented having to show a customer how to change revision scheme because the workflow is clunky.

In summary, I want the ability in the definition of a lifecycle state transition to enable an Action that is "Automatically assign Revision Scheme <dropdown>"

-Ryan