22R1.3 Functionality Guide

The Functionality Guide is intended for Sales Operations, Business Administrators, System Integrators, and others responsible for making decisions about what features are needed for end users to be successful and deciding which features work together with existing customer configurations.

Approved Email

Event Speaker and Event Catalog Objects in Relationship Tokens

Content creators can reference relationships between two disconnected objects, EM_Speaker_vod and EM_Catalog_vod, using the relationship Approved Email token. This enables greater flexibility when creating Approved Email content to use in Events Management.

For example, Alice Adams wants to edit an Approved Email template used as an invitation to events to reference the name of the event’s topic per the associated EM_Catalog_vod record. The Topic_vod field on the EM_Event_vod object references the EM_Catalog_vod object, so she adds the following token to the email template to reference the topic name:

{{EM_Event_vod__c.Topic_vod__r.Name_vod__c}}

To configure this feature, add the appropriate {{ObjectAPIName.RelationshipName.FieldAPIName}} token to the appropriate Approved Email Templates.

Engage

Supporting Engage Sandbox Releases

Engage features are available in sandbox orgs before production releases to allow admins to test upcoming Engage functionality.

To use the new Engage Sandbox, create a support ticket with the list of CRM sandbox orgs to link to the Engage Sandbox. Admins can assign Engage licenses to test users once the sandbox org is linked to the Engage Sandbox and existing Engage groups are recreated.

Previously created meetings and groups are not available once the org is linked to the Engage sandbox. Existing Engage groups must be recreated.

When the org is linked to the Engage sandbox, existing Engage data is maintained. However, Engage Post-Processing errors may occur when processing data prior to linking the sandbox. Veeva recommends removing meeting data prior to linking the sandbox when using Engage Post Processing in the sandbox org.

Refreshing sandbox orgs relinks the org to Engage production. Production CRM orgs cannot be linked to the Engage sandbox.

Prerequisites

  • Orgs and clients must upgrade to 221.3.200 or later in order to connect to the Engage sandbox

Using the Engage Sandbox

The Engage sandbox is compatible with all attendee apps, as well as the Engage Speaker App, without additional configuration or installation. Attendees joining Engage meetings via an attendee link generated from an org linked to the Engage sandbox automatically have access to sandbox functionality. Sandbox links contain sbx as part of the URL.

If the App Store version of CRM is installed, users must use the TestFlight version of the application to test sandbox functionality.

Events Management

Integrating Time Zones with Cvent

To localize all date/time values when creating Meeting Requests in Cvent, admins can map the Time_Zone_vod field on the EM_Event_vod object in CRM to the Event Timezone question on the Meeting Request form in Cvent. This causes date/time field values in Meeting Requests in Cvent to localize based on the selected time zone in CRM.

For example, Sarah Jones creates an event in Los Angeles with a start time of 11 am. During the event creation process, she selects the event’s time zone. When Sarah’s event is synced with Cvent, the event’s time zone is used to localize all date/time values on the Meeting Request created or updated by the sync.

Prerequisites

Time Zones in Meeting Requests in Cvent

When an event is created in CRM with the Time_Zone_vod field populated, all date/time values in the resulting Meeting Request in Cvent are localized based on the time zone.

For example, if an event is created in CRM with a start time of 2022-02-19T18:00:00+0000 and a Time_Zone_vod of America/Los_Angeles, the resulting Meeting Request in Cvent has a localized start time of 2022-19-02T11:00:00.

MCCP

MCCP Filtering by Product-Specific Metrics

To make it easier for users to filter accounts that are MCCP targets, MCCP filters only display values that are defined for the selected product instead of displaying all values for the metric. This feature is available from locations that support filtering MCCP target accounts, for example, My Schedule and the Targets and Edit Goals tabs in My Plan.

For example, Sarah Jones is a sales rep at Verteo Biopharma. She wants to find all MCCP targets where the Behavior metric equals Pioneer for the product Cholecap. From the MCCP Targets screen, Sarah selects the Filter icon and selects Cholecap from the Product field. She then selects Behavior and Equals from the Filter Criteria list, and only the three Behavior values configured for Cholecap display in the list.

This feature does not require configuration.

Using MCCP Filtering by Product-Specific Metrics

When users select a Product, the filter options are limited to display only values that apply to that Product. The filter values are listed in alphabetical order. If the organization is configured to use active values to reduce the number of picklist options, the MCCP filters only display active values from the value list on the MCCP Target object for pull-in picklist fields from the Account, Address, and TSF objects.

The list of values available in the product metric filters is determined based on whether metrics are configured for the organization.

  • Without product-specific metric values metrics configured - MCCP filters display values defined in the product metrics pull-through field from the MCCP Product object.
  • Product-specific metric values configured - MCCP filters display values that exist in both product metrics pull-through fields on the MCCP Product object and Available Values fields of the Metric Configuration object. Any values that exist only in the MCCP Product object or Metric Configuration object do not display.

The list of values available in the filters for pull-through fields from Account, Address and TSF objects on Targets and Edit Goals tabs in My Plan are now taken from the values defined in the MCCP Target object.

The values in the source and target lists are typically consistent.

For details on filtering accounts that are MCCP targets, see Working with the MCCP Interface.