Pushing Data to Vault
A Push to Vault outbound connector is available allowing admins to push Nitro data to Vault. When Nitro data is available in the Vault platform, it can be used to drive Vault-specific workflows and business processes. For example, Nitro users can derive CRM usage of documents and HCP deciling/segmentation using multiple commercial data sources. These insights can then be tied to content and HCPs in PromoMats and Align, respectively.
The Vault outbound connector only supports custom Vault Objects and Documents.
The Veeva VAULT outbound connector uses the Vault REST API v21.3.
To push Nitro data to Vault:
Log into the NAC.
Select Outbound Connector from the Connectors menu.
Select the New Connector button.
Enter data for the required fields in the Outbound Connector Details section:
Admins can also select the Import Connector button to import a Veeva VAULT outbound connector configuration.
- Display Name
- Target Type - select Veeva VAULT
- Target System Username - Vault username
- Target System password - Vault password
- Target Endpoint
Ensure the Active check box is selected.
Select Add next to Source to Target Mappings.
Select the following values in the Table Mapping section:
- Connector - Nitro connector
- Target Table (VAULT)
- Source Table (Nitro)
- Target Table Data Operation - UPSERT, UPDATE, INSERT
Only UPDATE operation is supported for Documents.
Add a Source Table (Nitro) SQL Filter. This step is optional.
The Target Table Batch Size is a value from 1-500.
Select specific columns to map from the Nitro table selected above to the Vault table selected above in the Column Mapping section. Add rows as needed by selecting the + button.
Admins can run a Veeva VAULT outbound connector job as ad hoc, scheduled, or as part of a Job Orchestration, then view the results and outputs of the job in the Job History console.
Admins can reorder the source-to-target mappings to change the order in which they are processed by editing the connector. Select the Preview button to view the first 100 rows and columns of the source query.