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.
My understanding is that Vault currently uses a client local version of MS Reporting Services to render reports in the Vault client. I would like to see support for the server version of Reporting services. This way I could write companywide dashboard reports. I would also be able to link Vault data to ERP system data. We should have a way to use Vault API calls when developing SSRS reports. If there is currently a way to do this I would like to know.
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.
on 07-25-201208:00 AM - last edited on 01-14-201301:10 PM by ihayesjr
I'm not sure if it is allowed to request new API features in Idea Exchange.
It should be possible to enable/disable custom commands introduced by a vault extension. E.g. if a command is only available for a special user (Administrator) the command should be disabled for all other users.
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.