Integrating CRM and Vault for CLM

CLM requires an integration with an instance of Veeva Vault in order to deliver approved content to end users. Integrating CLM with Vault streamlines the process for managing and distributing CLM content to end users, ensuring they have the most current and relevant information on their device. The subscription pulls CLM content from Vault into CRM where it is deployed to end users. The integration administration console is managed in Veeva CRM. CLM content and data is managed in Veeva Vault.

The Multichannel Loader simplifies the process of loading CLM content into Vault. For more information, see Vault documentation.

Vault uses lifecycles to manage content. Documents are assigned to the appropriate document states defining a lifecycle. Vault admins can control the availability of content to end users in CRM using the states. CLM content in Vault can also be automatically published to CRM. See Using Vault's Auto-Publishing for CLM for more information.

To improve load times and overall performance for CLM content, admins can enable the China CDN for users in China. See Using the China CDN for Multichannel Content for more information.

CLM-Vault Integration Lifecycle

  • The CLM integration releases the CRM Content Lifecycle for the Slide document type. The lifecycle can be updated or replaced with a new lifecycle to manage content.
  • Draft content is automatically sent to the Staged CDN. To make content available on the Production CDN, the lifecycle’s steady state should utilize the Send to CLM entry action. Entry actions are automated functions Vault performs when a document enters a designated state. For more information about working with CLM content in Vault, see the Vault documentation.
  • In the CRM Content Lifecycle, the Send to CLM entry action at the Approved state puts content on the Production CDN. Approved is the designated steady state for the lifecycle.
  • At least one lifecycle state needs Withdraw from CLM as an entry action for content to be removed from the CDN. Withdraw from CLM entry action at the Expired state removes content from the Staged and Production CDNs.
  • If the Content User needs the ability to explicitly send and withdraw content from the CDN, place the User action, Send to CLM on the lifecycle state required
  • Send to CLM only displays if the CLM Content flag is selected.
  • The CLM integration releases the Binder lifecycle for the Binder Presentation document type. The lifecycle can be updated or replaced with a new lifecycle to manage Binder Presentations.
  • The Binder Presentation document type should be assigned a different lifecycle from the lifecycle that is assigned to the Slide document type. The states in the Binder Presentation life cycle should not have the Send to CLM action.

In some versions of Vault, the CLM Content label reads iRep Content.

Vault API requests sent from CRM are monitored and limited to avoid interrupting integrations. 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.

Admins can integrate Vault with CRM and perform the following tasks to maintain and update CLM content: