I see no reason for Vault to use numeric codes to represent errors. It would be much better if the error codes used words instead. For example, "InvalidUserPassword" is a much more useful error code than "301".
This is quite an annoying issue. I've created several Search Folders in Vault, which contain pretty complex search-parameters. Every time we migrate to a newer version of Vault (almost every year) I have to manually 'redesign' these search criteria... FOR EACH WORKSTATION THAT USES VAULT in our company!
It would be a great improvement of Vault Basic to incorporate a tool/function to export/backup AND import the search folders. Can't imagine other users don't think the same.
"I think it would be useful if PS would email users if they have a checked out file in Vault that has been checked out for more than X number of days/weeks etc without any activity (new checkin). I've found some people purposely or accidentally checkout a file and forget about it. I tried having them create a saved search, but it needs to be more of a "in the face" reminder.
It could also be a popup when you login that says something like... "you have X number of files that have been checked out for X number of days, would you like to checkin the files now?" Granted this may be tougher since you will have to use Inventor to do the actual checkin."
We need the ability to store all deployable files related to Inventor in the Vault. This includes, but is not limited to, the ability to put the Design Data folder into vault, and enhanced tools to manage Templates, Style and material libraries, and iFeatures within the Vault. Being able to deploy inventor settings XMLs through the project file would be very useful as well.
Basically, we need enterprise level tools to manage inventor configuration.