With every release, we update the data model to better support evolving needs and new feature functionality. With this release, we’ve added the following components to the Commercial data model. These data model updates are automatically included in all Commercial Vaults, but Admins must make configuration changes to make them available. For information on feature functionality, see What’s New in 21R3.

With this release, we’ve added the following components to the Commercial data model to support new features:

  • Added new object Positive/Negative List
  • Added the following shared document fields:
    • Add to Positive/Negative List
    • Delivery to HCPs
    • Positive/Negative List Name
    • Promotional Material Document Name
    • Promotional Material Document Description
    • Promotional Material ID

The following component was added to PromoMats & MedComms Vaults to support the Document Level Rendition Type Selector for Single Doc Publishing for CLM Content feature:

  • Added new shared document field CRM Rendition Override (crm_rendition_override_v)

The following components were added to PromoMats & MedComms Vaults to support the CLM Metadata Enhancements for Medical Affairs feature:

  • Added new shared document field CRM Searchable Description (crm_searchable_description_v)
  • Made the shared document field Website (website__v) editable
  • Added the following fields to the Multichannel Presentation document type:
    • CRM Org (crm_org__v)
    • CRM Product (crm_product__v)
    • CRM Searchable Description (crm_searchable_description_v)
  • Added the following fields to the Multichannel Slide document type:
    • CRM Org (crm_org__v)
    • CRM Product (crm_product__v)
    • CRM Directory (crm_directory__v)
    • CRM Searchable Keywords (crm_keyword__v)
    • CRM Searchable Description (crm_searchable_description_v)
  • Made the following inactive document fields active:
    • CRM Org (crm_org__v)
    • CRM Product (crm_product__v)
    • CRM Searchable Description (crm_searchable_description_v)
    • CRM Searchable Keywords (crm_keyword__v)
  • Added the field dependency rule: Within document type Multichannel Presentation, if Publish for Veeva CRM (CLM) equals Yes, fields CRM OrgCRM ProductCRM DirectoryCRM Searchable Description, and CRM Searchable Keywords are required
  • Added the field dependency rule: Within document type Multichannel Slide, if Publish for Veeva CRM (CLM) equals Yes, fields CRM OrgCRM ProductCRM DirectoryCRM Searchable Description, and CRM Searchable Keywords are required

The following components were added to MedComms Vaults to support the Automated Email Intake for Medical Inquiries feature:

  • Added the following new fields on the Case Request (case_request__v) object:
    • Recipient Email Address (email_recipient_address__v)
    • Recipient Email Username (email_recipient_username__v)
    • From (email_from__v)
    • To (email_to__v)
    • CC (email_cc__v)
    • Subject (email_subject__v)
    • Attachments (email_attachments__v)
    • Body (email_body__v)
    • Body Text (email_body_text__v)
    • Sent (email_sent__v)
    • Received (email_received__v)
    • Message ID (email_message_id__v)
    • Email Forwarding Address (email_forwarding_address__v)
  • Added value Email (email__v) to the Source (source__v) picklist
  • Added object type Email Forwarding Email Address (email_forwarding_address__v) to the Person (person__sys) object
  • Added field Email Message ID (email_message_id__v) to the Case Response Email (case_response_email__v) object
  • Added the following notifications:
    • Medical Inquiry – Forward Email (medical_inquiry_forward_email__v)
    • Medical Inquiry – Email Received (medical_inquiry_email_received__v)
  • Added state Email Forwarded (email_forwarded_state__v) to the Case Request object lifecycle
  • Added the following states to the Case (case_lifecycle__v) object lifecycle:
    • Email Forwarded (email_forwarded_state__v)
    • New Follow-Up Email (new_follow_up_email_state__v)
  • Added email processor Medical Inquiry Email Processor (medical_inquiry_email_processor__v)