18r3 release notes - docs.veevacrm.comdocs.veevacrm.com/releasenotes/veeva crm 18r3 release...

CRM 18R3 Release Notes

November 2018

Veeva CRM 18R3 Release Notes

Veeva Systems Confidential Information Copyright © Veeva Systems 2007 - 2018

(For use only by licensed Customers of Veeva Systems)

2

Contents

Contents .......................................................................................................................................... 2

Figures ............................................................................................................................................. 3

Tables .............................................................................................................................................. 4

Introduction .................................................................................................................................... 5

Highlights of this Release ................................................................................................................ 5

User Visible Changes ....................................................................................................................... 5

Multichannel ............................................................................................................................ 6

Engage Meetings ..................................................................................................................... 6

New in Veeva CRM 18R3................................................................................................................. 8

Online Documentation .................................................................................................................... 8

Note Styles ............................................................................................................................... 8

Feedback .................................................................................................................................. 8

Advanced Searching in the Online Help .................................................................................. 9

Core CRM ...................................................................................................................................... 10

Accounts .................................................................................................................................... 10

Adding Action Items for KAMs .............................................................................................. 10

Account Plan Sharing Using Account Plan Hierarchy ............................................................ 13

Account Plan Progress Calculation Using Account Plan Hierarchy ....................................... 14

Supporting Custom Objects in the Account Plan Hierarchy .................................................. 14

Call Reporting ............................................................................................................................ 16

Call Pull-In Fields .................................................................................................................... 16

Inventory Monitoring ................................................................................................................ 19

Inventory Monitoring Product Groups .................................................................................. 19

Medical Events .......................................................................................................................... 21

Child Accounts in Medical Events .......................................................................................... 21

Medical Inquiries ....................................................................................................................... 22

Medical Inquiry Fulfillment Response Method ..................................................................... 22

Use ......................................................................................................................................... 23

Order Management ................................................................................................................... 24

Viewing IM information in an Order ..................................................................................... 24

Surveys ...................................................................................................................................... 26

Branching Surveys.................................................................................................................. 26

Use ......................................................................................................................................... 28

Events Management ..................................................................................................................... 29

Bulk-Add Event Attendees ..................................................................................................... 29

Country-specific Sign-In Sheet Disclaimer ............................................................................. 30

OpenData Integration for Attendee Reconciliation .............................................................. 33

Vault Integration for Event Materials .................................................................................... 34

Multichannel ................................................................................................................................. 36

Approved Email ......................................................................................................................... 36

Approved Email Conent Search Enhancements .................................................................... 36

Stamping the Email Source in Approved Email ..................................................................... 37




3

CLM ............................................................................................................................................ 38

Mapping Vault Object Reference Fields ................................................................................ 38

Presentation Labels in CLM ................................................................................................... 39

Enhancing Single-Doc Publishing ........................................................................................... 41

Display By View for Grouping Presentations ......................................................................... 42

Augmented Reality in CLM .................................................................................................... 42

AR Content Creation .............................................................................................................. 47

Veeva Now ................................................................................................................................ 54

Consent Capture ........................................................................................................................ 55

Capturing Consent to Track Email Activity ............................................................................ 55

Opt-Out Specific Disclaimer Text in Consent Capture ........................................................... 58

Engage ....................................................................................................................................... 59

Engage Webinar Recording ................................................................................................... 59

MyInsights ..................................................................................................................................... 61

Medical Dashboard ................................................................................................................ 61

MyInsights Smart Linking Enhancement ............................................................................... 64

Scheduling and Planning ............................................................................................................... 65

Schedule Color Changes ........................................................................................................ 65

Parity ............................................................................................................................................. 66

Push Notifications .................................................................................................................. 66

Accounts .................................................................................................................................... 66

Advanced Coaching Reports .................................................................................................. 66

Call Reporting ............................................................................................................................ 66

Call ......................................................................................................................................... 66

Events Management ................................................................................................................. 67

Scheduling and Planning ........................................................................................................... 67

MCCP ..................................................................................................................................... 67

MyInsights ................................................................................................................................. 67

Network ..................................................................................................................................... 67

Creating Unverified Records .................................................................................................. 67

Surveys ...................................................................................................................................... 67

Surveys for iPhone ................................................................................................................. 67

Revision History ............................................................................................................................ 69

Appendix A: New Objects ............................................................................................................. 70

Appendix B: New Fields ................................................................................................................ 70

Figures

Figure 1: Note Style Update ............................................................................................................ 8

Figure 2: Feedback in CRM Online Help.......................................................................................... 9

Figure 3: Advanced Search Online Help ........................................................................................ 10

Figure 4: Actions Items for KAMS ................................................................................................. 13




4

Figure 5: Inventory Monitoring Product Groups .......................................................................... 20

Figure 6: Medical Inquiry Fulfillment Response ........................................................................... 23

Figure 7: Viewing IM in an Order .................................................................................................. 24

Figure 8: Survey Branching Example ............................................................................................. 26

Figure 9: Branching Surveys .......................................................................................................... 28

Figure 10: Bulk-Add Event Attendees ........................................................................................... 30

Figure 11: Sign_in Sheet Disclaimer .............................................................................................. 32

Figure 12: Sign_In Shet ................................................................................................................. 32

Figure 13: Vault Integration for EM .............................................................................................. 35

Figure 14: Event Detail page ......................................................................................................... 35

Figure 15: External Vault View ...................................................................................................... 36

Figure 16: AE Advanced Search .................................................................................................... 37

Figure 17: AE Advanced Search Results ........................................................................................ 37

Figure 18: Mapping Vault Object Reference Fields ...................................................................... 38

Figure 19: Presentation Labels in CLM.......................................................................................... 40

Figure 20: Adding Presentation Lables ......................................................................................... 40

Figure 21: Filtering Presentations ................................................................................................. 41

Figure 22: Display By View ............................................................................................................ 42

Figure 23: Augmented Reality exaple ........................................................................................... 44

Figure 24: Displaying AR................................................................................................................ 45

Figure 25: Resetting the AR Scene ................................................................................................ 46

Figure 26: Slider Bar in AR ............................................................................................................. 46

Figure 27: Previous and Next in AR ............................................................................................... 47

Figure 28: CC Email Activity Tracking Opt Out .............................................................................. 57

Figure 29: CC Email Opt In ............................................................................................................ 57

Figure 30: Opt-Out Disclaimer ...................................................................................................... 59

Figure 31: Medical Dashboard ...................................................................................................... 64

Figure 32: Weekly Calendar Schedule Colors ............................................................................... 65

Figure 33: Color Chart ................................................................................................................... 66

Tables

Table 1: Pull-In Fields Call Reporting ............................................................................................ 18

Table 2: Pull-In Fields Unique Activities ........................................................................................ 18

Table 3: Child Accounts in Medical Events ................................................................................... 21

Table 4: Mapping Vault Object Reference Fields.......................................................................... 39

Table 5: CC Email Activity Tracking FLS ......................................................................................... 56

Table 6: Medical Dashboard ......................................................................................................... 63

Table 7: 18R3 Objects ................................................................................................................... 70

Table 8: 18R3 New Fields .............................................................................................................. 78




5

Introduction

Many new features can be enabled with Veeva CRM 18R3. This document provides a brief explanation of each new feature and updates to existing features.

Highlights of this Release

Veeva CRM 18R3 brings major improvements across the full suite of applications, providing enhancements optimizing the user experience and maximizing productivity.

• Augmented Reality - new CLM content type to present AR content within Veeva CRM

• CLM Labels - allows users to organize CLM content with their own keywords so they can find their content quicker

• New iPhone Capabilities - Unique Activities Calls, Surveys, and more are now available on the iPhone

• KAM Action Items - a more flexible alternative to Call Objectives and Tasks as the most granular level of planning in your Account Plans

• Approved Email Content Search Improvements - provides a more robust searching capability by indicating whether the search terms should be treated as an AND or OR

Detailed instructions for settings required to fully enable these, as well as all the new features in Veeva CRM 18R3, are available later in this document.

User Visible Changes

Users can view the following changes for this release without additional configurations:

General • Push notifications can be hidden from the notification list by swiping left on the notification and

selecting Hide

Call Sampling • Sample lots now sort to display sooner expiring lots first in the list of available lots • Sample lots with a null expiration date display last in the list of available lots on the Online

platform when the ENABLE_EXPIRATION_FILTER_vod Veeva Setting is enabled

Events Management • The Meal_Opt_In_vod field on the EM_Attendee_vod object must now be placed on the proper

page layout in order to display on the Attendee related list signature page. This change makes the Meal Opt-In display behavior on related list signature pages consistent with the behavior on the self-service signature page.

• Email surveys using Approved Email can now select Event Topic templates when the Country_vod field is populated




6

• If an Approved Email Template in Vault has Country and Event Topics populated, but Event Types is blank, the integration only creates topic material records in CRM. Previously, the integration also created Event Rules in this case.

• Check box fields that previously displayed as 1/0 or true/false in the attendee selection screen now display as selected or deselected check boxes

My Tasks

• When selecting Complete, the Complete Task modal displays with a title. The options are now Go Back and Complete.

Sample Management

• iPad users can now search on the mass add sample and promotional items (--masp) user interface using Lot # in addition to Product

Multichannel

Approved Email

• Fields on the Manage Email Addresses page now respect page layout permissions • Users can force the search to only return results containing all of the words by selecting the

Must Include All Key Terms check box. For example, Sarah Jones searches for Efficacy Chol. This result returns Efficacy of Cholecap and Efficacy of Raxxipan. Sarah then selects the Must Include All Key Terms checkbox and searches again. This search only returns Efficacy of Cholecap.

CLM

• The CLM Media library and slide selector screens now scroll vertically and not horizontally • Search now includes thumbnails and the ability to favorite the presentation from the search

results • Media preview now includes a Cancel option • The More Actions button now has a Favorites option for presentations • The Presentation status displays above the presentation thumbnail

Engage Meetings

• A green border surrounds the app to remind the user they are in an active Engage Meeting on the iPad

• CRM Engage App (for CRM Online hosts) now utilizes Chrome CefSharp v65.0.1 as the embedded browser and requires a minimum version of .NET 4.5.2

Surveys • The label of the Search button now displays as Create when creating a survey target

from a Call Report on the iPad platform

• The input fields for survey questions on the iPad platform now follow the Sunrise UI

• If an iPad user scrolls on the Survey Target screen while the keyboard is open, the keyboard automatically closes




7

• User Surveys on the Survey Target home page have a new style that displays the Survey Name more prominently

• When selecting a survey template to create a survey target, if the Survey is expiring within the pre-configured Survey Alert Threshold, the text indicating expiration now displays in red




8

New in Veeva CRM 18R3

The following are available to all licensed users. Instructions to configure these options are discussed in each topic and in the Veeva CRM product documentation.

Windows App

The Windows application now displays Veeva CRM 18R3 next to the icon. This title is being changed as the 18R3 version of the application is the last classic version before the new Sunrise UI release in 19R1. The 19R1 version will have the traditional Veeva CRM title.

Online Documentation

Note Styles

We updated the note styles in the online documentation to represent the content contained in the notes. There are now three levels of notes:

• Note (Blue) – provides additional information

• Caution (Yellow) – An adverse effect may occur, for example a misconfiguration

• Warning (Red) – A critical error may occur, for example, you may lose data

Figure 1: Note Style Update

Feedback

Each topic in the CRM Online Help now displays a Feedback button in the bottom left corner of the page.




