# About the PromoMats-CRM Connection

Organizations using both a PromoMats Vault and Vault CRM on the same domain can use a standard Vault to Vault connection.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: The PromoMats-CRM Connection is only available for organizations with both a PromoMats Vault and Vault CRM.</p>
    </div>
  </div>
</div>



The PromoMats-CRM Connection enables the transfer of the following data from Vault CRM to your PromoMats Vault:

  * _CRM Product_ records
  * _CRM Product Group_ records
  * _CRM Detail Group_ records
  * _Content Groups_ records
  * _Surveys_ records
  * _Directories_ records 
  * _Content Types_ records
  * _Event Topic_ records
  * _Event Configuration_ records
  * _Country_ records

The PromoMats-CRM Connection also enables the transfer of the following data from your PromoMats Vault to Vault CRM:

  * _Product Family_ and _Brand/Product_ records
  * _Indication_ records

Vault notifies users when content is successfully published to Vault CRM via CrossLinks, and also notifies users of any errors.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: The PromoMats-CRM Connection works cross-domain between production and Sandbox Vaults. However, Vault does not populate production Vaults with data or documents from sandboxes.</p>
    </div>
  </div>
</div>



## Prerequisites

To use this feature, your Admin must complete the following procedures:

  * <a href="/en/gr/53358/#Establish_Vault_to_Vault">Establish a Vault to Vault Connection</a>
  * <a href="/en/gr/921794/">Configure the PromoMats-CRM Connection</a>

## How the PromoMats-CRM Connection Works

The PromoMats-CRM Connection supports synchronizing records from <a href="/en/gr/921794/#duplicating">multiple Vault CRMs</a>. While synchronizing records:

  * If a pre-existing record from the source Vault with a matching _CRM Org_, _CRM ID_, _External ID_, or _Link_ value exists in the target Vault, Vault updates the existing record.
  * If a pre-existing record from the source Vault with an identical _Name_ but different _CRM Org, CRM ID, External ID_, or _Link_ value, Vault creates a new record.

Vault uses the _Link_ field to look up matching records in Vault CRM. If the _Link_ field on an existing record in PromoMats is blank, the PromoMats-CRM connection uses the _External ID_ field.

### How the Country Integration Works

Vault CRM includes a _Connection Settings_ object type, such as _CLM Integration Settings_, for each feature that supports document routing based on country. Within this object, users can select multiple _Country_ (`country_cda__v`) values from the _Country Filter_ picklist to route content for their PromoMats Vault.

In the PromoMats Vault, a _Connection Country_ record is created to match the _Countries_ selected from the filter in Vault CRM. The connection confirms that it creates a _Connection Country_ record for each _Country_ (`country__v`) record which has the _Country_ (`country_cda__v`) field populated with values that match the values in the _Country Filter_ picklist in Vault CRM.

For example:

* **Vault CRM A**: The _Country Filter_ picklist is populated with **United States**.
* **Vault CRM B**: The _Country Filter_ picklist is populated with **United States**, **Canada.**
* **Vault CRM C**: The _Country Filter_ picklist is populated with **Mexico**, **Canada**.

Subsequently, the PromoMats Vault will have _Country_ records for the **United States**, **Canada**, and **Mexico**, and the _Country_ records will have their _Country_ fields populated with `country_cda__v` picklist values for their matching countries. Additionally, the _Global Country_ record also has its _Country_ field populated with `country_cda__v` picklist values of **United States**, **Canada**, and **Mexico**, along with other countries listed.

After Vault synchronizes Vault CRM with the PromoMats Vault, the _Connection Country_ object creates records as follows:

* **Vault CRM A**: United States, Global
* **Vault CRM B**: United States, Canada, Global
* **Vault CRM C**: Mexico, Canada, Global

If Document A in the PromoMats Vault has a _Country_ field of **United States** and is updated with a new description, Vault CRM A and Vault CRM B are updated with the new description in near real-time, based on the records in the _Connection Country_ object.

If Document B is created in the PromoMats Vault and has a _Country_ field of **Global,** Vault CRM A, Vault CRM B, and Vault CRM C are sent Document B in near real-time, based on the records in the _Connection Country_ object.

### How the CLM Integration Works

With the CLM Integration, Vault can distribute approved multichannel presentations and slides from PromoMats Vaults to Vault CRM. This connection ensures that content approved via a standard MLR (Medical, Legal, Regulatory) workflow is available for use in CLM within Vault CRM. The CLM integration uses the standard Vault to Vault connection to establish a bridge between your source PromoMats Vault and the target Vault CRM to share content approved for distribution.

Vault can transfer CLM content in the format of a binder containing slides. Users can manually create a binder and slides for transfer or use the _Create Presentation_ user action to generate a binder and slides, but CLM auto-publishing is not supported for use with this integration. 

PromoMats Vaults automatically publish content to Vault CRM when a document's _Publish for CRM (CLM)_ (`clm_content__v`) field is set to _Yes_. Content is withdrawn when this field is set to _No_ or moves into an _Obsolete_ state. For every document published, Vault CRM creates a CrossLink of the original source document. This CrossLink connects the production Medical Vault to the sandbox Vault CRM across domains.

To ensure that the correct content reaches the right audience, Vault routes documents to specific Vault CRM environments based on their _Country_ assignments, using the _CRM Connection Country_ object and routing logic applied via the `country__v` field.