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.
Probably a different idea for a different day.
Similar to the find and replace functionality in MS Word and MS Excel this would be a good tool for finding files in not only the vault, but also in factory files as well.
This suggestions is to further the idea link posted below
and based on this thread.
When it is being sold as the integration point for Vault, the Item Master is inadequate.
First, lifecycles for items should be as configurable as for files. If you use the system as intended and control the lifecycle of the file through the item, you are severely constricted.
Items should assume the properties of the files that created them, or they should be easily called through the API.
Given the possibility that an item could be created before the CAD representation exists, there needs to be an ability to attach a CAD file as a representation of an item after the item has been created (this is also a huge hurdle if a company converts a product from 2D to 3D).
Document item types should exist so that external applications can reference and control files that don't represent parts.
OR do away with the item master and integrate the BOM capabilities (for 2D and 3D) of item master into the file interface and do away with item master altogether.
This would probably help with any plm integration, PLM360 included.
The Lifecycle Event Editor is currently available only through the Vault SDK. However the tool is not just for custom programmers. For example, it's used to configure Project Sync. Making it part of the Vault client would make admin tasks more convenient.
We are trying to add a stamp or Water mark in the file preview based on life cycle state change. There should be a option in the API to do so, based on the requirement in life cycle state change. Even tried to check if any event is assosiated with preview tab click.