OCE Connector

Overview

The Vodori OCE Connector is a powerful add-on that enables your team to seamlessly sync MLR-approved CLM (Closed Loop Marketing) assets and email templates directly from Vodori to IQVIA’s Omnichannel Engagement (OCE) platform.

This connector eliminates manual content transfer and ensures your commercial teams can engage confidently with customers, knowing that CLM presentations and re-triggered emails are approved, compliant, and up to date.

This article talks about:

• Supported Content

• Supported Use Cases

• Content Availability

• Emails

• For CLM Assets (PDF)

• For CLM Assets (ZIP)

• Other Notable Information 

Supported Content

The Connector is designed to support the formats accepted by the OCE API — CLMs in PDF or ZIP format and Email templates in ZIP format. The ZIP packages contain HTML.

CLM assets typically consist of interactive, presentation-style content designed for use in field engagement scenarios within IQVIA OCE. These must be packaged and formatted according to OCE’s CLM requirements. 

Email templates are also supported and must follow specific HTML formatting defined by OCE packaged as a ZIP. Customers may route flat PDFs of email templates for MLR approval or leverage Vodori's rendition capabilities before proceeding with the production of the HTML format. However, the final version intended for OCE must be in the expected HTML (ZIP) format to work as a rep-triggered email in OCE.

Supported Use Cases

Integration Details

Content Availability 

A document in Vodori must meet certain criteria to be eligible for OCE Personal sync. These criteria are configurable by each customer, so they may differ slightly in your environment; however, the list below is provided as an illustrative, directional example. Consider an “and” operator between each requirement.

Emails

Required Vodori fields that sync:

• OCE display name (input by user)
• Email subject (input by user)
• Unique ID (system-generated)

Optional Vodori fields that sync: 

• Approved for Use date
• Expiration date (recommended)
• Description

The following fields are not managed in Vodori and must be input into OCE for each email template: 

For CLM Assets (PDF)

Required Vodori fields that sync:

• OCE display name (input by user)
• Unique ID (system-generated)

Optional Vodori fields that sync: 

• Approved for Use date - Will populate Presentation Start Date in OCE
• Expiration date (recommended) - Will populate Presentation End Date in OCE, except when presentation is force expired in Vodori

The following fields are not managed in Vodori and must be input into OCE for each CLM Asset: 

Note: Each page in the PDF creates an individual sequence in OCE, named by the page number (default OCE functionality)

For CLM Assets (ZIP)

Required Vodori fields that sync:

• OCE display name (input by user) - Will populate Presentation Name
• Unique ID (system-generated)

Optional Vodori fields that sync: 

• Approved for Use date - Will populate Presentation Start Date in OCE
• Expiration date (recommended) - Will populate Presentation End Date in OCE, except when presentation is force expired in Vodori

The following fields are not managed in Vodori and must be input into OCE for each CLM Asset: 

Other Notable Information 

• Only content that has reached the Approved for Use state in Vodori will be eligible to sync to OCE Personal. Scheduled content in Vodori will not sync to OCE Personal.
• The default refresh interval is once per 24 hours at 2:00 AM UTC (8:00 PM CST), however this is configurable and may be different for your organization's configuration of the connector.
• Sync errors are reported to the OCE Admin through a report in OCE Personal, that can be scheduled to be sent at a periodic interval via email.
• If an Expiration date has synced to OCE, OCE Personal's native functionality to unpublish content when its Expiration Date is reached may happen to content before the next scheduled sync date. The solution will attempt to unpublish the document if it has not already been unpublished by OCE Personal.
• The connector does not provide fallback behavior for missing or invalid content properties. If a piece of content is missing a metadata value that is required by OCE Personal, or if the value is invalid for the field, an error will be logged in the sync process and the content will not be synced to OCE Personal.
• There is a 50 MB file size limit on email templates and a 500MB file size limit on CLM presentations imported via the OCE API. Any files uploaded into Vodori larger than the 50MB or 500MB limit are not eligible to be synced to OCE Personal. Additionally, there is a 200 page size limit on PDF CLM presentations imported via the OCE API.
• In order to withdraw content from OCE Personal, the Connnector will set the end date in OCE to the current date. OCE Personal will mark the content as 'Unavailable' after the end date has passed.
• ZIP CLM content cannot be withdrawn from OCE on the same day that it was approved because OCE Personal requires that the end date is later than the start date.
• Files uploaded into Vodori cannot contain non latin-1 characters in their filenames, otherwise they will fail to sync to OCE Personal.  Example: ẞ.
• The OCE Connector supports sending full presentations from Vodori to OCE Personal. Sending only sequences is not currently supported.
• The OCE Connector cannot force expire a sequence from OCE Personal; it can only force expire presentations. For this reason it is not recommended to use the same sequence in multiple presentations unless routed through Vodori as individual presentations.
• Deleting content in OCE Personal that was synced from Vodori may result in irrevocable data synchronization issues and errors and should be avoided.
• You cannot switch a Document subtype between CLM and Email in Vodori between versions. Once a document has attempted to sync to OCE through the Connector, it must remain the initial Document subtype as defined in Vodori.