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.
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.