9

Select the Feedback button, enter your email address and feedback, then select Submit. The documentation team receives an email containing the link to the page from which you selected the Feedback button. The email also contains the email address entered for future follow-up.

Figure 2: Feedback in CRM Online Help

Advanced Searching in the Online Help The CRM Online Help site now supports advanced search settings to enable users to quickly locate a relevant topic. Advanced searching consists of two components:

• Filtering – Select the Filter icon to limit the list of search results to only display topics belonging to the selected category. Only one filter may be selected at a time.

• Exact Search – Select the Exact Search check box to limit the list of search results to only display topics containing the exact term. For example, if the search term is --cat and exact search is enabled, the search results only display topics with words containing exactly --cat. If exact search is not enabled, the search results also include all topics with words that contain cat (category, catalog, etc).

For example, Alice, an administrator at VerteoBiopharma wants to learn more about the --cat section signal. She is unsure which topic to read but knows the section signal is a part of Call Reporting. She enables an exact search for --cat and limits the search results to only display Call Reporting topics. The search returns two results, allowing the administrator to quickly locate the correct topic.




10

Figure 3: Advanced Search Online Help

Core CRM

ACCOUNTS

Adding Action Items for KAMs

Action items offer a flexible way of planning at a lower level as an alternative to Call Objectives or Salesforce Tasks. They can be included as part of the customer's Account Plan Hierarchy, used in Account Plan sharing, and used in Account Plan progress roll-up calculations. Action Items are adaptable enough to work for companies to having two, three, or four levels in their Account Plans. For example, to achieve the company’s goals at A Center for Dermatology, Mark Mitchell, a KAM, puts together a plan with the following action items:

• Understanding who is the employee in charge of clinical trial approvals at the clinic




11

• Larry Lakes, the MSL, reaching out to whoever that is to educate them about the clinical trial and

• Sarah Jones, the commercial rep, distributing pamphlets to the HCPs at A Center for Dermatology

Configuration

To enable this feature:

1. Ensure Offline Validation Rules are configured if using offline devices. This is required to validate the Start Date is before the Due Date when creating or editing an Action Item.

2. Grant end users Create, Read, and Update permission to the Action_Item_vod object. 3. Grant end users FLS edit permission to all fields on the Action_Item_vod object. 4. Activate the VMOCs associated with the Action_Item_vod object.

Use the following three VMOC WHERE clauses for this feature:

• WHERE ((OwnerId = @@VOD_SF_USER_ID@@) OR (Assignee_vod__c = @@VOD_SF_USER_ID@@))

• WHERE Account_vod__c IN (SELECT Id FROM Account) • WHERE Account_Plan_vod__c IN (Select Id FROM Account_Plan_vod__c)

These VMOCs allow users to retrieve action items they own or are assigned to, action items pertaining to an Account they own, and action items that are part of an Account Plan to which they have visibility, respectively. To use all three VMOCs in conjunction, set the SYNC_CONFIGURATION_MODE_VOD Veeva Setting to 1.

5. Update the Account_Plan_Object_Hierarchy_vod Veeva Setting to use Action Items. The default value for this Veeva Setting is Plan_Tactic_vod__c.Account_Plan_vod__r,Account_Tactic_vod__c.Plan_Tactic_vod__r, Call_Objective_vod__c.Account_Tactic_vod__r. To incorporate Action Items into a hierarchy, add the object to this setting following the example below.

Plan_Tactic_vod__c.Account_Plan_vod__r,Account_Tactic_vod__c.Plan_Tactic_vod__r,Action_Item_vod__c.Account_Tactic_vod__r

This example replaces Call Objectives with Action Items.

The lowest level of the Account Plan Hierarchy can either be Action Items or Call

Objectives, using both at the same time is not supported. This feature only supports org-

level custom settings.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Mobile_Device_Setup/OfflineValidationRules.htm




12

6. Update the HTML Report to a report that uses action items. This step is optional.

The Account Plan Dashboard MyInsights visualization is enabled to display Action Items instead of Call Objectives, depending on which one of these is configured at the bottom level of the Account Plan Hierarchy (as defined in the Account Plan Object Hierarchy Veeva Setting.) You can download and use the out of the box template visualization or update your own custom MyInsights visualization.

7. Update any Export to PowerPoint template to include Action Item tokens. This step is optional.

Use

Action items can are used in many ways, including the following:

• Not assigned to a specific user • Not targeted to a specific account • Targeted to a specific account once an account is determined • Assigned to a specific user to execute on a specific account • Not completed as a part of a call

Once the Status_vod picklist on the action item is set to Complete, the item is stamped automatically with the current date and the user who marked the item complete. The Account Plan Dashboard displays the progress of action items and items that are due soon or are overdue, while also using Smart Linking. This allows end users to navigate to Action Item records from the dashboard.

https://crmhelp.veeva.com/doc/Content/CRM_topics/My_Insights/HTMLReports/HTMLReports.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Accounts/Account_Planning_and_Execution/ExportToPowerPoint.htm




13

Figure 4: Actions Items for KAMS

This feature is available on the Online, iPad, and Windows 8 and 10 platforms.

Account Plan Sharing Using Account Plan Hierarchy

The Account Plan Sharing feature now uses the org-level Account_Plan_Object_Hierarchy_vod Veeva Setting and shares records with team members based on the defined hierarchy. For example, an Account Plan Hierarchy might be defined with a model where an Account Plan consists of several Account Tactics with multiple Action Items linked to them. This is represented with the following value in the org-level Account_Plan_Object_Hierarchy_vod custom setting: Account_Tactic_vod__c.Account_Plan_vod__r,Action_Item_vod__c.Account_Tactic_vod__r

In this case, the Share With field drives record access for the Account Plan, Account Tactic, and Action Item for those end users who are team members on the Account Plan with a particular role applying to the Share With values. This feature also allows custom objects to be added to the hierarchy and considered when calculating sharing.

This feature is available on the Online, and if shared, available on the iPad and Windows 8 and 10 platforms.




14

Account Plan Progress Calculation Using Account Plan Hierarchy

Account Plan Progress calculations can now be performed by using a new Veeva batch class instead of instantly executed triggers. Any progress calculation that already exists in triggers and updates existing fields is moved to the batch class. Administrators need to schedule the VeevaRollupsSchedulingWrapper batch class to run according to the desired frequency and update the progress for each level in the Account Plan Hierarchy (as defined by the org-level Account_Plan_Object_Hierarchy_vod Veeva Setting). This feature also allows custom objects to be added to the hierarchy and considered when calculating progress. Progress Calculation Logic:

• Progress at the first level (for example, the Account Plan level) is determined by counting the number of completed records at the second level (defined by the first object in the comma-delimited list of the hierarchy Veeva Setting) and dividing that by the total number of records (for example, complete, incomplete, etc.) at the second level

• Progress at the second level (for example, the level immediately below the Account Plan, defined by the first object in the comma-delimited list of the hierarchy Veeva Setting) is determined by counting the number of completed records at the third level (defined by the second object in the comma-delimited list of the hierarchy Veeva Setting) and dividing that by the total number of records (for example, complete, incomplete, etc.) at the third level

• Progress at the third level (defined by the second object in the comma-delimited list of the hierarchy Veeva Setting) is determined by counting the number of completed records at the fourth level (defined by the third object in the comma-delimited list of the hierarchy Veeva Setting) and dividing that by the total number of records (for example, , complete, incomplete, etc.) at the fourth level

• Progress based on Call Objectives is determined based on the Completed Boolean flag (Completed_vod = TRUE)

• Progress based on objects other than Call Objectives is calculated using the Status picklist (Status_vod = Completed_vod)


Supporting Custom Objects in the Account Plan Hierarchy The Account Plan Hierarchy setting now supports custom objects in the hierarchy. This also enables Account Plan Sharing, Progress Calculation, and the Export to PPT features to consider and make use of any custom defined object along with Veeva objects. The following are key considerations and restrictions for defining the hierarchy:




15

• The hierarchy is defined using the org-level Account_Plan_Object_Hierarchy_vod

custom setting • The feature only supports org-level custom settings • The top-most hierarchy level is Account Plan • The bottom-most hierarchy level is either Call Objective or Action Item • The first object in the comma-delimited list (if defined) corresponds to the second level

of the hierarchy (for example, the level immediately below the Account Plan itself) • The second object in the comma-delimited list (if defined) corresponds to the third level

of the hierarchy • The third object in the comma-delimited list (if defined) corresponds to the fourth level

of the hierarchy • Progress displays in all levels of the Account Plan Object Hierarchy, from the top

(Account Plan) level to the lowest or most granular level of planning • Each level is a rollup of the preceding level

For example, an Account Plan consists of several Account Tactics with multiple Action Items linked to them. This is represented with the following value in the org-level Account_Plan_Object_Hierarchy_vod Veeva Setting: Account_Tactic_vod__c.Account_Plan_vod__r,Action_Item_vod__c.Account_Tactic_vod__r

In this example, Progress on the Account Tactic level displays based on the Status of Action Items while Progress on the Account Plan level displays based on the Status of Account Tactics.

Configuration

To add a custom object to the Account Plan Hierarchy and include it in record sharing and progress rollup calculations:

1. Create a custom object. There are no restrictions on the object name. 2. Create a lookup to the Account_Plan_vod object. There are no restrictions on the field

name. 3. Create the Share With field with FLS edit permission for the user who is responsible for

setting the values and appropriate FLS permission for end users. This step is only for first-level objects immediately below the Account Plan in the hierarchy).

• Field Name - Share_With_vod • Data Type - Picklist • Picklist Values - Sales_vod, Medical_vod, Market_Access_vod

4. Create an Apex Sharing Reason with the name Veeva_Account_Plan_Sharing_vod.




16

5. Create a trigger and a handler Apex Class, following VeevaPlanTacticTrigger and VeevaPlanTacticTriggerHandler used for Plan_Tactic_vod as an example. This enables dynamic sharing of records for the custom object.

• Apex Class - Create the Apex class using any preferred naming convention that

extends VeevaAccountPlanSharingTriggerHandler by following VeevaPlanTacticTriggerHandler and replace Plan_Tactic_vod__c with the API Name of the custom object

• Trigger - Create the trigger using any preferred naming convention by following VeevaPlanTacticTrigger as the reference and replace Plan_Tactic_vod__c with the API Name of the custom object

6. Create the Status field with FLS edit permission for the user who scheduled the batch class, and appropriate FLS for end users:

• Field Name - Status_vod • Data Type - Picklist • Picklist Values - Completed_vod, Pending_vod

7. Create the Progress field with FLS edit permission for the user who scheduled the batch

class and appropriate FLS permission for end users:

• Field Name - Progress_vod • Data Type - Percent(18,0)

8. Add the custom object to the desired level of the hierarchy in the org-level Account Plan

Object Hierarchy Veeva Setting. The object must be after the Account Plan and before the lowest level of the hierarchy.

9. Create appropriate VMOCs for the custom object for offline devices. This feature is available on the Online, iPad, and Windows 8 and 10 platforms.

CALL REPORTING

Call Pull-In Fields

Administrators can now create custom pull-in fields on the Call2_vod object to display information from associated objects. This feature also streamlines the Call Reporting process by creating and configuring fields that automatically populating fields with the relevant information, so users do not have to manually input the information. For example, Sarah Jones records a call with Clinton Ackerman, a non-prescriber. Sarah’s company requires any call logged against a non-prescriber must also have an associated prescriber. Sarah’s org is configured so associated prescriber information is stored on the account record as an account lookup. Tonja Holma is the associated prescriber for Clinton

