Any iLogic Rules That Make Vault Better?

[Anonymous]

Hello everyone,

The engineering department I work is adopting Vault and upgrading from Inventor 2016 to 2019.  We are hoping to go live in about a week.  Since we are new to this, I was wondering if there are any iLogic/API rules available that help make things run smoother.

I know this is a vague question but, I'm not really sure what I am looking for.  Any info would help.

Thanks

[philip1009]

Unfortunately there's not a lot immediately available since the API for the Vault Add-In for Inventor is either not exposed or if it is exposed, it's not documented.  If you have either Vault Workgroup or Professional, the API is exposed so programs can be made in VBA fashion, but not in iLogic.  The only bit of code I've used in iLogic is to deactivate and reactivate the Vault Add-In, when you run code that opens and closes a bunch of documents, the vault add-in will pop for every document.  You can deactivate and reactivate the add-in with this code:

SyntaxEditor Code Snippet

oVault=ThisApplication.ApplicationAddIns.ItemById("{48B682BC-42E6-4953-84C5-3D253B52E77B}")
oVault.Deactivate
'Run Code.
oVault.Activate