Veeva Vault connector release notes
Veeva Vault connector 1.0.18.0
This release of the Veeva Vault connector features the following enhancements. For more information about the connector, see About the Veeva Vault connector.
System Enhancements
There are no system enhancements in this release.
Fixed issues
-
When crawling a large number of documents, if the API limit specified in the web.config file was reached, the connector would sleep for an hour leading to "invalid Session ID" errors. (BAI-16300)
-
If the Veeva Vault connector content source Content Sources do the following: Receive data from the Source System via the Connection, Filter the data it receives, Provide the results to the Target, Define the specific search index that contains the content you wish to index (and later search). was configured with a complex query filter with nested "AND" and "OR" operators, items would incorrectly be included or excluded from the crawl. (BAI-16316)
-
If an incremental crawl Scanning and capturing only new data from all of your content sources. This data did not exist when the last crawl was run. was run right after a full crawl, it would fail due to an invalid DateTime error. (BAI-16777)
Veeva Vault connector 1.0.17.0
This release of the Veeva Vault connector features the following enhancements. For more information about the connector, see About the Veeva Vault connector.
System Enhancements
| Feature | Description |
|---|---|
| Support for auto-managed groups | The Veeva Vault connector now supports fetching auto-managed groups. Auto-Managed groups are automatically created and populated by Veeva Vault during user role setup. For more information, see the Veeva Vault documentation. |
Fixed issues
-
Search queries that used "OR" or "AND" conditions were not being parsed correctly, resulting in no results being returned and an error is displayed in the crawl log. (BAI-15547)
-
The Veeva Vault connector was only crawling documents that were included on the first page of results. (BAI-15218)