https://crmhelp.veeva.com/doc/Content/CRM_topics/General/Sync/VMOCs.htm

17

Ackerman. Sarah’s administrator creates a custom pull-in field on the Call Report to automatically display Tonja Holma as the associated prescriber in the call with Clinton Ackerman.

Configuration

To create a new custom pull-in field on the Call2_vod object:

1. Create a new Call2_vod field using the format zvod_<Object Name>_<Field Name> in the Field Name and API Name fields:

• Replace <Object Name> with one of the following supported objects using the appropriate abbreviation:

• NOTE: Syntax is important and must be configured as detailed below:

o ACC – Pulls in the value from the Account record matching the Account_vod field on the Call2_vod record

o ADP – Pulls in the value from the Address_vod record matching the Parent_Address_vod field on the Call2_vod record

o ADS – Pulls in the value from the Address_vod record matching the Ship_To_Address_vod field on the Call2_vod record

o TSF – Pulls in the value from the TSF_vod record where the Account_vod field and the Territory_vod field matches the fields on the Call2_vod record

• Replace <Field Name> with the appropriate field API name from the source object For example, the custom pull-in field zvod_TSF_Associated_Prescriber_vod displays the Associated_Prescriber_vod field from the appropriate TSF_vod record associated with the Account.

Field names cannot be longer than 40 characters.

2. Select the appropriate Data Type. The Data Type and length must match the source

field. Supported Data Types are:

Check box Currency Date Date/Time

Email Number Percent Phone

Picklist Text TextArea Lookup

If the Data Type is either Picklist or Lookup, all available values must match the source

field.




18

3. Grant all users FLS edit permission for the new field. 4. Place the new field on the appropriate Call2_vod object page layout either as editable

or as read-only (Optional). If the pull-in field is editable on the page layout, users can override the values before saving the call report.

Custom pull-in fields populate with the associated information even if the field is not on the

Call2_vod page layout.

Custom pull-in fields are only supported on calls made against an account.

Supported Pull-In Fields per Call Layout Section

Layout Section Supported Objects on an Individual Call Supported Objects on Group Call

Call Header • ACC • ADP / ADS • TSF

• ACC • ADP • TSF

--asf section signal • When using --paa • ACC • TSF

• ACC • TSF

Table 1: Pull-In Fields Call Reporting

Supported Pull-In Fields for Unique Activities Calls

Field Type Supported Objects

Layout Section

Parent and Child Fields ACC TSF

• Call Header – Editable • UA – Editable, Hidden on Header • --asf section signal – Editable,

Hidden on Header

Parent Fields ADP • Header – Editable • UA – Read Only

Child Fields (Unique_Person_Fields_vod)

ADS • Header – Hidden • UA – Editable, Hidden on Header

Table 2: Pull-In Fields Unique Activities

If the address or territory information on the call is changed before saving, the associated pull-

in information refreshes accordingly.




19

This feature is supported on the Online, iPad, and Windows 8 and 10 platforms.

INVENTORY MONITORING Inventory Monitoring Product Groups

Users can now use Product Groups during their Inventory Monitoring activities, for example assessing product presence or stock levels. Product groups are an additional level of hierarchy in the product catalog and are used to group various products together by categories, for example Animal Health or Cough and Cold. Products in a product group must be of type Order_vod.

For example, Sarah Jones is doing a store check for all Cough and Cold goods in a pharmacy. She filters all the Cough and Cold products and quickly completes the shelf check for each of the products.

Configuration

To configure product groups for Inventory Monitoring, enable top-level VMOCs for the Product_Catalog_vod and Product_Group_vod objects and the appropriate platforms. To enable Inventory Monitoring Product Groups for administrators:

1. Ensure users have access to Inventory Monitoring and the Product Catalog. 2. Grant users CRUD permission to the Product_Catalog_vod object. 3. Grant users CRUD permission to the Product_Group_vod object. 4. Grant users FLS edit permission on the Inventory_Monitoring_vod__c field on the

Product Catalog object. 5. Grant users FLS edit permission to the following fields on the Product_Group object:

• Product_Group_Name

• Product_Catalog_vod

• Product_vod

6. Place the Inventory_Monitoring_vod field on the appropriate Product_Catalog_vod object page layout.

To enable Inventory Monitoring Product Groups for end users:

1. Ensure users have access to Inventory Monitoring and Product Groups. 2. Grant users Read permission to the Product_Catalog_vod object. 3. Grant users Read permission to the Product_Group_vod object. 4. Grant users FLS read permission to the Inventory_Monitoring_vod__c field on the

Product Catalog object. 5. Grant users FLS read permission to the following fields on the Product_Group object:

https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Inventory_Monitoring/ConfiguringIM.htm




20

• Product_Group_Name • Product_Catalog_vod • Product_vod

Use

To create the product group and associate a product to that group:

1. Create a new product in the product catalog to represent a specific category, for example Skin Care. The Product Type is Product Group.

2. Create the products to associate to that product group. Ensure the Product Type is Order_vod.

3. Select the Inventory Monitoring check box for the products that should be part of the group.

4. Create the association via the Product Groups section on the Product Catalog Detail page.

Users can filter products based on product groups when viewing Inventory Monitoring line items.

Figure 5: Inventory Monitoring Product Groups

This feature is available on the iPad and Windows 8 and 10 platforms.




21

MEDICAL EVENTS

Child Accounts in Medical Events

Child Accounts are now supported in Medical Events for Japanese orgs. This allows event organizers to properly track HCP behavior in these orgs. For example, Sarah Jones is adding attendees to a Medical Event. On the Manage Attendees page, she can select the appropriate HCO and then select the proper Child Account HCP. This ensures the Attendee record is properly associated with both the account and the HCO.

Configuration

To configure Child Accounts in Medical Events:

1. Ensure Child Accounts are configured. 2. Configure Managing Attendees for Medical Events. 3. Grant users the appropriate FLS permission to the following fields:

Object Field FLS Permission

Child_Account_vod

• Child_Account_vod • Parent_Account_vod

Edit

• Parent_Child_Name_vod • Child_Name_vod • Parent_Name_vod

Read

Event_Attendee_vod Child_Account_vod Edit

Table 3: Child Accounts in Medical Events

4. Activate the appropriate platform VMOCs for the Child_Account_vod object.

Use

To add a Child Account to a Medical Event:

1. Navigate to the appropriate Medical Event. 2. Select the Manage Attendees button. The Manage Attendees page displays all HCOs

available for the user. Select the Hierarchy icon for the appropriate HCO to display all Child Account records associated with that HCO.

3. Select all Child Account records to add as attendees. 4. Select the Up icon next to the HCO name to return to the list of available HCOs.

Additionally, users can select Child Accounts directly from the Child Account view. See Account

Lists and Views for more information.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Accounts/Using%20Accounts/ChildAccounts.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Medical_Events/Managing_Attendees.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Accounts/My_Accounts/Account_Lists_and_Views.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Accounts/My_Accounts/Account_Lists_and_Views.htm




22

The Parent_Child_Name_vod field displays in the Attendees related list of the Medical Event with a Type of Child Account. This feature is available on the Online and Windows 8 and 10 platforms.

MEDICAL INQUIRIES

Medical Inquiry Fulfillment Response Method

When responding to a Medical Inquiry, Medical users can select a fulfillment response method different than the method requested. This enables users to quickly fulfill Medical Inquiries depending on the selected response method. For example, Larry Lakes is an MSL that receives a Medical Inquiry from Dr. Ackerman with Mail as the delivery method. Larry decides to respond to Dr. Ackerman via Email. Larry creates a Medical Inquiry Fulfillment Response (MIFR) with the Email response type and selects Dr. Ackerman’s email.

Configuration

To configure the MIRF:

1. Grant users FLS edit permission to the following fields on the

Medical_Inquiry_Fulfillment_Response_vod object:

● Address_Line_1_vod

● Address_Line_2_vod

● City_vod

● Country_vod

● Email_vod

● Fax_Number_vod

● Phone_Number_vod

● State_vod

● Zip_vod

2. Grant users FLS read permission to the zvod_MIFR_Delivery_Method_vod field on the

Medical_Inquiry_Fulfillment_Response_vod object.

3. Grant the appropriate user profiles access to the following record types on the

Medical_Inquiry_Fulfillment_Response_vod object:

● Email_vod

● Fax_vod

● Mail_vod




23

● Phone_vod

4. Place the zvod_MIFR_Delivery_Method_vod field on the appropriate

Medical_Inquiry_Fulfillment_Response_vod object page layouts,

Use

The zvod_MIFR_Delivery_Method_Value_vod picklist on the MIRF record displays the following information based on the corresponding Record type:

● Email – Displays email addresses associated with the Account on the Medical Inquiry

Response

● Fax – Displays fax numbers associated with the Account and Account’s Address on the

Medical Inquiry Response

● Mail – Displays addresses associated with the Account on the Medical Inquiry Response

● Phone – Displays phone numbers associated with the Account and Account’s address

When creating a response to a Medical Inquiry Fulfillment, the page layout for the response method listed in the Medical Inquiry Fulfillment displays by default. To change the response method, select the appropriate response from the record type picklist.

Adding New Delivery Details

Users can add new delivery details from the MIFR screen. This enables users to add in a delivery value manually if the value is not already available. To add new values:

1. Select the displayed check box to specify an alternate value for the MIFR delivery method.

This check box displays differently based on the selected record type.

2. Enter the appropriate value in the displayed delivery detail field. This field is dependent

on the selected record type.

Figure 6: Medical Inquiry Fulfillment Response

24

This feature is available on the Online and Windows 8 and 10 platforms.

ORDER MANAGEMENT

Viewing IM information in an Order

Inventory Monitoring information can be pulled into the Order Line to aid in identifying stock alerts, product presence, or other helpful information to use when negotiating an order. Pull-in Fields are custom fields with the API Name zvod_IML_<SourceFieldName>_vod__c.

• The pull-in fields pull data from the last Inventory Monitoring record (using the record type defined in the Last Inventory Monitoring Type Veeva Setting)

• For example: The zvod_IML_Layer field on the Order Line, pulls from the Layer_vod__c field in the Inventory_Monitoring_vod__c object into the Order Lines.

Inventory Monitoring records created using the Photo Tagging functionality do not accurately

reflect as a pull-in field on Order lines on the Online platform.

Figure 7: Viewing IM in an Order

For example, Sarah Jones notices Cholecap 20mg is out-of-stock during her visit to a pharmacy. She notes this information in Inventory Monitoring. Later that day, she calls on the pharmacist to take an order, checkes the inventory information, and reminds the pharmacist to order more Cholecap 20mg along with the rest of the order.

Configuration

25

1. Enable the Last_Inventory_Monitoring_Type_vod Veeva Setting with the record type of the appropriate Inventory Monitoring activities to display in the order lines. The value must be the literal match of the Inventory Monitoring RecordType Name.

The default record type for the setting is Inventory_Monitoring_vod.

2. Grant users FLS read permission to the Last_Inventory_Monitoring_Date_vod__c field

on the Order_vod object. This determines how current the inventory monitoring

information and may be displayed in the Order header.

3. Grant users FLS edit permission to the Line_Rank_vod__c field on the

Inventory_Monitoring_Line_vod object. This is a system field that determines the

newest data in Inventory Monitoring if there are multiple lines for the same product.

4. Place the Last_Inventory_Monitoring_Date__c field on the appropriate page layout in

