![]() An example would be mapping a custom field on an Email Template in Vault to a custom text field on Approved Document records in CRM.Ĭustom mapping is available by default if the integration is configured. Users can map custom fields and VOF (Vault Object Framework) records to CRM fields using the CRM-Vault Integration. Select Pull Vault Statistics to retrieve Document Views and Downloads from Vault.Select Full Force Refresh to retrieve documents from Vault.Verify the Is this a SandBox field is selected if appropriate.Verify the User value in the Salesforce Approved Email Credential Management section matches your Veeva CRM user name.Select Validate to confirm the credentials are authenticated against SFDC. Indicate whether the account is a sandbox.Enter the credentials for the integration user account.Select Edit under the Vault Login Credential Management section of the Approved Email Administration tab.The Veeva Approved Email Credential Management section enables admins to define an integration user whose credentials are used to integrate with Vault. This provides an audit trail within Vault that lists all SFDC orgs that reference each Email Template or Email Fragment Write events related to the Incremental Refresh and Full Refresh processes back to the Vault activity log.Query Vault to pull Vault document events (views and downloads by email recipients) into the Email_Activity_vod object.Query Vault to validate outbound Email Templates, Email Fragments and all referenced Vault documents are in an approved or steady state prior to sending an email.Query Vault during the Full Refresh of Vault metadata into the Approved_Document_vod object.Query Vault during the Incremental Refresh of Vault metadata into the Approved_Document_vod object.All actions are fully audited in the Vault activity logs. The Vault authentication credentials are used for several Approved Email integration processes. The Vault URL endpoints and optional Vault WHERE clause display in this section. Ensure that the Vault Integration User has access to Events API in Vault. ![]() If the password ever expires, the integration will fail. The Vault integration user must be assigned to a Vault Security Policy (Users->Settings->Security Policy) that has a Password Expiration value of No Expiration. Select Validate next to the credentials to confirm their authentication and create a connection to Vault. ![]() Users can connect to multiple Vault instances, with each line representing a single Vault instance from which the integration pulls Vault Document metadata into the Approved_Document_vod object in CRM.Īdmin users must supply a Vault username and password for each Vault instance, and this user must have the Vault User Type of System Admin. The Vault Login Credential Management section manages the Vault credentials for integration with CRM. ![]() Multichannel functionalities relying on the integration between CRM and Vault, including Approved Email, CLM, and Engage, send API requests to Vault and should not hit Vault API limits. Vault API requests sent from CRM are monitored and limited to avoid interrupting integrations. The Approved Email Administration Tab manages this integration and enables admins to manage the integration user, manage and validate Vault credentials, map Vault fields. Integrating CRM and Vault for Approved EmailĪpproved Email requires an integration with an instance of Veeva Vault in order to deliver approved content to end users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |