The Vault automation toolkit
- Vault API (SDK) – .NET access to Vault's web services for files, folders, items, BOMs, properties, lifecycles and users.
- Vault Development Framework (VDF) – a higher-level .NET library that simplifies connections, file operations and UI controls.
- Vault Explorer extensions – custom commands, tabs and event handlers inside Vault Explorer, for example checks before a lifecycle change.
- Job Processor – runs background jobs such as creating PDF, DXF or STEP files on release. Custom jobs extend it with your own logic.
var results = VDF.Vault.Library.ConnectionManager.LogIn(
"vaultserver", "Vault", "user", "password",
VDF.Vault.Currency.Connections.AuthenticationFlags.Standard, null);
if (results.Success)
{
var connection = results.Connection;
// search files, read properties, change lifecycle states...
VDF.Vault.Library.ConnectionManager.LogOut(connection);
}What to automate in Vault
| Task | Automation |
|---|---|
| Release | Check properties and drawings before release; block the change if data is missing |
| Neutral files | Create PDF, DXF and STEP on release with the Job Processor and store or publish them |
| Numbering | Custom numbering schemes, or numbers taken from ERP |
| Properties | Bulk updates, mapping between file and item properties, clean-up of legacy data |
| Notifications | Email or Teams messages when files change state |
| Migration | Bulk import of legacy files with folders, properties and revisions |
Connecting Vault to ERP
With Vault Professional, items and BOMs are managed in Vault. That makes it a natural source for ERP: when an item is released, its data and BOM can flow to ERP automatically. Common patterns are:
- Push on release – a lifecycle event or job sends the released item and BOM to ERP.
- Number from ERP – Vault requests a part number from ERP when an item is created.
- Two-way status – ERP data such as cost, stock or make/buy is shown in Vault for engineers.
- Middleware – an integration service or message queue sits between Vault and ERP, handling mapping, retries and logs.
Getting the mapping right
Most integration effort goes into mapping, not code: which Vault properties match which ERP fields, how units convert, how phantom and reference items are handled, how revisions map to ERP change control, and what happens when ERP rejects a record. Agree the mapping first and test it with real assemblies.
A Vault-to-ERP link is only as good as its mapping and its error handling.
ERP systems we connect
SAP, Oracle, Microsoft Dynamics 365, Epicor, Infor, Odoo, Tally-based systems and custom ERPs, through their APIs, middleware or files, depending on what each ERP supports.
Vault services
See Vault customisation and automation, Vault to ERP integration and Vault workflow automation.