the Order_vod object.

5. Create a pull-in field on the Order_Line_vod object, using the following naming

convention: zvod_IML_<SourceFieldName>.

6. Ensure the data type and length for the source and destination fields match.

7. Place the pull-in field on the appropriate page layout in the Order_Line_vod object.

Use

When placing an order, users can view the pull-in fields in the Order Lines.

• Fields do not display for users who do not have FLS read permission to the source and destination fields

• When a user adds a product to the order lines, the pull-in fields automatically populate with the appropriate values

• If the pull-in field does not have any data, the field displays blank on the order line

• Unless a Veeva Message excludes the pull-in fields, they display on the signature page

• Pull-in fields always display read-only

• Mass Add order entry is supported with pull-in fields

• Offline Validation Rules are not supported with this feature

Cloning / Editing

To facilitate easier order entry, users can clone or edit existing orders with IM pull-in fields. The cloned fields are reset on the order lines with the values from the last IM.

Smart Edit

When a user changes pricing information on the order header when using Smart Edit, the pull-in fields are reset on the order lines with the values from IM.

Multiple IM Lines for 1 Order Line




26

If multiple IM lines exist for the same product, the first line stamped (via the Line_Rank_vod__c field) is ranked first and is the one pulled into the Order Line. Users must have FLS edit permission to this field.


SURVEYS

Branching Surveys

Veeva CRM now supports branching surveys to guide users down conditional paths with questions based on previous answer choices. These surveys allow designers to collect valuable market and segmentation data available only with a customized set of questions while asking users a less generalized set of questions. Branching surveys are used by survey designers, who create the surveys; by end users, who complete surveys; and by coaches filling out Advanced Coaching Reports for employees. For example, Colleen Smith, a survey designer, and her brand team need to determine how many of Sarah Jones’ accounts prefer prescribing Cholecap for noninsulin-dependent diabetes mellitus (NIDDM), but they also want to gather answers only from doctors who currently screen for NIDDM. Colleen creates a survey with a parent question and child questions based on the parent question answer.

Figure 8: Survey Branching Example

Configuration

To enable this feature for survey designers:

1. Ensure the Surveys feature is enabled.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Accounts/Account_Planning_and_Execution/AdvancedCoachingReports.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Surveys/Configuring_Surveys/InitialConfiguration.htm




27

2. Ensure the Advanced Coaching Reports feature is enabled for branching Advanced

Coaching Reports. This step is optional.

3. Ensure survey designers have FLS edit permission to the following fields on the

Survey_Questions_vod object:

● Condition_vod

● Source_ID_vod

4. Ensure survey designers have FLS read permission to the following fields on the

Question_Response_vod object:

● Condition_vod

● Source_ID_vod

● Inactive_Condition_vod

To enable this feature for coaches, end users, and survey integration users:

1. Ensure the Surveys feature is enabled.

2. Ensure the Advanced Coaching Reports feature is enabled for branching Advanced

Coaching Reports. This step is optional.

3. Ensure users have FLS read permission to the following fields on the

Survey_Questions_vod object:

● Condition_vod

● Source_ID_vod

4. Ensure users have FLS edit permission to the following fields on the

Question_Response_vod object:

● Condition_vod

● Source_ID_vod

● Inactive_Condition_vod

This feature is only available for the Online platform. Admins need to prevent survey targets

with branching questions from displaying on other platforms. On other platforms, child

questions display and behave as main line questions, with the potential to gather incorrect

data.


https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Surveys/Configuring_Surveys/InitialConfiguration.htm





28

The following record types are supported: One_Time_vod, Recurring_vod,

Coaching_Report_vod, and User_Survey_vod.

The CRM channel is supported.

Use

There are four areas in a branching survey:

Figure 9: Branching Surveys

The illustrated example contains one main line question and one parent question. The parent

question has two branches and four child questions.

Branching surveys can contain one-to-many parent and child questions. Child questions are not numbered but count toward survey question limits. Only one level of child questions is support; a question cannot be both a child and a parent. Parent questions can be of type picklist or radio button. If a survey designer deletes a parent question, or deletes an answer choice on a parent question, or changes a parent question to a type other than Picklist or Radion button, the associated child questions are also deleted.

Cloning Surveys

Branching logic is preserved when cloning surveys.

Translating Surveys

Branching logic is copied to translated surveys. If the question is also added to the Question Bank, the branching logic is not preserved in the Question Bank.

Answering Surveys with Branching

Child questions display for end users when they select the corresponding answer choice from a parent question.




29

Child questions are indented underneath parent questions and do not display a question number. Only parent and main line questions are numbered. If a child question is marked as required, the validation to ensure the questions is answered is performed only if the question is visible to the end user at the time the survey is submitted. Child questions that are not visible to the end user when a survey target is saved or submitted, have their answer blanked out.

Survey Results

When viewing results of a branching survey on the Survey Management page, only the questions

that were visible to the end user during submission are included in the calculations.

This feature is available on the Online platform.

Events Management

Bulk-Add Event Attendees Events Management users can add event attendees in bulk, allowing efficient input of information. For example, Sarah Jones hosts an event. She uses account lists to help organize the different accounts in her territory. When Sarah creates an event and adds the attendees, she views the appropriate account list and selects the Select All button to add all attendees at the same time. This feature is automatically enabled in orgs created after Veeva CRM 18R3.

Configuration

To enable Bulk-Add Attendees, set the BULK_ADD_ATTENDEE Events Management setting to 1. To disable Bulk-Add Attendees, set the BULK_ADD_ATTENDEE Events Management setting to 0.

Use

To add attendees in bulk:

1. Navigate to the appropriate event. 2. Navigate to the Attendees related list. 3. Select Add to load the Add Attendees page.

From the Add Attendees page, users can select multiple attendees by selecting the check box next to the account name. To add these selected accounts as attendees, select the Add button. This button also displays the total number of selected accounts.




30

To add all accounts on a list as attendees:

1. Navigate to the Add Attendees page. 2. Select the appropriate account list from the drop-down menu. 3. Select the Select button. This changes the name of the button to Select All. 4. Use the Select All button to highlight all accounts.

The Select All button selects all accounts in the list, even if the list is multiple pages long.

5. Select the Add button to add all the selected accounts to the event as attendees.

Figure 10: Bulk-Add Event Attendees


Country-specific Sign-In Sheet Disclaimer

Events Management administrators can configure country-specific disclaimer text in multiple languages that display on the event’s sign-in sheet. This enables administrators to define compliant disclaimer text for each country and in the languages attendees. For example, Sarah Jones hosts an event with a sign-in sheet in Switzerland. Local laws require each HCP signing in to read and accept the disclaimer statement. HCPs are given the option to




31

view the disclaimer text in German, French, and Italian to read and accept when signing into the event. This feature enables changing the language of only the disclaimer text.

Configuration

To configure this feature:

1. Configure translatable signatures, if not all ready configured:

• Grant end users FLS read permission to the Signature_Page_vod object

• Create a VMOC record for the Signature_Page_vod object

2. Grant end-users FLS read permission to the Language_vod field on the

Signature_Page_vod object.

3. Grant end-users FLS read permission to the Signature_Page_vod picklist on the


4. Activate the Medical_Event_vod value in the Signature_Page_vod picklist on the


5. Grant end-users FLS read permission to the Country_vod field on the

Medical_Event_vod object.

6. Place the Language_vod field on the appropriate Signature_Page_vod object page

layouts.

7. Activate the Full Sync VMOC for the Signature_Page_vod.

8. Grant appropriate user profiles Read permission to the Singature_Page_vod object.

9. Create all appropriate Signature_Page_vod records with the following fields populated:

● Record Type = Select Disclaimer_vod

● Active_vod – Set value to True

● Disclaimer_Country_vod – The country that uses the disclaimer

● Language_vod – The language of the disclaimer

● Signature_Page_vod – Select Medical_Event_vod

● Disclaimer_Text_vod – The text of the disclaimer

Use

Disclaimer text automatically assigns to the event based on the Signature_Page_vod records matching the country of the event. To switch the disclaimer text to a different language:

1. Select the Language Selector icon.

2. Select the appropriate language from the list of available languages.




32

Figure 11: Sign_in Sheet Disclaimer

The Language Selector icon also displays on the sign-in sheet from the Attendee related list.

Figure 12: Sign_In Shet

If the account corresponding to the attendee has a Language_vod value matching the Language_vod field of a Signature_Page_vod record, the corresponding disclaimer text in that language automatically displays. This feature is available on the iPad platform.




33

OpenData Integration for Attendee Reconciliation

Users can now search across OpenData and Network to reconcile walk-in attendees in Events Management. This enables users to quickly match walk-in attendees to known HCPs in OpenData or Network by improving name matching and providing access to a larger database than Veeva CRM. For example, Sarah Jones uses Attendee Reconciliation to find a matching account for Clint Ackerman, a walk-in event attendee. The Attendee Reconciliation searches for matching accounts in both Sarah’s local CRM database and in Veeva OpenData. Results are combined and display as potential matches. Since the search runs against all of OpenData, Sarah is able to reconcile the walk-in to Dr. Clinton Ackerman, an account in OpenData, but not in Sarah’s CRM.

Configuration

Prerequisites

To enable this feature, the following prerequisites are required:

● Events Management is configured

● Customers must have an OpenData subscription

● Configured Network Customer Master or OpenData Delivery Manager

● Network to CRM Field mappings is configured

● The Activate Network Account Search Network Setting is enabled


1. Update the Attendee Type formula on the EM_Attendee_vod object to:

IF( OR(NOT(ISBLANK(Account_vod__c)), NOT(ISBLANK(Network_ID_vod__c))), $Label.ACCOUNT_vod, IF(NOT(ISBLANK(Contact_vod__c)), $Label.CONTACT_vod, IF(NOT(ISBLANK(User_vod__c)), $Label.USER_vod, IF(NOT(ISBLANK(TEXT(Walk_In_Status_vod__c))), $Label.WALK_IN_vod, $Label.ONLINE_REGISTRANT_vod))))

2. Grant administrators FLS edit and end users FLS read permission to the Network_ID_vod

field on the following objects:

● Event_Attendee_vod

● EM_Attendee_vod

3. Populate the Country_vod field on the User object for all appropriate users.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Events%20Management/Configuration/QuickStartGuide.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Integration/Network_Integration/Network_Mapping/Network_Mapping_Overview.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Integration/Network_Integration/Account_Search.htm




34

This feature requires an internet connection.

Use

Attendee reconciliation searches run against both Network and CRM databases. Results are combined, enabling the user to select the Confirm Match button on the appropriate account. When matching a walk-in attendee to a record from Network, the Walk_In_Status_vod picklist on the attendee record updates to Reconciled_To_Customer_Master_vod and the attendee’s Network_ID_vod field stamps with the Network record’s Network VID. This indicates that the attendee was reconciled to a Network record and provides the appropriate information to find the account in Network. The Network VID is the only information copied down from Network. If the matched account is

not included in the OpenData subscription, it is added when a match is confirmed.


Vault Integration for Event Materials

Events Management now supports viewing Vault documents directly from event material records in CRM. This integration enables greater control over event content by ensuring only the most recent and approved material displays for events. For example, Sarah Jones’s company stores the template for ad-board agendas in Vault. The template in Vault links to an EM catalog record in CRM. Sarah views the most recent template in Vault directly from the event material record in CRM, even though she does not have a Vault login.

Configuration

To configure Event Materials in Vault:

