About the Veeva Vault Connector

Features

BA Insight’s Veeva Vault Connector securely indexes both the full text and metadata of Veeva Vault objects into SharePoint’s search engine, as well as Azure Search and Elasticsearch.

• For more information about Veeva Vault Connector abilities and features, see https://www.bainsight.com/connectors/veeva-vault-connector-sharepoint-azure-elasticsearch/.

Security

The BA Insight Veeva Vault connector honors Veeva Vault security in determining which documents users can access.

Limitations

Performance and Throttling

• Because Veeva Vault limits the number of API calls it accepts, the connector must be throttled to stay within the allocated quotas.
• You can do so by limiting the number of concurrent documents crawled at the search engine level.
• Consider the API limitations when scheduling the security sync job.

The connector consumes the following API calls at indexing time:

• 1 call per 1000 supporting documents (both full or incremental)
• 1 call per 1000 docs enumerated (both full or incremental)
• 1 call for deleted documents on incremental crawls
• 1 call for retired documents on full crawl
• 2 to 6 calls per item indexed
  • 1 call for the metadata
  • 1 call for the file binary
  • 1 call for all record attachments
  • Up to 2 calls for security ACLs (information is cached)

• Minimum number of calls for each item: 2

  • 1 call for item metadata

  • 1 call for item content

• There are 4 other possible calls:

  • 1 is a fallback to get the document version from Veeva if both the in-memory and on-disk caches are lost

  • 1 is a fallback to get the reference field name values if both the in-memory and on-disk caches are lost

  • 1 is if the security cache is empty

  • 1 is if the item has attachments

For the Security Sync Job:

• 1 call per 1,000 users enumerated
• 1 call per 1,000 groups enumerated