A few months ago my colleague Mike Space wrote about powerVault – a native PowerShell extension produced by coolOrange that can dramatically simplify interaction with the Vault API. Today I’d like to build upon that idea by illustrating how using powerVault in conjunction with the Vault Data Standard can provide a complete solution for customizing Vault behavior.
There’s a neat ‘trick’ you can perform using Vault Data Standard (VDS) and iLogic that involves creating Engineer-To-Order (ETO)-type components. If you have a semi-standard product line that changes based on customer spec you can use VDS to help create new iterations of those components, and even off-load the creation of those components to non-CAD users.
powerVault is a native PowerShell extension that allows you to talk with Vault via pure PowerShell command-lets.
With powerVault, you get command-lets for dealing with files and items. For instance “Open-VaultConnection” for establishing a connection to Vault, or “Get-VaultFile” for getting/downloading a file, or “Get-VaultItem” for getting an item and many more.