1. Ensure the Approved Email Integration user is properly configured in CRM.

2. Ensure the appropriate event material is in a steady-state in Vault.

3. Ensure the Integration user can view the appropriate event material in Vault.

4. Grant end-users FLS read and administrators FLS edit permission to the Vault_Link_vod

field on the EM_Catalog_vod object.

5. Add the View_vod button to the list of visible buttons on the EM_Event_Layout_vod

record associated with the Event Material record type.

Use

To link a Vault document to an EM_Catalog_vod record in CRM, paste the Vault document’s complete URL into the Vault_Link_vod field of the corresponding EM Catalog in CRM.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/Approved_Email/Configuration/BasicAEConfig.htm

http://vaulthelp.vod309.com/wordpress/admin-user-help/document-lifecycles-admin/about-special-states/

http://vaulthelp.vod309.com/wordpress/admin-user-help/ah-user-permissions-access-control/configuring-user-permissions/




35

A View button displays for event material records created using the linked EM catalog record.

● For all platforms, the View button displays on the event material record’s detail screen

Figure 13: Vault Integration for EM

● On the Online platform, the View button also displays next to the event material record

on the event detail page

Figure 14: Event Detail page

Selecting the View button displays the Vault document in each platform’s native browser using the External Vault Viewer.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/Approved_Email/Content_Creation/Vault_ViewerOptions.htm




36

Figure 15: External Vault View

Document views from this feature do not count toward document view license limits in Vault.

This feature is available on the Online and iPad platforms.

Multichannel

APPROVED EMAIL

Approved Email Content Search Enhancements The default search in Approved Email now uses keywords where the search phrase is considered an OR statement with all wor Auds in the phrase. Additionally, a starts with search is performed for each keyword in the search phrase Users can force the search to return only results containing all of the keywords (creating an AND statement rather than an OR statement) in the search phrase by selecting the Must Include All Keywords toggle. For example, Sarah Jones searches for Efficacy Rax which returns Efficacy of Raxxipen and Efficacy of Cholecap.




37

Figure 16: AE Advanced Search

Sarah then selects the Must Include All Keywords check box and searches again. This search only returns Efficacy of Raxxipen.

Figure 17: AE Advanced Search Results

This feature is available on the Online and iPad platforms.

Stamping the Email Source in Approved Email

The field where the the email address was sourced in an Approved Email automatically stamps on the created Sent_Email_vod record. This enables administrators to view the source of the email address used in Approved Email. This feature is enabled by default.

Configuration

To disable this feature, remove FLS edit permission to the Email_Source_vod field on the Sent_Email_vod object. This feature is available on the Online and iPad platform.




38

CLM

Mapping Vault Object Reference Fields Administrators can now map custom fields in CRM Products to custom object reference fields within the CRM Product (CRM_Product__v) and CRM Detail Group (CRM_detail_group__v) objects in Vault to enable users to filter CRM products by more than one org.

Verteo Biopharma has multiple CRM orgs connected to one global Vault. He wants to display Cholecap, but only for the US market, not Capchole which is in the Canadian market. John filters the one org to display Cholecap.

Use

Before being able to filter products, a link is established between CRM Product fields and Vault via the CRM Vault Metadata Sync administration page. To create the mapping:

1. Select the CRM Vault Metadata Sync Administration tab. 2. Select View Map in the Vault Connection Management section. 3. Select Edit Mapping. 4. Select Show All for Vault Fields. 5. Select the appropriate field from the drop-down on the referenced Vault object. 6. Select the appropriate field from the drop-down for CRM API Name (Product_vod__c

object).

Figure 18: Mapping Vault Object Reference Fields

The following CRM and Vault Field Types are supported: Field values must be an exact match to populate the object reference field.




39

CRM Field Type Vault Field Type

Text Text, Picklist, Multipicklist

Text Area Text, Picklist, Multipicklist

Boolean Boolean

Number Number

Picklist Text, Picklist, Multipicklist

MultiPicklist Text, Multipicklist

URL Text

Table 4: Mapping Vault Object Reference Fields

This feature is available on the Online platform.

Presentation Labels in CLM

Users can create and add labels to CLM presentations to organize their presentations. Using labels aids in quickly identifying the appropriate presentation to use especially if there are several presentations from which to select. For example, Sarah Jones uses different presentations based on the HCP she visits. She creates a custom label for each type of HCP and applies the appropriate label to the corresponding presentations. When Sarah visits an Dr. Ackerman, she filters the total list of CLM presentations to only display the presentations for Cholecap, a drug Dr. Ackerman typically orders. Custom labels are unique to individual users and are not shared between users. This feature is enabled by default.

Use

Managing Custom Labels

To create and apply a custom label:

1. Navigate to CLM Presentations.

2. Select the More Actions button for the appropriate presentation.




40

Figure 19: Presentation Labels in CLM

3. Select Add Labels.

4. Create a new custom label or select from the list of existing custom labels. Presentations

can have multiple labels and a label can be applied to multiple presentations.

Figure 20: Adding Presentation Lables

5. Select Save.

Labels are case insensitive. Users can create new custom labels from the Filter menu by selecting the Create New Label button.




41

Selecting the Edit button from the Filter menu enables users to edit or delete existing labels:

● To delete a label, select the red circle button, then select Delete

● To rename a label, select the pencil button

Custom labels store locally on the device and do not upload to Veeva CRM. Labels are kept

when refreshing the database or upgrading Veeva CRM, but delete if Veeva CRM is uninstalled.

Filtering by Custom Labels

To filter by custom labels:

1. Select the Filter button.

2. Select all appropriate labels to display.

The number of presentations using the label displays next to the label name.

3. Select Apply.

Figure 21: Filtering Presentations

Labels cannot be filtered if there is already an applied directory filter.

This feature is available on the iPad platform.

Enhancing Single-Doc Publishing

Single-Doc publishing supports slide titles and numbering for PowerPoint presentations via CRM Rendition settings in Vault.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/CLMVaultIntegration.htm




42

To display the selected option in CRM:

1. Select the CLM Content Admin (CLM_Admin_vod) tab. 2. Select View Map in the Vault Connection Management section. 3. Select the Compare CRM to Vault button. 4. Select the Sync button on the CLM Administration page.

Ensure the appropriate fields are configured within Vault's CRM Rendition Settings. Refer to Vault documentation for more information.

Display By View for Grouping Presentations

In addition to viewing presentations by Tile view and Table view, users are now able to select from a list in the Display By view to group presentations.

Figure 22: Display By View

The default view is the first option in the Display By list. Once you select a new option, that option becomes sticky and automatically displays the next time you access the Display By view.

Augmented Reality in CLM

CLM Administrators can now display Augmented Reality (AR) content in CLM, enabling more creativity when displaying product metrics, effects, and information. AR overlays virtual objects, called models, onto a lens of the real world, called the scene. Augmented Reality differs from Virtual Reality (VR) in that AR uses a blend of virtual objects and the user’s surroundings, rather than completely replacing the surroundings with a virtual environment as in VR.

http://vaulthelp2.vod309.com/wordpress/applications/promotional-materials-edition/using-single-document-multichannel-publishing-promomats-medcomms/

http://vaulthelp2.vod309.com/wordpress/applications/promotional-materials-edition/using-single-document-multichannel-publishing-promomats-medcomms/




43

Models placed on an AR scene are interactive and can be navigated, simulating the experience in the real world. With AR, users can visualize objects or experiences users would otherwise have difficulty experiencing. For example, Sarah Jones visits Dr. Ackerman to talk to him about Restolar, a product designed to treat vision loss. She shows him an AR CLM presentation using a model of a human eye. She places the model on the scene and uses her device to view and interact with the model, simulating the effects of vision loss and how Restolar improves vision.

Components

AR presentations consist of the following components:

The Scene

The scene is the virtual representation of the world as seen through the device’s camera. The scene can be navigated by walking around or repositioning the camera.

Models

Models are static or interactable virtual objects placed on the scene. An AR presentation may have multiple associated models. Models may have associated animations to better present content. Models can be moved, rotated, and resized to display optimally, and then locked in position for interaction and navigation.

Opening Slide

The opening slide of an AR Presentation is a traditional CLM slide and is the default. From here, AR mode can be activated. Exiting AR mode returns to the opening slide. Slides must be either image or HTML content types.

Configuration

To configure AR content in CLM:

1. Ensure CLM is properly configured. 2. Ensure the packaged CLM presentation contains the following files:

• A JSON file named AR_configuration.json • All files and assets utilized by the JSON file

See Content Packaging for additional guidelines on packaging CLM content.

Use

When viewing a piece of CLM content with AR, enter AR mode by selecting the AR button at the top-right corner of the screen.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/Getting_Started/BasicCRMConfig.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/Media_Pkging_Guidelines/ContentPackaging.htm




44

Figure 23: Augmented Reality exaple

In AR mode, the device’s camera is used to display the user’s surroundings. The scene’s name displays in the top center of the screen. Selecting the AR button while in AR mode ends AR mode and displays the opening slide. CLM tracking occurs for AR presentations, activity within a scene is not tracked.

Managing Models

To add AR models to the scene:

1. Select the + button. 2. Select the desired model from the list of models. 3. Follow the displayed prompt to locate a flat surface. This surface anchors the AR model.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/CLM_Interactive_Media/AdvPlayerConfig.htm#Tracking




45

Figure 24: Displaying AR

4. Move the model to the desired location by using a one-finger dragging motion. 5. Rotate the model to the desired orientation by using a two-finger circular motion. 6. Properly size the model by using a two-finger zoom gesture to enlarge the model or a

pinch gesture to shrink the model. 7. Lock the model in place by selecting the green check mark or double-tapping the model.

Models must be locked in order to use interactions or animation effects associated with

the model.

Double-tap a locked model to enable editing its position, size, and orientation. Unlocked models can be deleted by selecting the Trash Can button. For optimal performance, Veeva recommends only having one interactable model placed on

the scene at a time.

Selecting the Reset button at the top right corner of the screen removes all models placed on the scene.




46

Figure 25: Resetting the AR Scene

Animation Control Panel

CLM supports two types of animation triggers in the animation control panel AR content:

• Slider Animation – Displays as a slider bar at the bottom of the screen. Animations can be controlled by selecting the bar and moving it right or left.

Figure 26: Slider Bar in AR

• Next and Previous – Displays as Next and Previous buttons. Use these buttons to

navigate to the previous or next animation.




47

Figure 27: Previous and Next in AR

This feature requires iOS 11 or later and is supported on iPad 9.7” and all iPad Pro models. This feature is available on the iPad platform.

AR Content Creation For more information on what AR Content is, along with packaging and using AR Presentations, see AR in CLM.

Guidelines

The font, location, and size of all headings or labels cannot be formatted.

Models

All models must use the .dae or .obj file format. If the model uses animations, the .dae format must be used. For optimal performance, an individual model must not exceed 100,000 polygons. Veeva recommends limiting a scene to less than 10 models.

Animations

IDs must be set for each animation to be referenced in the JSON file. Animations should have a recognizable name describing the associated object, for example, Disposable_Syringe, Iris, Left_Artery, etc.




48

Masks

Masks enable all or a portion of a model to be hidden when viewing the model from a certain angle. Masks must be a 3D mesh and can be any shape. The mask needs to be identified in the JSON file. Only use one mask per model.

Textures

Textures can be created and edited using a raster graphics editor. For optimal performance, use to portray details on a model rather than adding polygons to the model. Limit each model to one set of 2048x2048 textures.

