Veeva Vault Reader
Note
This adapter is in preview and is available on Striim Developer only. See Striim Developer for more information.
Veeva Vault is a cloud-based document and content management system that assists businesses with managing regulated content and documents in areas such as clinical trials, regulatory affairs, and quality management. The Veeva Vault Reader allows businesses to instantly connect and integrate Veeva Systems data with various applications, databases, and business intelligence tools in real time.
Feature summary
Feature | Supported? | Notes | |
---|---|---|---|
Objects | Standard objects | ✓ | |
Custom objects | ✓ | ||
Authentication | Basic authentication | ✓ | Username and password |
OAuth authentication | Manual configuration based | ||
Custom authentication methods | Not all methods may be supported | ||
Operations | Automated mode | ✓ | |
Initial load | ✓ | ||
Pull-based incremental load | ✓ | ||
Push-based incremental load | |||
Automated pipeline | |||
Governance | Connection profile | ||
Sherlock AI | |||
Sentinel AI | |||
Schema handling | Initial schema creation | ✓ | Works with supported targets |
Schema evolution | |||
Setup | Wizard template | ||
Flow Designer | ✓ | ||
Striim TQL | ✓ | ||
Runtime | Resilience/recovery | ✓ | |
Parallel execution | |||
Metrics | ✓ | Standard metrics |
Supported authentication method
The Veeva Vault Reader supports basic authentication using a username and password to authenticate with the Veeva Vault server.
Supported objects
The following are the supported objects for reading from Veeva Vault:
AuditHistory
DocumentRelationships
DocumentRoles
DocumentUserActions
Lifecycles
ObjectRelationships
ObjectRoles
ObjectTypes
ObjectWorkflowTasks
ObjectWorkflows
Veeva Vault Reader properties
Property | Type | Default value | Notes |
---|---|---|---|
URL | String | Base URL of the Veeva Vault instance, typically of format: https://<your-instance>.veevavault.com. The Veeva Vault URL is the same URL you use to access the Veeva Vault web application through a browser. | |
Username | String | The Veeva Vault user account used to authenticate. Together with Password, this field is used to authenticate against the Veeva Vault server. | |
Password | Password | The password used to authenticate the user. The Username and Password are used together to authenticate with the server. | |
Connection pool size | Integer | 20 | Specifies the maximum number of active connections. |
Exclude tables | String | A list of tables excluded from read operations. Typically used to create a list of exceptions when the Tables property includes wildcards. Misconfiguration of the Tables and Exclude Tables properties can cause "Invalid table names" errors. | |
Incremental load marker | String | The incremental load marker is a unique incremental column in each object used for incremental load. When no marker is specified, tables are resynced at each polling interval. Specify the name of the column that contains the start position value. This column must meet the following criteria:
| |
Migrate schema | Boolean | False | Only available in Initial Load or Automated mode. Set to |
Mode | Select list:
| Automated | Automated mode applies incremental updates to objects that support incremental load and performs full resyncs for objects that do not support incremental load. |
Polling interval | Integer | 5m | Specifies an interval as an integer followed by a unit. Supported units are days ( |
Refresh token | Password | An OAuth 2.0 refresh token.Use the value generated while creating the token. | |
Start Position | String | %=-1 | Value of the incremental load marker that defines the initial reading position. |
Tables | String | A semicolon-delimited (;) list of objects to read from the source. Supports the | |
Thread pool count | Integer | 10 | The number of parallel running threads. The default value of zero specifies single-threaded operation. When the value of the thread pool counter is higher than the connection pool size, large data ingestion operations can cause the app to halt. Since best performance is achieved when using one thread for each table being synced, increasing the size of the connection pool to match the number of threads in use is a performance best practice. |