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.
If I'm not wrong, at this time, Vault is able to map and import existing iProperties coming from "User Defined Property" property set only.
If for some reason or particular customization you need to create your own PropertySet with custom iProperties, you will not be able to import them into Vault UDPs.
I think it would be very useful to extend this feature and allow administrators to map iProperties from any Property Set.
Just for an example, with this feature available, you'll be able to import into vault the "IsCustomPart" iProperty that's simplify rules to understand if a ContentCenter part is a "real" CC part or not.
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.
When you edit > copy/paste a link/shortcut to a file into another folder on Vault's thick client it does not appear on the web client.
In a large company where licenses may be an issue the web client is ideal and should include links to drawings so people can access these drawings easily from different folders. In our case we asbolutely have to refrain from using this feature due to its in ability to appear in the web client. This limits the folder structure within Vault.
Ensure that edit > copy/paste shortcuts to files appear in the web client as well as the full / thick client.