Hi all. Our Vault is heavily customised, I have a load of automated triggers from third party developers that kick in on file and item lifecycle state change. The problem I have is all the add-ins are Vault Client based, they don't all function 100% if a file is changed state from within the CAD client.
Rather than ask the developers to extend their code into the CAD clients, I'd prefer to have the option to completely remove the ability to change lifecycle states from within CAD clients. Is this possible? If I need to do a registry hack I'll do it!
This can be done with another Vault API trigger. Hook into the GetRestrictions event on a file lifecycle change. In the GetRestrictions code, check the process name. If you are running in a CAD application, you can add a restriction and block the operation.