The Veeva Vault Connector will crawl content from a Veeva Vault repository.
Introduction
The connector extracts content from Veeva Vault using Vault Query Language (VQL) statement (a SQL-like statement) that specifies the object to query (in the FROM clause), the fields to retrieve (in the SELECT clause), and any optional filters to apply (in the WHERE and FIND clauses) to narrow your results.
Also extracts the following from the resulting Vaults Objects:
- Attachments
- Renditions
Environment and Access Requirements
Repository Support
In order to access the Veeva Vault and make API calls against Vault, you need a Vault user account with API access.
The Veeva Vault connector supports crawling the following the repositories versions:
| Repository | Version | Connector Version |
|---|---|---|
| Veeva Vault | 21.3 | 5.0.3 |
Environment Requirements
Other Veeva Vault versions could work with the connector, but is not guaranteed.
Framework and Connector Features
Framework Features
| Name | Supported |
|---|---|
| Content Crawling | Yes |
| Identity Crawling | Yes |
| Snapshot-based Incrementals | Yes |
| Non-snapshot-based Incrementals | No |
| Document Hierarchy | Yes |
Content Crawled
The content retrieved by the connector is entirely defined using VQL statements, so you can select a subset of fields from one or more vault objects. Initially, the data is inserted into Aspire using the returned column names, but this may be changed by further Aspire processing.
The Veeva Vault connector is able to crawl the following objects:
| Name | Type | Relevant Metadata | Content Fetch & Extraction | Description | Reference |
|---|---|---|---|---|---|
| Vault Object | container | object quarriable fields | apply depends on the object, example documents | Fields requested by VQL | Vault Object Documentation |
| Attachments | document | Yes | Attachment document to object | Attachments Documentation | |
| Renditions | document | N/A | Yes | Another attachment type to an object |
For more information about a VQL Query please visit the reference documentation Vault Query Language (VQL).
Limitations
The Veeva Vault Connector has the following limitations:
- The content extracted depends on the fields configured on the VQL query.
- The ID field is needed in the VQL query.
- An update of the renditions or attachments does not update the parent vault object.
- Vault limits the number of API calls that can be made every 5 minutes (burst). When a vault has reached the burst limit, each subsequent API will be delayed by 500ms until the burst period has expired.
- Vault limits the number of Authentication API calls that can be made every minute (burst) based on the username and the domain name used in the API call. When the limit is reached, the API returns an API_LIMIT_EXCEEDED error message and no further Authentication API calls to the vault will be processed.
Overview
Content Tools
Copyright © 2024 Accenture
