For people who use a structured file system the inevitable gaps that eventuate when using Vault Numbering Schemes are a real pain. Here is a thread discussing it. Surely it can't be that hard for the Vault Developers to change this function? Vault can assign numbers but nothing should be done (numbers allocated) until Save is hit. This change in action would eliminate the gaps and make our lives better.
Being an ex-Solidworks PDM administrator, it would happen to me quite oftern where I would have to restore a single file to the PDM environment. This would require logging on to the PDM server and moving the deleted file (which was never really deleted, just moved to a location within the PDM so out of viewing sight from the casual user) back to it's original location. This was an operation that only an administrator could perform. Having had training to do this it was a rather simple operation. So I am requesting similar abilities be implemented here in the Autodesk Vault side of the world.
Please see this thread that explains the conditions I was faced with and have been from the past.
As it currently stands it is not possible to delete users and groups within Autodesk Vault.
This is a problem. I understand Autodesk's stance on that the users need to be retained for historical reasons, however the management side of things needs to be improved.
For example I created a group and users that were never used. Why can't I delete them? Objects that were never used should be allowed to be deleted. Also as the database grows and users are hired and terminated, the list will grow to an unmanageable mess.
What has happened to me is that I am in the middle of implementing Vault for my company. When I first set it up I created users. However, since then we have switched to a Domain and have now imported the Domain users and groups to use. Now I have groups and users that have never been used that I have no way of deleting or using for anything else.
I have found blogs and forum posts suggesting that users be diabled and renamed so that they are sorted appropriately. This is a hack solution at best and not a real solution to the problem.
As I see it two things need to happen:
1. Unused users and groups need to be allowed to be deleted.
2. There needs to be additional options and sorting methods for used users and groups that are no longer active. ie. Once they are disabled they are moved to a different list and only retained for historical purposes.
Allow Vault installation/configuration to connect to an Instance not named AUTODESKVAULT
We have several separate vault servers (Professional) all connected to remate databases on an SQL cluster. The SQL people claim that they can only have one single instance called AUTODESKVAULT in their complete environment AND that instance names MUST follow their naming conventions
Actually, vault is the only software that I know of that requires a specific instance name
So far, Vault is the only program I use where I have to type in something special to find a piece of a text string. Everyother program with a search function will find “AutoCAD” if I just search for “CAD”, except, ironically enough… Autodesk Vault!
Having to use wildcards and boolean operators in the age of Google seems antiquated.