We have had several clients that would like to reset the next number in a change order scheme. They may pilot the ECO scheme starting at 1 and then want to go to production with the numbering continuing from 1001. At this point, you have to create a new scheme to do this. Most clients are much more comfortable with continuing to use the existing scheme prefix.
When copying a design with a prefix or suffix you have to individually then delete the existing prefix or suffix to then apply the new one this is simply painstaking. The prefix suffix should have a replace function so you can enter the old then enter the new one done.
PLM 360 has a fairly functional scripting feature, so why can't Vaut?
PLM's scripts are easy to write and run in response to user actions, such as creating an item, or changing lifecycle state.
Since PLM's scripts run server-side, they become part of the core business logic. In contrast, Vault's API is client side, which makes it hard to build custom business logic. For example, setting a propery value on state change is much easier with PLM scripting than with the Vault API.
Other file management solutions allow for differentiation of folder structure by role (not role like with security in Vault, but role within a company). That is, people in different groups see different folder structures when they open the vault. While I believe that the current method should be retained, for those companies that have enough properties on their file objects to pull this off could see a huge benefit.
These folder structures would be created based on properties. Think of it as a supercharged saved search folder. Users, who are required to enter the descriptive properties anyway wouldn't be required to describe the object again when they select save location for the file (the same argument I have against intelligent part numbering). Also, this would allow different groups to coexist within the same vault without having to compromise efficiency so that they can use the same folder structure.
When it comes to local workspace, it doesn't really matter if it matches the displayed folder structure. This would allow vault to store the files locally in whatever structure is most efficient for the programs that use them. Pack and Go could still allow a user to export files into a particular folder structure for use outside of the PDM system.