22R2.2 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.

Engage

Sending Confirmation Emails for Accepted Meeting Requests

To notify HCPs about accepted meeting requests, confirmation emails are automatically sent to HCPs when a user accepts a meeting request in My Schedule. Customers can also define an optional company logo in the confirmation email. To do this, populate the COMPANY_LOGO_vod Engage Link setting with an externally hosted URL to the appropriate image.

For example, Dr. Clinton Ackerman submits a meeting request with Sarah Jones. Later, Sarah reviews the meeting request in My Schedule and selects Accept. Dr. Ackerman automatically receives a confirmation email from Sarah that contains the time, date, and meeting type.

This feature does not require configuration.

Automatically Sending Confirmation Emails

When a user accepts a meeting request in My Schedule, a confirmation email is sent to the account based on the Invitee_Email_vod field on the corresponding Meeting_Request_vod record. This email details the meeting type, date and time, and participants.

If the Meeting_Type_vod or Phone_vod fields are not populated in the Meeting_Request_vod record, they do not display in the email.

This email is supported in all of Veeva CRM’s supported languages and uses the Invitee_Locale_vod field from the corresponding meeting request to determine the language of the email.

Additionally, an .ICS file is attached to the email the recipient can use to add the scheduled meeting to their calendar.

Events Management

Event Session and Event Speaker Tokens

To better communicate the agenda of large-scale events, content creators can add tokens to Approved Emails sent from Events Management that render as tables listing the event’s sessions and speakers. This provides a better overview of what the event is about, enabling attendees to better plan for the event.

For example, Alice Adams is a content creator who wants email invitations to large-scale events to include tables listing the event’s speakers and sessions. She edits the appropriate template and adds the {{EventSession}} and {{EventSpeaker}} tokens to the template. She then edits each token to display the appropriate columns, as well as add custom styling for each table.

Later, Sarah Jones organizes a large scale event with several associated sessions and speakers. When she previews the invitation prior to sending it to her attendees, she views the rendered tables listing her event’s sessions and speakers.

Adding the Event Sessions Table to Approved Email Content

To add the Event Sessions table for Approved Email content, add the {{EventSession}} token to the appropriate Approved Email Templates used as invitations for Events. If you are using Vault to create the email template, this token can be added via the BEE Editor.

The Sessions Table token has the following parameters, all of which can be used together to create specific and relevant tables:

  • tableHeader – Defines the table’s header
  • fields – Defines the columns of the table. At least one field must be referenced for the table to render.
  • sort – Defines the field to sort EM_Event_Session_vod records by, as well as if records should sort in ascending or descending order

Line breaks and spaces are not supported in this token.

The tableHeader Parameter

Content creators can specify the table’s title using the tableHeader= parameter.

For example, {{EventSession[fields=Session_Title_vod__c;tableHeader=Sessions]}} would render the table with a header of Sessions.

The tableHeader parameter is not translated.

The fields Parameter

Use the token’s [fields=Field1APIName, Field2APIName] parameter to define a comma-separated list of EM_Event_Session_vod fields to display as columns of the table.

At least one field must be added to the token in order for the table to render.

For example, {{EventSession[fields=Session_Title_vod__c, Description__c]}} renders the table with two columns representing the Session_Title_vod and Description__c fields.

Content creators can specify the format of Date, Time, or Date/Time fields.

The sort Parameter

By default, EM_Event_Session_vod records sort in the table based on their Start_Time_vod__c field values.

Content creators can use the sort= parameter to specify a different field and sort order for the table.

For example, {{EventSession[fields=Session_Title_vod__c, Description__c;sort=Session_Title_vod__c, asc]}} sorts the list in ascending order based on the Session_Title_vod field values.

Customizing Styles for the Event Sessions Table

Content creators can customize the styling of the Event Session table by adding the following CSS class selectors to the <style> tag of the Email Template:

  • .eventsession – Controls the style of the overall table
  • .eventsession th – Controls the style of the table header row
  • .eventsession tr – Controls the style of table rows
  • .eventsession td – Controls the style of table cell content

Adding the Event Speakers Table to Approved Email Content

To add the Event Speakers table to Approved Email content, add the {{EventSpeaker}} token to the appropriate Approved Email Templates used as invitations for Events. If you are using Vault to create the email template, this token can be added via the BEE Editor.

The Speaker Table token has the following parameters, all of which can be used together to create specific and relevant tables:

  • tableHeader – Defines the table’s header
  • fields – Defines the columns of the table. At least one field must be referenced for the table to render.
  • status – Filters the list of Event Speakers based on their Status_vod fields
  • sort – Defines the field to sort EM_Event_Speaker_vod records by, as well as if records should sort in ascending or descending order

Line breaks and spaces are not supported in this token.

The tableHeader Parameter

Content creators can also specify the table’s title using the tableHeader= parameter.

For example, {{EventSpeaker[fields=Speaker_Formatted_Name_vod__c;tableHeader=Speakers]}} would render the table with a header of Speakers.

The tableHeader parameter is not translated.

The fields Parameter

Use the token’s [fields=Field1APIName, Field2APIName] parameter to define a comma-separated list of EM_Event_Speaker_vod fields to display as columns of the table.

At least one field must be added to the token in order for the table to render.

For example, {{EventSpeaker[fields=Speaker_Formatted_Name_vod__c, EM_Speaker_vod__r.Speaker_Biography__c]}} renders the table with columns representing the Speaker_Formatted_Name_vod field, as well as the custom Speaker_Biography__c field referenced from the EM_Speaker_vod field.

Up to five levels of relationship references are supported. For example, EM_Event_Speaker_vod__c.EM_Speaker_vod__r.Account_vod__r.Primary_Parent_vod__r.Formatted_Name_vod__c

Content creators can specify the format of Date, Time, or Date/Time fields.

The status Parameter

Content creators can filter the list of Event Speakers based on their Status_vod fields using the status= parameter.

For example, {{EventSpeaker[fields=Speaker_Formatted_Name_vod__c, Speaker_Biography__c;status=Approved_vod, Invited_vod]}} filters the list of Event Speakers to only display speakers with a Status_vod field of Approved_vod or Invited_vod.

The sort Parameter

By default, EM_Event_Speaker_vod records sort in the table based on their First_Name_vod fields. Content creators can use the sort= parameter to specify a different field and sort order to use instead.

For example, {{EventSpeaker[fields=Speaker_Formatted_Name_vod__c, EM_Speaker_vod__r.Speaker_Biography__c;sort=Speaker_Formatted_Name_vod__c, asc]}} sorts the list in ascending order based on the Speaker_Formatted_Name_vod field.

Customizing Styles for the Event Speakers Table

Content creators can customize the styling of the Event Speakers table by adding the following CSS class selectors to the <style> tag of the Email Template:

  • .eventspeaker – Controls the style of the overall table
  • .eventspeaker th – Controls the style of the table header row
  • .eventspeaker tr – Controls the style of table rows
  • .eventspeaker td – Controls the style of table cell content