This article details how to create, publish, distribute, and withdraw Engage content. For general information, see About CLM & Engage Integration.
How to Add Engage Content
The process below details the steps you’ll need to complete in order to publish content to Engage. Generally, you won’t follow these steps all at once.
- Create a new document by uploading a source file. You can upload a PDF, image, or video file for Vault to auto-generate a distribution package. For HTML content, upload a ZIP file distribution package.
- Set the Document Type to Multichannel Slide.
- Set the document field Publish for Veeva CRM (Portals) to Yes.
- Select a media type for the CRM Media Type field.
- Set any additional document fields that are needed and finish the document creation process. Once the document is created and Vault has finished auto-generating distribution packages, Vault publishes the content to Engage. (See details about publishing and distributing.)
- Create a binder and set its Document Type to Multichannel Presentation.
- Add Multichannel Slide documents to the Multichannel Presentation binder.
- Take the binder through its lifecycle.
- Log into CRM and sync with Vault. This action creates the records in CRM that match your Vault documents.
Note: You can use any document type to add CLM content by adding the applicable existing multichannel shared fields to the specified document type.
How to Use the Shared Resource Relationship
When working with Multichannel Slide documents, you can use the Related Shared Resource relationship types to connect the content in the Engage player. This relationship connects another document to the Multichannel Slide document. The target document must have the Multichannel Slide document type. Typically, this document will contain a bundle of images, CSS, or JavaScript files that are used within the referring slide. The document must have the Shared Resource field set to Yes.
How to Preview Presentations
Use the Preview action on a Multichannel Presentation binder and then select a specific website to see what the presentation would look like on an actual website. Note that only documents that you have published will appear in the preview.
How to Withdraw Engage Content
You can withdraw individual Multichannel Slide documents from CLM using the Withdraw from Stage Engage or Withdraw from Production Engage actions. If the documents have not yet been distributed, this will prevent distribution. If the documents are already distributed, this will make them unavailable for further distribution in Engage. Note that if you withdraw a document and then update the distribution package, Vault will automatically re-publish the document.
These options appear automatically in the Actions menu for any document that’s been sent to Engage. By default, the CRM Content Lifecycle withdraws documents as an entry action for the Expired state.
Deleting documents from the Vault will also withdraw them from Engage.
Distributing Engage Content to China
If your organization distributes content to Chinese customers, your Admin can enable the shared document field Use China CDN. Then, you can set this field to Yes in the Multichannel Properties section of the Doc Info page to indicate that Vault should replicate the content to the China-hosted CDN.
Document Fields
The following document fields appear on documents or binders when you’re using Engage Integration. All Multichannel document fields are shared fields. Although these fields apply primarily to Presentation and Slide document types, you can add the following document fields to any document type:
| Field | Document Type | Function |
|---|---|---|
| Publish for Veeva CRM (Portals) | Presentation, Slide | Indicates whether the document is valid content to publish to CLM |
| Publish for Veeva CRM (CoBrowse) | Presentation | Indicates if the document will be used as CoBrowse content; if so, the Publish for Veeva CRM (Portals) field should also be set to Yes. |
| CRM Manually Assigned Content Template | Presentation, Slide | Indicates one or more CRM Message Templates available to CRM users when sending presentations as web links |
| Website | Presentation | Specifies the site where Vault should publish the Engage content |
| Related Content Display Order | Presentation | Sets the display order for related content in the Engage player |
| Presentation ID | Presentation | External ID of the presentation binder, used for “gotoSlide” references |
| CRM Media Type | Slide | Indicates the type of document content: image, HTML, PDF, PPTX, or video |
| HTML File Name | Slide | Indicates the file name of the index file in HTML content only You only need to populate this field if the main HTML page in the ZIP is not named index.html. Vault does not require or validate this field, but the Engage player will not display the HTML if the field value is not correct. |
| HTML Height | Slide | Indicates the appropriate height dimension for the media in the Engage player (HTML only) |
| HTML Width | Slide | Indicates the appropriate width dimension for the media in the Engage player (HTML only) |
| Key Message | Slide | Corresponds to the Key Message entity in Veeva CRM and creates a link between the slide document in Vault and the key message in CRM |
| Shared Resource | Slide | Indicates if the document will be used as a “Shared Resource” in CLM or Engage |
| Searchable in WeChat | Presentation | Determine if this content should be searchable in WeChat. |
| Publish for Veeva CRM (WeChat) | Presentation | Determine if this content is specific to WeChat. |
Note that Vault does not support Security Overrides on any document fields used for Engage Integration.
About Slide & Presentation Document Types
Vault uses two document types for Engage content: Multichannel Slide for documents representing individual slides and Multichannel Presentation for binders representing a presentation. Depending on when your Vault enabled Engage Integration, the labels for these document types may be different:
- Multichannel Slide may be Slide
- Multichannel Presentation may be Presentation
Admins can also rename these document types if needed, so your Vault may not use any of these labels.This difference only affects the names and labels for the document types. It does not affect how you use Engage Integration.