Restrict manual assignament of file revisions

[vali_dobrea]

If using manual assign of revision on a specific category of files inside Vault, new revision could be added only if previous revision was approved. Assigning new revision should look back in the file history to see if previous revision was approved. 

Curently there is no posibility to secure / condition the assignament of new revision based on lifecycle state. 

Maybe one solution could be to add a security tab or option to be checked to eliminate this deviation from the lifecycle. 

[RajSchmidt]

So far I have seen this used only for manually bumping the revision for imported documents. In a standard process there is no need to do that, the revision is set during status changes.

And you could probably restrict the rights by creating a special role.

[vali_dobrea]

@RajSchmidt thanks for the reply! The purpose here is to eliminate a human error that does not follows the standard process. For me it is, I belive, the third time dealing with this situation. 

I do not understand how could creating a special role be helping on this issue? 

[RajSchmidt]

Hello @vali_dobrea! My ideas was to create a special role for that. Any user who is allowed to bump revisions would get this role. And you would then have to take away this right from all other users.

[ihayesjr]

@vali_dobrea 

Are you saying that your users are clicking the Change Revision option instead of following the lifecycle workflow?

If so, as @RajSchmidt stated, you could remove the "File Change Revision" permission from the user's role so they cannot do it. You need to create a custom role for those users without this permission.