Not sure how often this comes up for other users, but where I work it comes up a fair amount.
If there was a way to export out the detailed list of uses for an assembly out of vault, say into a notepad file this would be useful. I know this functionality is not in workgroup. If it is in Pro please funnel this function down to lower versions.
Going through an implementation of vault, the lack of the option for a multi-list as a property type is very limiting when it comes to integration.
This may be a limitation that stems from matching the capability of the authoring tools, but those could stand to be updated as well. Alternatively, there could be a translation that would take a comma separated list in a property or attribute into a multi-list property.
I have had my VAR in and there was no solution currently for this.
When we had the revision in the rev table on the drawing being driven by Vault, the previous rev line would revert to the newly created revision. We would have to manually change it back and update the new line to the current rev. There is an obvious glitch in the software that is causing this.
What should happen is when the vault is driving the revision block the new revision row comes in and not only shows the newly created rev, but leaves previous revision lines as they were.
This condition also seems to exist for the description. In general it seems like there is a communication issue between this revision block and vault.
Can we please be a little more descriptive in the error messages?
I get a message that tells me I cannot move a specific file in the vault from one location to another.
The message reads "File Cannot be moved" looking at the details it says "File could not be moved due to vault error"
Really? Why couldn't it have explained to the detail of saying one of the factory files was checked out causing this file not to be moved. This is just one example. I would like to see all messages be a little more descriptive.
Side note. I would like to see less messages as well. That is more of how the software is written though.