Preparing Files

After optimizing and testing a model and its associated textures, normal maps, audio, and animations, place the model and its assets in a folder. For example, the folder Eye contains the model file for a human eye along with all other assets used by the model. Repeat this process for all models in an AR scene.

JSON Configuration

The AR_configuration.json file defines the scene and all models used by the presentation. Every scene has an id, name, and an array of models: "scenes" : [

{ "id" : "scene.L004", "name" : "Veeva_keynote_demo", "models" : [...] }

]

Each model contains a series of metadata tags defining the model’s appearance and behavior. The following metadata tags are available:

Metadata name Example Description

id scene.L004

name Veeva_keynote_demo The title of the scene displays at the top of the screen.

debug_mode "debug_mode" : true If true, displays the debugging overlay for testing the models.




49

Veeva recommends setting this to

false before deploying to

production. models "models": [

{ "id": "eyeball.demo", "name": "Eyeball_opt", "path": "Models", "assets": "Eyeball_v12", "file_extention": "dae" {

]

The list of models available for selection in the scene. Specify the following parameters for each model:

• Id • Name • Path • Assets • File_extension – Must be either

dae or obj

id Eyeball.demo The unique id of each model. This needs to be specified when placing more than one model on the scene.

path Models The path to the Models file. Each model within a scene can have its own path.

assets Eyeball_Env.scnassets The path to the assets used by the model. This path is within the path metadata tag. In this example, the location is ./Models/Eyeball_env.scnassets/

file_extension .dae or .obj Allows different kinds of AR compatible files.

normal_maps "obj_name" : "Sclera", "texture_name" :

"Sclera_Normal_Map.tga"

More than one normal map can be associated with a model. Specify both the texture name and the ID of the associated object.

Scale 1.0, 1.0, 1.0

The X, Y, and Z values of the object’s initial scale.

logo logo.png The name of the overlay image. This image can contain company logos, instructions, safety information, etc. This image is always centered and will scale down to fit a screen resolution, but not up.

Veeva recommends this image have

a transparent background and is

tested to ensure the image does not

obscure actions.




50

animation_ control_panel

"animation_control_panel":

{ "type": "control_panel", "id":

"control_panel.eyeball", "buttons": [...]

}

Defines the actions when selecting the Next and Previous buttons. Each button can have multiple associated actions.

touch_triggers "touch_triggers": [ { "type": "trigger", "id": "trigger.pupil", "obj_name": "Pupil", "fade_object" : true, "fade_object_duration" :

1.0, "actions": [...] }

]

Defines actions initiated by selecting specific objects of the model. Set the ID parameter to the ID of the associated object.

Fades and duration of fades, in seconds, are also controlled by this metadata tag.

anchors "anchors" : [ { "type" : "anchor", "id" : "anchor.eyeball", "obj_name" :

"II__Eyeball", "position" : [ 0, 0, 0

], "distance" : 0.4, "actions" : [ { "type" : "label", "id" : "label.eyeball" } ]

} ]

The reference points for proximity triggers. When the camera is closer to the object than the distance specified, the actions initiate. The following parameters must be defined for each anchor:

• Type – Is always anchor • Id • Obj_name – The id of the

appropriate object • Position – Specifies an offset

distance from the center of the object. This enables the activation point to be outside of the model rather than all around it

• Distance – Radius, in meters, of the activation point

• Actions – Multiple actions can be associated

animations "animations": [ { "type": "animation", "id": "Pupil-anim", "autoplay": false, "repeat_count": 1 }

]

Defines all animations in the model.

Set the autoplay parameter to true to begin the animation when the model loads.

A repeat count of 0 (zero) endlessly loops the animation.

audios "audios" : [ {

Define any audio files played when initiating actions.




51

"type" : "audio", "id" : "audio.shot", "file_name" :

"ArrowHit02.wav" }

]

labels "labels" : [ { "type" : "label", "id" : "label.eyeball", "text" : "The Eyeball" }

]

Defines labels or descriptions displayed using actions.

Formatting cannot be applied to this

text block. Labels always displays in

the same location at the bottom

center of the screen. reference_images "reference_images" : [

{ "name" :

"eyeball_marker.png", "width" : 0.08 }

]

The name of the image used to trigger the image-recognition software when placing a model.

mask "portal" : { "type" : "portal", "id" : "portal.demo", "interior_name" :

"Entire_Scene", "mask_name" : "Mask"

}

Enables hiding all or a portion of a model when viewed from a certain angle. The interior_name parameter defines the ID of the model being hidden. The mask_name parameter defines the ID of the masking object.

Example Scene

"scenes": [ { "id": "scene.L005", "name": "Veeva AR Demos", "debug_mode": true, "models": [ { "id": "eyeball.demo", "name": "Veeva_Large_Eyeball_opt", "path": "Models", "assets": "Eyeball_Environment_Scene_v12-opt.scnassets", "file_extention": "dae", "normal_maps" : [

{ "obj_name" : "Sclera", "texture_name" : "Veeva_Sclera_Normal_Map_v2.tga" }, { "obj_name" : "Nu_Retina",




52

"texture_name" : "Veeva_Retina_Interior_Normal_Map_v3.tga" }

], "scale": [ 1.0, 1.0, 1.0

], "logo": "logo.png", "animation_control_panel": { "type": "control_panel", "id": "control_panel.eyeball", "buttons": [...]

} }

Interaction triggers cause certain changes in the model to occur, for example, starting an animation, displaying a label, or playing an audio file. Three kinds of interaction triggers initiate actions:

• Touch triggers • Proximity triggers • Animation Control Panel – Controlled in one of two ways:

o Slider control bar o Forward and Previous buttons

Each interaction trigger can cause one or several actions. These triggers are set up in an array within the JSON file. Always specify the following information for all interaction triggers:

• Type • ID of the associated object • Name of the associated object • Type of action • ID of individual action

Touch Trigger Example

"touch_triggers" : [

{

"type" : "trigger",

"id" : "trigger.left.door",

"obj_name" : "NovaSeq_2_a_Left_Door",

"actions" : [

{




53

"type" : "animation",

"id" : "NovaSeq_2_a_Right_Door-anim"

},

{

"type" : "audio",

"id" : "audio.right.door.start"

}

]}]

Proximity Trigger Example

"anchors" : [ { "type" : "anchor", "id" : "anchor.lens", "obj_name" : "Retina_front", "position" : [ 0, 0, 0 ], "distance" : 0.4, "actions" : [ { "type" : "animation", "id" : "Back-anim" }, { "type" : "label", "id" : "label.eyeball" }

]}]

Control Panel Example

Each set of animations can also be controlled by the animation slider rather than playing from beginning to end automatically: "animation_control_panel" : {

"type" : "control_panel",

"id" : "control_panel.demo",

"slider" : false,

"buttons" : [

"actions" :[

{

"type" : "audio",

"id" : "audio.pi3k"

},

{


"id" : "NovaSeq_2_a_Left_Door-anim"




54

}

{

"type" : "audio",

"id" : "audio.fgfr"

},

{


"id" : "NovaSeq_2_a_Right_Door-anim"

}

]

}

//Animations that play when triggering the associated action. "animations" : [ { "type" : "animation", "id" : "NovaSeq_2_a_Left_Door-anim", "autoplay" : false, "repeat_count" : 1 }

]

//Audio files that play when triggering the associated action. "audios" : [ { "type" : "audio", "id" : "audio.fgfr", "file_name" : "Pipeline.mp3" }

]

//Labels that display depending on the triggered action. "labels" : [ { "type" : "label", "id" : "label.monitor", "text" : "This is the MONITOR" }

]

VEEVA NOW

After the production upgrade to Veeva CRM 18R3, Veeva Now will no longer be available in the iOS app store. New installations are no longer possible after this date. Veeva will no longer support notifications to Veeva Now after the 19R1 production upgrade in April 2019.




55

For real-time notifications, users should use Veeva CRM on the iPad or iPhone. See Push Notifications for more information.

CONSENT CAPTURE

Capturing Consent to Track Email Activity

HCPs now have the option to have their email activity tracked anonymously. Administrators can configure Consent Capture to allow HCPs to opt into receiving Approved Emails but not have any subsequent email activity associated with their account information. This enables customers to be compliant with local data regulations.

When an HCP opts into receiving Approved Email but does not want their activity tracked, the Multichannel_Consent_vod record does not stamp with a value in the Activity_Tracking_vod field. Any Approved Email sent after this Multichannel_Consent_vod record is created has email activity associated to an anonymous Sent_Email_vod record.

The following Email_Activity_vod fields do not stamp any values associated with the anonymously tracked Sent_Email_vod record:

● Event_Msg_vod

● IP_Address_vod

● Click_URL_vod

● User_Agent_vod

Email events, delivered, bounced, dropped, unsubscribed, unsubcribed all, marked as spam,

and preferences modified, are still tracked on the initial Sent_Email_vod record since they

pertain to the delivery of the email itself rather than actions taken by the recipient. These email

events, Opened, Clicked, Viewed, and Downloaded are tracked to the anonymous

Sent_Email_vod record.

For example, Sarah Jones visits Dr. Clinton Ackerman and Dr. Bob Adams. Both opt into Approved Email communications regarding Cholecap. Dr. Ackerman consents to have the email activity tracked. Dr. Adams does not. Activity from the email to Dr. Ackerman associates with his account, while activity from the email to Dr. Adams tracks anonymously, without any reference to Dr. Adams.

Configuration

To configure email activity tracking in Consent Capture:

1. Ensure Approved Email is properly configured. 2. Ensure Consent Capture is properly configured. 3. Grant the following user profiles the appropriate FLS permission to the following fields:

https://crmhelp.veeva.com/doc/Content/CRM_topics/Mobile_Device_Setup/PushNotifications.htm


https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/Approved_Email/Configuration/BasicAEConfig.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/Capturing_consent/CaptureConsent.htm#Configuration

56

Object Field End-User

FLS Integration

User FLS

Consent_Type_vod ● zvod_Consent_Default_Consent_Text_vod ● zvod_Consent_Activity_Tracking_vod

Read N/A

Multichannel_Consent_vod ● Default_Consent_Text_vod ● Activity_Tracking_vod

Edit N/A

Table 5: CC Email Activity Tracking FLS

4. Add the following Consent_Type_vod fields to all appropriate page layouts:

• zvod_Consent_Default_Consent_Text_vod

• zvod_Consent_Activity_Tracking_vod

4. The following Consent_Type_vod fields should be populated with a value –

• zvod_Consent_Default_Consent_Text_vod

• zvod_Consent_Activity_Tracking_vod

The text in the zvod_Consent_Activity_Tracking_vod field supports the following HTML tags:

• Paragraph – 

• Line Break – 

• Bold – 

• Italics – 

• Underline – 

• Ordered and Unordered Lists – <ol>, <ul>, and <li>

• Hyperlinks – <a>, must have the target attribute set to _blank

Approved Email Configuration

To enable activity tracking options in Approved Email:

1. Grant end-users FLS edit and integration users FLS read permission to the Activity_Tracking_Mode_vod field on the Sent_email_vod object.

2. Grant integration users FLS edit permission to the VExternal_Id_vod field on the Sent_Email_vod object.

3. Grant the integration user Create access to the Sent_Email_vod object and access all record types on the Sent_Email_vod object.

Use




57

On the Consent Capture screen, the Activity Tracking check box displays with the text from the zvod_Consent_Activity_Tracking_vod field. Users must consent to receive emails in order to allow tracking the activity of those emails.

Figure 28: CC Email Activity Tracking Opt Out

Figure 29: CC Email Opt In

Anonymous Tracking in Approved Email

When sending an Approved Email, if the configuration requires a check for consent and the resulting

Multichannel_Consent_vod record has a blank Activity_Tracking_vod field value, then anonymous

tracking is enabled and the Activity_Tracking_Mode_vod picklist on the corresponding Sent_Email_vod

record populates as Anonymous_vod.

Regular Tracking in Approved Email

When sending an Approved Email, if the configuration requires a check for consent and the resulting

Multichannel_Consent_vod record has a value in the Activity_Tracking_vod field populated, then regular




58

tracking is enabled and the Activity_Tracking_Mode_vod picklist on the corresponding Sent_Email_vod

record populates as Regular_vod.

If end-users do not have FLS edit permission to the Activity_Tracking_Mode_vod picklist on the

Sent_Email_vod object, the behavior defaults to regular tracking. Prior to the 18R3 release, this

was the default behavior.

Approved Emails sent from the following entry points always use regular tracking as these emails do not require consent:

• Medical Inquiry

• Receipts

• Double Opt-In

• Case


Opt-Out Specific Disclaimer Text in Consent Capture

Administrators can configure Consent Capture to support an opt-out specific disclaimer when opting out of a channel. This provides additional clarity regarding what the account consents to. For example, Sarah Jones visits Dr. Clinton Ackerman, who decides to opt-out of communications regarding Cholecap but opt into communications regarding Restolar. When Sarah captures Dr. Ackerman’s consent, an opt-in disclaimer displays for Restolar and a separate opt-out disclaimer displays for Cholecap.

Configuration


1. Grant end-users FLS read permission to the following fields on the Consent_Type_vod

object:

● Opt_Out_Disclaimer_Text_vod

● zvod_Opt_Out_Consent_Line_vod

2. Add the following fields on the Consent_Type_vod object to the appropriate page

layout:

● Opt_Out_Disclaimer_Text_vod

● zvod_Opt_Out_Consent_Line_vod




59

3. Grant end-users FLS edit permission to the Opt_Out_Disclaimer_Text_vod field on the

Multichannel_Consent_vod object.

4. Populate the Opt_Out_Disclaimer_Text_vod field on the Consent_Type_vod object on the appropriate page layout.

Use

If an account uses Consent Capture to opt-out of communications for a certain product or channel, the Opt_Out_Disclaimer_Text_vod field displays along with each product or content type the account is opting out of. If the account is opting out of some products or content types and opting into others, both the opt-in and opt-out sections display.

Figure 30: Opt-Out Disclaimer

The opt-out and opt-in sections only display if the appropriate consent is being captured from

the account. If a section does not display, fields in those sections are left blank in the resulting

Multichannel_Consent_vod record.


ENGAGE

Engage Webinar Recording

Engage administrators can now record and store Engage Webinars for future training, marketing, or auditing purposes. Recorded webinars are stored in Veeva Vault for 30 days. For example, Sarah Jones hosts an Engage Webinar on the efficacy of Cholecap. She selects the Record to the Cloud button as the Webinar begins. Part way through the Webinar, she selects the Cloud button and pauses the recording for a break. This counts as one recording. Sarah selects Record again when the webinar continues. This counts as a second recording. After the webinar is complete, both recordings are stored together in Vault.




60

Configuration

Prerequisites

This feature requires a connection with Vault:

1. Navigate to the Engage Meeting & Webinar Process Administration tab.

2. Select New in the Vault Login Credential Management section.

3. Enter the following credentials:

● Vault Name

● Vault URL

● Username

● Password

4. Select Save to validate the connection.

To configure Engage Webinar recordings:

1. Grant integration users FLS edit permission to the following EM_Event_vod fields:

● Vault_External_ID_vod

● Vault_Binder_Path_vod

2. Grant end-users FLS read permission to the Attendance_Report_Process_Status_vod

picklist field on the Remote_Meeting_vod object.

Use

Webinar hosts can begin recording a webinar by selecting the Record to the Cloud button in the More Actions menu. Hosts can pause or end the recording by selecting the Cloud button, then selecting the appropriate action. If a host stops or pauses a recording and then restarts, two recordings are saved. After the host ends the webinar, all recordings made during the webinar are upload to the configured Vault and are stored in a new Vault Binder. The created binder is named after the event and the date of the webinar. The location of the created binder stamps in CRM on the Vault_Binder_Path_vod field on the EM_Event_vod record. This feature is available on the Online and iPad platforms.

http://vaulthelp.vod309.com/wordpress/user-help/binders-user-help/viewing-binders/




61

MyInsights

Medical Dashboard The Medical Dashboard provides MSLs with information about communications with a Stakeholder, including current and planned action items. This information helps MSLs determine future actions and plans. Depending on permissions, the following widgets are available to display on the Medical Dashboard:

• Engagement Plan - a list of all Engagement Plans associated to Stakeholder

• Interaction Summary - the activity summary for the Stakeholder based on Interactions, Sent Emails, Multichannel Engage Activities, Medical Events, Medical Inquiries, and Medical Insights

• Open Actions - open actions based on Tasks, Interaction Objectives, and Medical Inquiries

• Suggested Actions - open suggestions for the Stakeholder

• Scientific Activity - a summary of media presentations displayed to Stakeholder

• Medical Insights - all Medical Insight records made with the specific Stakeholder

• External Scientific Activity - a summary from Clinical Trials, Publications, and Medical Events

For example, Larry Lakes reviews Dr. Clinton Ackerman’s Medical Dashboard. On the scientific activity widget, Larry notices it has been a few weeks since Dr. Ackerman saw the new scientific publications on the new trials for Cholecap Efficacy results. Larry makes a note to review and discuss the new efficacy studies in the next interaction with Dr. Ackerman.

Configuration

To configure the Medical Dashboard for end users:

1. Ensure Medical and MyInsights HTML Reports are enabled. 2. Ensure the record types for the appropriate entry point are enabled:

Account_Reports_vod, KOL_Profile_vod or Account_Profile_Override_vod. 3. Create or activate the appropriate VMOCs: 4. Grant Read access to objects, and FLS read permission to the corresponding fields listed

below:

Object Field

Call2_vod Call_Datetime_vod CLM_vod

Call2_Detail_vod Detail_Group_vod

https://crmhelp.veeva.com/doc/Content/CRM_topics/Medical/MedicalOverview.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/My_Insights/HTMLReports/HTMLReports.htm




62

Product_vod

Call_Objective_vod Account_vod From_Date_vod To_Date_vod Title_vod Completed_Flag_vod

Sent_Email_vod Account_vod Email_Sent_Date_vod Product_vod Detail_Group_vod Open_vod

Medical_Event_vod Account_vod Start_Date_vod Start_Time_vod

Event_Attendee_vod Account_vod EM_Attendee_vod Attendee_vod

Medical_Insights_vod Account_vod Status_vod Clinical_Trial_vod Interaction_vod Other_Source_vod Publication_vod Medical_Event_vod

Multichannel_Activity_vod Account_vod

Multichannel_Activity_Line_vod Account_vod

Medical_Inquiry_vod Account_vod Status_vod

Suggestions_vod Account_vod Expiration_Date_vod Posted_Date_vod Reason_vod Mark_As_Complete_vod Dismiss_vod Record_Type_Name_vod

Task_vod AccountID Title

Call_Key_Message_vod Account_vod




63

CLM_Presentation_Name_vod Product_vod Detail_Group_vod

Clinical_Trial_vod Account Date_vod Description_vod

Account_Clinical_Trial_vod Account_Id_vod Clinical_Trial_vod

Publication Account Date_vod Title_vod

Account_Publication_vod Account_Id_vod Publication_ID_vod

Table 6: Medical Dashboard

To configure the Medical Dashboard using MyInsights HTML Reports:

1. Download the Medical Dashboard HTML zip file (available with the 18R3 Production upgrade) or create your own. The MyInsights JavaScript Library can be used in the HTML for these reports. Note: If you are creating your own HTML visualization, compress the files inside your top-level folder. For example, compress the Assets folder and the index.html file to create the Archive.zip file.

2. Navigate to the HTML Reports tab. 3. Create a new HTML_Report_vod record with the appropriate record type :

Account_Reports_vod, KOL_Profile_vod or Account_Profile_Override_vod. 4. Specify a Report Name for the dashboard. 5. Attach the HTML report zip to the HTML Report record using the Notes and Attachment

related list.




64

Figure 31: Medical Dashboard


MyInsights Smart Linking Enhancement

The following are available with the 18R3 Production upgrade.

• Suggestions - Users can execute Suggestions via Smart Linking in MyInsights

• Approved Email - Approved Email users can now create a new email from MyInsights as well as view previously sent emails

• CLM - Users can launch the Media Library for a specific HCP from a MyInsights visualization or launch a specific presentation

See the Developer Portal for more information after the18R3 Production upgrade.

https://developer.veevacrm.com/




65

Scheduling and Planning

Schedule Color Changes

Based on customer feedback after the launch of Sunrise, we updated the My Schedule colors for both Online and iPad to better differentiate the Call states. We made the decision to push these changes because quickly identifying Calls is an important part of the users’ interaction with Veeva CRM. The following is information you can share about the color changes. You can also view the color changes in this video.

• Shades of teal/green show progression through the statuses

o Light teal - planned o Dark teal - saved o Green – submitted

• Red indicates past calls - prominently highlighted • White pattern aids in identifying planned calls easily

Figure 32: Weekly Calendar Schedule Colors

http://docs.veevacrm.com/New%20Colors.mp4




66

When using Shared Calendars in the Online platform, events from those shared calendars

display with a black border to make visible what events are the current users and what events

are from the shared calendar.

Figure 33: Color Chart

Parity

Push Notifications

iPad users can now use Push Notifications.

ACCOUNTS

Advanced Coaching Reports

iPad user can now comment on Advanced Coaching Reports. See Employee Commenting on Advanced Coaching Reports for more information.

CALL REPORTING

Call

iPhone Call Reports now support:

• Unique Activity calls

• Attendee Specific fields







67

• Account Tactic, Product Strategy, Product Tactic on Call Discussion

• Medical Discussion

• Call Follow-ups

EVENTS MANAGEMENT

Limiting Outside Territory Searches

iPad users can now Limit Outside Territory Searches.

Speaker Contract Generation

Windows 8 and 10 users can now generate contracts for speakers. See Speaker Contract Generation for more information.

SCHEDULING AND PLANNING

MCCP

MCCP Administrators can now indicate product goals by priority for the same product via one call channel on the iPad platform. See MCCP Goals by Priority in a Single Call Channel for more information.

MYINSIGHTS

iPhone now supports MyInsights SmartLinking.

NETWORK

Creating Unverified Records

Windows 8 and 10 users are now able to create unverified records to maintain a clean CRM data set. See Creating Unverified Records for more information.

SURVEYS

Surveys for iPhone Surveys are now available on the iPhone platform. To enable Surveys on iPhone, admins must enable the appropriate Surveys VMOCs. The minimum required VMOCs for Surveys include:

• Survey_vod for iPhone

• Survey_Target_vod VMOC for iPhone

• Survey_Question_vod VMOC for iPhone

• Question_Resonse_vod VMOC for iPhone

Admins must ensure they enable the appropriate VMOCs and ensure the Where clauses are updated with any existing Where clauses used for iPad to ensure parity.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Events%20Management/Using/Attendees.htm#Limiting

https://crmhelp.veeva.com/doc/Content/CRM_topics/Events%20Management/Using/SpeakerContractGeneration.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Events%20Management/Using/SpeakerContractGeneration.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Scheduling_Planning/Cycle_Plans/Multichannelcycleplans/UsingMCCP/GoalsbyPriority.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Integration/Network_Integration/Data_Change_Requests/CreatingUnverifiedRecords.htm




68

See the Surveys documentation for more information.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Surveys/SurveysOverview.htm




69

Revision History

Feature Date Change

Country-Specific Disclaimer 11/8/2018 Added config steps, changed screen shots

Viewing IM Infor in an Order

11/8/2018 Added note about records created using Photo Tagging.

Appendix A: New Objects

The list below contains all objects added in Veeva CRM Version 18R3.

Object Label Description

Action_Item_vod Action Item Object used to represent a task that is associated to an account plan through the Account Plan hierarchy.

Sent_Message_vod Sent Message The object contains a record of outbound messages

Table 7: 18R3 Objects

Appendix B: New Fields

The list below contains all fields added in Veeva CRM Version 18R3. The fields are organized by object. Visibility to all fields is disabled by default to all users except administrators. See the Veeva Data Model information for a full listing of Veeva objects.

Object Field Name Field Label Description Field Type

Account_Plan_vod

Progress_vod Progress Value calculated from the total and completed number of sub-level tasks

Percent

Account_Tactic_vod


Percent

Account_Tactic_vod

Share_With_vod Share With Used to facilitate record sharing among Account Team Members. Team Members whose Role matches any of the selected values will have visibility to the record.

Picklist (Multi-Select)

Action_Item_vod

Account_vod Account Lookup

Action_Item_vod

Account_Plan_vod Account Plan Lookup


Veeva Systems Confidential Information (For use only by licensed Customers of Veeva Systems)


Action_Item_vod

Account_Tactic_vod Activity Lookup

Action_Item_vod

Assignee_vod Assignee User who the Action Item has been assigned to

Lookup

Action_Item_vod

Completed_By_vod Completed By Lookup

Action_Item_vod

Completed_Date_vod Completed Date Date

Action_Item_vod

Description_vod Description Text

Action_Item_vod

Due_Date_vod Due Date Date

Action_Item_vod

Share_With_vod Share With Used to facilitate record sharing among Account Team Members. Team Members whose Role matches any of the selected values will have visibility to the record.

Picklist

Action_Item_vod

Start_Date_vod Start Date Date

Action_Item_vod

Status_vod Status Picklist

Action_Item_vod

Plan_Tactic_vod Strategy Lookup

Call2_vod Ship_To_Address_Text_vod

Ship To Address The Ship to Address Formula field corresponds to a formatted version of the Ship to Address fields. This value is leveraged in the case that the referenced Ship to Address has been deleted. This field should not be added to a Page Layout.

Formula




Clm_Presentation_vod

Control_Visibility_vod Control Visibility If Product is selected, then Detail Group field is ignored when determining CLM content visibility. If Detail Group is selected, then Product field is ignored when determining CLM content visibility.

Picklist

Consent_Type_vod

Opt_Out_Disclaimer_Text_vod

Opt Out Disclaimer Text The text that will be displayed on the review panel for opt outs.

Long Text Area

Consent_Type_vod

zvod_Consent_Activity_Tracking_vod

zvod_Consent_Activity_Tracking_vod

The text displayed on the review panel for activity tracking. A checkbox will be added before the text that is stored in this field.

Long Text Area

Consent_Type_vod

zvod_Opt_Out_Consent_Line_vod

zvod_Opt_Out_Consent_Line_vod

Veeva markup field that drives the visibility and page layout location of the consent changes on review panel for opt outs of the record type.

Checkbox

EM_Attendee_vod

Network_ID_vod Network ID The Network account acting as the attendee

Text

EM_Attendee_vod

Walk_In_Status_vod Walk-In Status Used to track the status of walk-in attendees at an event.

Picklist

EM_Catalog_vod

Vault_Link_vod Vault Link Stores the document's Vault Doc ID URL

EM_Event_Action_vod

Add_Delegates_to_Event_vod

Add Delegates to Event Used to add a delegate approver to the event team

Picklist

EM_Event_History_vod

Delegate_Approver_vod Delegate Approver The user selected as the delegate approver

Lookup

EM_Event_vod

Vault_External_ID

EM_Event_vod

Vault_Binder_path




Event_Attendee_vod

Child_Account_vod Child Account Lookup to the child account for the attendee

Lookup

Event_Attendee_vod

Network_ID_vod Network ID The Network account acting as the attendee

Text

Event_Attendee_vod

Walk_In_Status_vod Walk-In Status Used to track the status of walk-in attendees at an event.

Picklist

Events_Management_Settings_vod

BULK_ADD_ATTENDEE_vod

Bulk Add Attendee Determines whether the bulk add feature can be used with the Attendee Selection page.0: Feature is disabled 1: Feature is enabled

Number

HTML_Report_vod

Phone_vod Phone Check this field to configure MyInsights visualization for phone form factor

Checkbox

Inventory_Monitoring_Line_vod

Line_Rank_vod Line Rank Stamps the sequence in which multiple Inventory Monitoring Lines are stored for a same product

Number

Medical_Event_vod

Country_vod Country Country where an event takes place. Used to define event-level rules.

Lookup

Medical_Inquiry_Fulfillment_Response_vod

Address_Line_1_vod Address Line 1 The Address Line 1 of the Address captured for Medical Inquiry Fulfillment Response.

Text


Address_Line_2_vod Address Line 2 The Address Line 2 of the Address captured for Medical Inquiry Fulfillment Response.

Text


City_vod City The City of the Address captured for Medical Inquiry Fulfillment Response.

Text





Email_vod E-Mail Email value captured for Medical Inquiry Fulfillment Response.

E-Mail


Fax_Number_vod Fax Number Fax value captured for Medical Inquiry Fulfillment Response.

Phone


Country_vod Country The Country of the Address captured for Medical Inquiry Fulfillment Response.

Picklist


Phone_Number_vod Phone Number Phone Number value captured for Medical Inquiry Fulfillment Response.

Phone


State_vod State The State of the Address captured for Medical Inquiry Fulfillment Response.

Picklist


Zip_vod Zip The Zip code of the Address captured for Medical Inquiry Fulfillment Response.

Text


zvod_MIFR_Delivery_Method_vod

zvod_MIFR_Delivery_Method_vod

The zvod_MIFR_Delivery_Method_vod field represents the special VoD Control that will display the filtered Addresses, E-mail Addresses, Phone Numbers, and Fax Numbers for the Account. Additionally, display a check box to control whether a

Checkbox




new value can be entered rather than selecting one of the above values.

Multichannel_Activity_vod__c

EM_Event_vod EM Event Indicates which Event Management record the activity is associated with

Lookup

Multichannel_Consent_vod

Activity_Tracking_vod Activity Tracking Consent The text that the Account consented for activity tracking, from the review panel.

Long Text Area

Multichannel_Consent_vod

Opt_Out_Disclaimer_Text_vod

Opt Out Disclaimer Text The disclaimer text that was shown to the Account, when opt out was captured.

Long Text Area

Order_vod Last_Inventory_Monitoring_Date_vod

Last Inventory Monitoring Date

Pulls the last Inventory Monitoring date (Inventory_Monitoring.Inventory_Monitoring_Date_vod__c) into the Order Header

Date

Order_vod zvod_Free_Good_Splitting_vod

zvod Free Good Splitting marker field to allow users to manually allocate Free Goods per Delivery during order splitting

Checkbox

Plan_Tactic_vod


Percent

Preferences_vod

Last_Map_Scheduler_Account_List_vod

Last Map Scheduler Account List

This field is used by the system to read/write the last selected list/view on the Map view of My Schedule.

Text

Preferences_vod

Last_Map_Scheduler_Bookmark_vod

Last Map Scheduler Bookmark

This field is used by the system to read/write the last selected Bookmark on the Map view of My Schedule.

Text

Question_Response_vod

Condition_vod Condition Copied from Survey Questions. Text


Inactive_Condition_vod Inactive Flag This flag is true if a child questions condition is not met and therefore the question is not visible.

Check box





Source_ID_vod Source ID Copied from Survey Questions. Text

Remote_Meeting_vod

Attendance_Report_Process_Status_vod

Attendance Report Process Status

Indicates the status of retrieving the attendance report

Picklist

Sent_Email_vod

Activity_Tracking_Mode_vod

Activity Tracking Mode The field that determines what kind of activity tracking is done on the email.

Picklist

Sent_Email_vod

Email_Source_vod Email Source Stores the object and field API names of the email.

Text

Sent_Email_vod

VExternal_Id_vod VExternal Id External id to determine which Sent Email to write the anonymous Email Activity for.

Text

Sent_Message_vod

Account_vod Account Lookup

Sent_Message_vod

Capture_Datetime_vod Capture Datetime Date/Time

Sent_Message_vod

Content_vod Content Content Lookup

Sent_Message_vod

Delivered_Datetime_vod Delivered Datetime Delivered Datetime Date/Time

Sent_Message_vod

Detail_Group_vod Detail Group Detail Group Lookup

Sent_Message_vod

Last_Open_Datetime_vod

Last Open Datetime Last Open Datetime Date/Time

Sent_Message_vod

Opened_vod Opened Opened Number

Sent_Message_vod

Product_vod Product Product Lookup

Sent_Message_vod

Sent_Datetime_vod Sent Datetime Sent Datetime Date/Time




Sent_Message_vod

Service_Account_vod Service Account Service Account Lookup

Sent_Message_vod

Status_vod Status Status Picklist

Sent_Message_vod

Template_vod Template Template Lookup

Sent_Message_vod

Territory_vod Territory User's territory Text

Sent_Message_vod

Total_Duration_vod Total Duration Total Duration Number

Sent_Message_vod

Total_Interacts_With_Content_vod

Total Interaction Total Interaction Number

Signature_Page_vod

Signature_Page_vod Signature Page The Signature page for which the Disclaimer is used.

Picklist

Survey_Question_vod

Condition_vod Condition Holds the display condition for a question related to branching. If the condition is met, the question will display.

Text

Survey_Question_vod

Source_ID_vod Source ID This field is used to set an identifier on parent questions. This field is referenced in the branching condition logic.

Text

Survey_Target_vod

Employee_Comment_vod

Employee Comment Stores the Employee Comment response. Long Text Area

Survey_vod Enable_Employee_Comment_vod

Enable Employee Comment Copied from Survey_vod when Survey Target header is created.

Picklist

VMobile_Object_Configuration_vod

Device_vod Device This determines the Client Device. A blank value is interpreted as Tablet_vod.

Picklist

Veeva_Settings_vod

LAST_INVENTORY_MONITORING_TYPE_vod

Last Inventory Monitoring Type

Setting for defining which Inventory Monitoring type will be used to define the last IM record to be used to run store-

Text




check driven Orders. Value should be the literal match of the Inventory Monitoring RecordType Name.

Veeva_Settings_vod

CONTENT_ACKNOWLEDGEMENT_TEMPLATE_vod

Content Acknowledgement Template

The format of the generated Content Acknowledgment receipt can be configured by modifying the HTML text contained within this setting.

Text

Table 8: 18R3 New Fields

18r3 release notes - docs.veevacrm.comdocs.veevacrm.com/releasenotes/veeva crm 18r3 release...

Documents