19R1 Release Notesdocs.veevacrm.com/ReleaseNotes/Veeva CRM 19R1... · as the Business_Professional_vod accounts Call Sampling iPad and Online: The address and Sample Indicator associated

CRM 19R1 Release Notes

April 2019

Veeva CRM 19R1 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 .............................................................................................................................................. 3

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

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

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

Core.......................................................................................................................................... 5

Events Management ................................................................................................................ 6

Multichannel ............................................................................................................................ 7

New in Veeva CRM 19R1................................................................................................................. 9

Sunrise on Windows ................................................................................................................ 9

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

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

Account Deep Linking ............................................................................................................ 10

Veeva ID on Accounts ............................................................................................................ 11

Call Reporting ............................................................................................................................ 11

Display Order for Call Objectives ........................................................................................... 11

Displaying Account Identifiers and Addresses in Call Location ............................................. 13

Stamping the Business Account on the Call .......................................................................... 15

Call Sampling ............................................................................................................................. 15

Sampling on iPhone ............................................................................................................... 15

Medical Events .......................................................................................................................... 18

Creating Calendar Reminders for Medical Events Invites ..................................................... 18

Order Management ................................................................................................................... 19

Planograms in Accounts and Inventory Monitoring .............................................................. 19

Payment Terms per Delivery ................................................................................................. 21

Events Management ..................................................................................................................... 23

Delegate Approvers ............................................................................................................... 23

Creating Calendar Reminders for Events Management Invites ............................................ 25

SAP Concur Data Centers ....................................................................................................... 25

SAP Concur Auto-Add to Expense Setting ............................................................................. 27

Integration .................................................................................................................................... 27

Network Integration .................................................................................................................. 27

Creating Unverified Account by Record Types ...................................................................... 27

Medical CRM ................................................................................................................................. 28

Key Medical Insights Restricted Words ................................................................................. 28

Configurable Lookups in Key Medical Insights ...................................................................... 30

Multichannel ................................................................................................................................. 30

Approved Email ......................................................................................................................... 30

Approved Email Restricted Words Enhancement ................................................................. 30

CLM ............................................................................................................................................ 31

WKWebView Support Loading Local Files ............................................................................. 31




3

Consent Capture ........................................................................................................................ 32

Checking Consent at the Email Template Level .................................................................... 32

Engage ....................................................................................................................................... 33

Remote Meeting Indicator .................................................................................................... 33

Engage Webinar ........................................................................................................................ 35

Displaying Webinar Links and Codes ..................................................................................... 35

Engage Webinar Web Client .................................................................................................. 36

Multichannel Cycle Plan ............................................................................................................ 37

Edit Product Goals by Priority in a Single Call Channel ......................................................... 37

Approved WeChat ......................................................................................................................... 37

Approved WeChat Notifications ............................................................................................ 37

Approved WeChat Dashboard ............................................................................................... 38

Parity ............................................................................................................................................. 39

Core CRM ............................................................................................................................... 39

Scheduling and Planning ........................................................................................................ 40

Revision History ............................................................................................................................ 41

Platform/Enablement ................................................................................................................... 42

Appendix A: New Objects ............................................................................................................. 43

Appendix B: New Fields ................................................................................................................ 44

Figures

Figure 1: Call Objective Display Order .......................................................................................... 13

Figure 2: Account Identifiers in Call Location ............................................................................... 14

Figure 3: iPhone Sampling ............................................................................................................ 18

Figure 4: Lock Icon After Signing ................................................................................................... 18

Figure 5: Planogram ...................................................................................................................... 20

Figure 6: Planogram in Account Partner ....................................................................................... 21

Figure 7: Configuring Delegate Approvers .................................................................................... 24

Figure 8: The SAP Concur Data Center.......................................................................................... 26

Figure 9: The Concur Data Center Picklist..................................................................................... 26

Figure 10: The Include user as an attendee by default check box ............................................... 27

Figure 11: iPad My Schedule ......................................................................................................... 34

Figure 12: Online Timeline ............................................................................................................ 35

Figure 13: Engage Webinar Web Client ........................................................................................ 37

Tables

Table 1: iPhone Sampling VMOCs ................................................................................................. 16

Table 2: Request Receipt iPhone VMOCs ..................................................................................... 16

Table 3: Platform/Enablement ..................................................................................................... 43




4

Table 4: 19R1 Objects ................................................................................................................... 43

Table 5: 19R1 New Fields .............................................................................................................. 48




5

Introduction

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

Highlights of this Release

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

• Survey Branching Support on iOS – quickly gather detailed responses to more comprehensive surveys through the use of dependent questions

• Approved Email - includes indicating exact string matches and support for defining more restricted words and the ability to indicate if consent should be checked for by email template

• iPhone Features - includes sampling and promotional materials with signature capture, survey branching, and send to maps

• Windows Sunrise - upgrade to a unified user experience on Veeva CRM across all mobile devices

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

User Visible Changes

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

Sunrise

• Windows: A message will display to indicate a new version of CRM on Windows is available with the 19R1 release

• Users who installed the Windows Sunrise Evaluation version need to delete that version and install the 191.7.0 version. There is a new signing certificate for Veeva CRM on Windows.

Core

Accounts

• iPad and Windows: The Account Overview Panels are now accessible from the Sunrise Bar instead of from the top of the Timeline View

• iPad: Users can now view additional historical data and planned activity in the Timeline by using the swipe up or down gesture at the bottom or top of the Timeline. Three months of additional data loads at a time.




6

• iPad: Engage for Portals activities on the Timeline now display only the first five lines. Additional lines are viewed by selecting the MC activity record.

• iPhone: The More Actions icon on the Account Detail page replaces the Create a Call icon if more than one action is available. If only the Record a Call action is available, the new handshake icon displays.

• Online: Custom lookup fields are now editable in the Call Objectives section of the Call Report

Call Reporting

• iPad and Online: Additional account identifiers and addresses now display when selecting a Call Location if users have FLS permissions

• iPad and Windows: When the DISABLE_CALL_LOCATION_NONE_vod Veeva Setting is disabled and only one location exists for the account, the Select Location popup does not display, and the call report automatically locks the one valid location

• All: When a call is made with a Business_Professional_vod account, The All Accounts section on the Add Attendees page only displays accounts with the same Primary Parent as the Business_Professional_vod accounts

Call Sampling

● iPad and Online: The address and Sample Indicator associated with attendees added to

group calls now display based on the following logic:

○ If the account has a Preferred Address in the same state as the call, that address displays

○ If not, the account’s Primary Address displays if it is in the same state as the call ○ If not, the first address associated with the account in the same state as the call

displays ○ If the account does not have an address in the same state as the call, the above

logic applies regardless of the state of the address ● iPad, iPhone: The icons on the Swap Signee page are now the same icons as on the Call

Report

Samples Management

• Online: Users can now search for specific order lines using the search bar in the Inventory Order Lines section of an Inventory Order

• Online: Users can now sort the columns of the Inventory Order Lines section of an Inventory Order

Events Management

• Windows: The Meal_Opt_In_vod field must now be placed on every Event_Attendee_vod object page layout associated with a record type using Meal Opt-in

• iPad: When manually entering a walk-in attendee from the Attendee Reconciliation screen, picklist fields now display their default values.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Call_Reporting/Configuration/Configuring_Call_Location.htm




7

Note: The Status value is still controlled by the Walk_In_Attendee_Statuses_vod field on the Event_Rule_vod object and the Meal Opt In value must still be set by the user.

Multichannel

Approved Email

• Thumbnails of newly added images now display on the Image Selection page of the BEE Email Template Editor

• All: Approved emails containing the {{addToCalendar}} token now display datetime tokens {{Call2_vod__c.Call_Datetime_vod__c}} etc., in the user’s locale format

Consent Capture

● iPad: A gray background now displays on Consent Capture channels where no action has

been taken

● iPad and Online: Channel source labels now display when capturing consent

● iPad and Online: Channel sources now stamp on the Multichannel Consent record

Engage Meeting

● When an HCP joins a meeting, their video is disabled by default. After joining the meeting, the HCP can enable or disable their video camera in the app.

● The Engage HCP Web Client no longer displays the Original Size button in Engage

Meetings. This ensures all shared content remains in view during the meeting.

● When an iPad user selects the Share button in the Meeting Options screen, a message

displays for the HCP that the host has started screen sharing as the screen share loads.

Key Medical Insights

• Online: The Save button now displays before the Submit button

Multichannel Cycle Plan

• iPad: Several elements in the My Plan tab, for example, the display of the Last Calculated and Days Remaining values now follow the Sunrise user interface. The Plan Name is now a drop-down in the title bar replacing the Change Plan button.

Scheduling and Planning

• iPad: Users can now view additional historical data and planned activity on the Timeline View by using the swipe up or down gesture at the bottom or top of the Timeline. Three months of additional data loads at a time.

• iPhone: Users can now push an address from the Veeva CRM app to Google Maps, Apple Maps, or Waze

Other

• iPad: The Date and Date time dialog Save label is now Done.

http://vaulthelp2.vod309.com/wordpress/applications/promotional-materials-edition/approved-email/bee-email-template-editor/

http://vaulthelp2.vod309.com/wordpress/applications/promotional-materials-edition/approved-email/bee-email-template-editor/




8




9

New in Veeva CRM 19R1

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.

Sunrise on Windows

Veeva CRM on Windows customers are required to upgrade to Windows 10 Build 16299 (Fall Creators Update, version 1709) in order to install Veeva CRM 19R1. With the release of the Windows Sunrise UI, and the upgrade to Windows 10 and the Universal Windows Platform (UWP) application on Veeva CRM on Windows in 19R1, users need to install a brand-new application. After the Windows Sunrise UI upgrade is released to orgs, users need to:

1. Perform a last sync on the classic application in 18R3. 2. Install the new application 3. Perform an initial sync on Veeva CRM 19R1 in order to use Windows Sunrise UI.

To configure the link and install the new application:

1. Log into Veeva CRM (Online). 2. Navigate to Application Setup. 3. Select Home. 4. Select Home Page Layouts. 5. Select the page where you want to display the link for Veeva CRM on Windows Modern. 6. Select Edit. 7. Select the Veeva CRM on Windows check box. 8. Select the side of the page you want the link to display. 9. Select Save. 10. Ensure users have access to the WinMod_Install_vod VisualForce page. 11. Log into the Veeva CRM Online version on your Windows 10 device through a web

browser. 12. Navigate to the page you selected in Step 5. 13. Select the Veeva CRM on Windows Installation link. 14. Select Install Now.

Note: Users who have the link for the evaluation version configured on their home page need

to follow the above instructions for the new sandbox version. The old link will no longer work.

Windows Content Testing

In 19R1, Veeva CRM on Windows will begin utilizing the Universal Windows Platform (UWP) framework in Windows 10. In this framework, the WebView technology displaying CLM and MyInsights content will use the Microsoft Edge (EdgeHTML) rendering engine. This update is required and is enabled by default for all Windows CRM app users. We recommend customers




10

and their agencies review all CLM content and MyInsights visualizations using the Windows Content Test Version.

Core CRM

ACCOUNTS

Account Deep Linking Users can now navigate directly to an account profile in Veeva CRM from an external application. When users rely on an external enterprise application to access specialized information about HCPs, they need to move between the external application and Veeva CRM to maximize their time. Now, they can do that automatically without having to sign into Veeva CRM and search for the specific HCP. For example, Sarah Jones’ company uses a reporting tool built on an external business intelligence platform. Sarah notices a downward sales trend for Dr. Ackerman in the reporting tool, and she needs check information in CRM to plan what steps to take for the account. Sarah selects Dr. Ackerman’s account from the external app and opens it directly in CRM. From the Account Timeline, she notices interactions with the account have slowed down and schedules more calls with the account in the upcoming weeks. Note: This feature is available for the Accounts object only.

Use

Veeva CRM supports a custom URL used by external developers to link users to a specific account record. The URL contains the 18-character CRM account ID. For example, veeva://Account/001j0000007Ir50AAC Developers can include this link an any external application. If a user previously signed into Veeva CRM and then selects an account from the external application, the default account view displays if the last-viewed screen in CRM was not in edit mode. Once in CRM, selecting the Back button displays the last viewed page. For example, after navigating to Dr. Ackerman’s account in CRM from the external reporting tool, Sarah selects the Back button from the Account Timeline to display the Account Details page for Verteo Biopharma. This page displays because it was the last page Sarah viewed before navigating to the external application. Note: The default account view is the tab configured to display first on the Account toolbar. For

more information, see Default Account View.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Accounts/Components/DefaultAccountView.htm




11

If the last-viewed CRM screen was in edit mode, an error message displays if data losses could occur. Selecting OK removes the error message and displays the current CRM screen. Note: Edit screens include both main screens and popups.

If a user selects an account not available in CRM, or an invalid link, an error message displays, and the last viewed CRM screen displays. If a user selects an account but is not signed in to Veeva CRM, the Login screen displays. This feature is enabled by default and is available on the iPad and iPhone platforms.

Veeva ID on Accounts

A new field, Veeva_ID_vod, is being introduced on the Account object. This unique, global Veeva ID helps with various use cases, for example, the identification of accounts across multiple orgs. The Veeva ID is the same Veeva ID leveraged by Veeva OpenData and Veeva Data Partners, making it easier to connect those data sources. An additional license is not required to use the Veeva ID in Veeva CRM and connected systems. Veeva is planning to begin stamping the Veeva ID during the first 19R1 patch starting with the US region, and continue to other regions during subsequent patches. This field is enabled by default.

CALL REPORTING

Display Order for Call Objectives

Administrators can now control the display order of Call Objectives on the call report. This enhances the Call Objective experience by displaying Call Objectives in logical or sequential orders. For example, Sarah Jones visits Dr. Clinton Ackerman and performs various tasks including speaking to him about Cholecap’s efficacy, asking if he needs any further samples, etc. When Sarah creates the call report to record this interaction, she reviews the available Call Objectives displaying in order of importance. This enables her to maximize the impact of her visit with Dr. Ackerman.

Configuration

To enable this feature:

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

Display_Order_vod field on the Call_Objective_vod object.




12

2. Grant end-users FLS edit permission to the Display_Order_vod field on the

Call_Objective_vod object if Display Order is intended to be used with Recurring Call

Objectives.

3. Place the Display_Order_vod field on the appropriate Call_Objective_vod object page

layouts. This step is optional and displays the Display_Order_vod code next to each Call

Objective.

4. Populate the Display_Order_vod field on all appropriate Call_Objective_vod records

with the display value.

Use

Call_Objective_vod records sort in ascending alpha-numeric order on the call report and in the Add Other modal. For example, if seven Call Objectives contain Display_Order_vod fields of 1, 5, 10, A1, C, B2, and 1a, the displayed order is:

● 1

● 1a

● 5

● 10

● A1

● B2

● C




13

Figure 1: Call Objective Display Order

Call Objectives with identical Display_Order_vod fields sort alphabetically based on record type, then by name. Note: If the Display_Order_vod field is empty, the associated Call Objective displays at the

bottom of the list of objectives.

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

Displaying Account Identifiers and Addresses in Call Location

Administrators can now configure the Call Location to display an account’s address and identifier. This makes it easier for end-users to select the correct call location when multiple accounts have the same name. For example, Dr. Clinton Ackerman is affiliated with Newton Memorial Hospital, which has two locations in the same state. Sarah Jones’s org is configured so each location of Newton Memorial Hospital is a separate account. Sarah visits Dr. Ackerman at one of these locations. When she creates the Call Report to record this interaction, she selects the call location. Since there are multiple Newton Memorial Hospitals in the same state as the call, Sarah uses the address and the account identifier to select the correct call location.

Configuration





14

1. Enable Call Location.

2. Enable Identifiers on the Call Report.

3. Grant end-users FLS read permission to the following Address fields:

● Address_Line_1_vod

● Address_Line_2_vod

● City_vod

● State_vod

● Zip_vod

Use

When users select the Select Location picklist, the list of available business accounts displays with their account identifiers and addresses.

Figure 2: Account Identifiers in Call Location

Displayed Address Logic

The following logic determines which address displays for each account:

● If the account has a Preferred Address in the same state as the call, that address displays

● If not, the account’s Primary Address displays if it is in the same state as the call

● If not, the first address associated with the account in the same state as the call displays

If the account does not have an address in the same state as the call, the above logic applies regardless of the state of the address.


https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Call_Reporting/Components/Attendees.htm





15

This feature is available on the Online and iPad platforms.

Stamping the Business Account on the Call

The value of the zvod_Business_Account_vod field now stamps on the call. This ensures if the business account name changes, the account name at the time of the call is properly recorded.

Configuration

To configure this feature, grant all users FLS edit permission to the Location_Text_vod field on the Call2_vod object.

Use

The value of the zvod_Business_Account_vod field automatically stamps on the Location_Text_vod field when the call is saved, signed, or submitted.

CALL SAMPLING

Sampling on iPhone iPhone users can now disburse Samples and Promotional Items. See Configuring Samples Management for more information.

Configuration

To enable this feature, activate the following VMOCS with the Device type of iPhone:

VMOC Sync Type

WHERE Clause Lookup

Account_Authorization_vod Full Sync

WHERE Account_vod__c IN (SELECT Id FROM Account)

N/A

Country_vod Full Sync

N/A N/A

Multichannel_Consent_vod Full Sync

N/A Account_vod

Sample_Limit_vod Top Level

WHERE Account_vod__c IN (SELECT Id FROM Account)

Account_vod

Sample_Lot_vod Full Sync

N/A N/A

Sample_Lot_Item_vod Full Sync

N/A N/A

Samples_State_Credential_Settings_vod Full Sync

N/A N/A

Samples_State_Settings_vod Full Sync

N/A N/A

https://crmhelp.veeva.com/doc/Content/CRM_topics/Sample_Management/ConfiguringSamples/ConfiguringSampleManagement.htm




16

Sample_Transaction_vod Full Sync

N/A N/A

Table 1: iPhone Sampling VMOCs

Section Signal Support

The following section signals are supported for Call Sampling on the iPhone platform:

• --nas

• --nb

• --nhvp

• --no

• --np

• --npdma

• --ns

• --nsl

• --nslns

• --sbl

Unsupported section signals are ignored.

Approved Email Receipt Support

iPhone users can also send Sample Receipts using Approved email. To configure this feature:

1. Ensure Email Receipts for Signature Transactions is configured. 2. Activate the following VMOCs with the device type of iPhone:

VMOC Sync Type

WHERE Clause

Approved_Email_Settings_vod Full Sync

WHERE SetupOwnerId in (@@VOD_SF_PROFILEID@@, @@VOD_MY_ORGID@@)

Approved_Document_vod Full Sync

N/A

Multichannel_Route_vod Top Level

N/A

Sent_Email_vod Top Level

WHERE Account_vod__c IN (SELECT Id FROM Account) AND CreatedDate<=LAST_N_DAYS:90

User_Detail_vod Full Sync

Where User_vod__c = @@VOD_SF_USER_ID@@

Attachment Full Sync

WHERE Name LIKE ‘Signature_Graphic%’

Table 2: Request Receipt iPhone VMOCs

Signature Page Support

https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/Approved_Email/Using%20Approved%20Email/EmailReceiptsforSignatureTransactions.htm




17

The iPhone platform also supports capturing signatures for samples. To enable this feature, activate the following Signature_Page_vod VMOC with a device type of iPhone:

Use

Disbursing Samples and Promotional Items

Users can disburse samples and promotional items on the iPhone platform. From the call report:

1. Navigate to the Samples and Promotional Items section. 2. Select the appropriate button (for example, Add Sample). 3. Select the appropriate Product. 4. Select the appropriate Item. 5. Select the appropriate Lot, if applicable. 6. Select the appropriate Quantity. 7. Select Next. 8. Select either Done or Done and New.

Signature Capture

After the sample is disbursed, capture the signature of the HCP:

1. Select the More Actions button. 2. Select Sign. 3. Select the correct information for the following sections:

• Display Image – If the Signature Graphic Picklist feature is enabled, users can select the arrow icon to select the appropriate image to display with the signature

• Language – If the Disclaimer based on Language feature is enabled, the user can select the appropriate language to use

• Account Details – The user can swap the signer or the ship to address

• Receipt – Users can select if the signee should receive a receipt for the sample, as well as selecting the appropriate email for the receipt if Approve Email receipts is enabled

4. Select Start.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Call_Reporting/Signatures/Marketing_Banner%20.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Call_Reporting/Signatures/Disclaimers.htm

https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Call_Reporting/Signatures/SignaturePages.htm#kanchor255

https://crmhelp.veeva.com/doc/Content/CRM_topics/Sample_Management/UsingSamples/ShiptoBusLoc.htm






18

Figure 3: iPhone Sampling

Select the Lock icon to display the screen verifying the signature and receipt (if enabled).

Figure 4: Lock Icon After Signing

Once the information is verified, select Done to return to the Call Report.

MEDICAL EVENTS

Creating Calendar Reminders for Medical Events Invites

When users send Medical Events invitations via Approved Email, they can now include an .ICS file attachment. This file attachment allows recipients to add a calendar entry for the event on common calendar applications.




19

Configuration

The .ICS file automatically pulls in data from the Medical Event. The user sending the email must have a minimum of read permission to the Start_Time_vod field on the Medical_Event_vod object for the .ICS file to generate. The following fields pull in optionally if the user sending the email has FLS read permission and the fields contain a value:

• End_Time_vod field on the Medical_Event_vod object

• Location_vod field on the Medical_Event_vod object

Use

To use this feature, Approved Email integration and end users must have the ability to send Medical Event invitations with Approved Email. To provide recipients with a calendar reminder, content admins insert the {{addToCalendar}} token anywhere in the Email Template. This token attaches an .ICS (iCalendar) file to the Medical Event email invitation. Content Admins can add this token to the Email Template manually or with the BEE Editor. If an event is rescheduled, or other key attributes of the event transmitted in the .ICS file are updated, the email template containing the {{addToCalendar}} token must be resent. When the .ICS attachment is opened, the existing calendar entry on the recipient’s calendar is updated to reflect the changes.

ORDER MANAGEMENT

Planograms in Accounts and Inventory Monitoring

A planogram is a visual representation of a product display, including shelves, pegboards, and hanging bars, in a pharmacy or grocery store. Planograms are used by sales reps when visiting a retail customer to compare actual and contract product placement (number of facings, position on shelf, and layer). Comparing the display to the planogram identifies missing or misplaced products. This saves the user time by being able to access and compare the planogram in CRM for each customer as needed. For example, Sarah Jones is visiting Verteo Pharmacy to check product placement and to determine if there are any products needing reorder. She compares the current display to the planogram accessed from the customer’s Account Partners page. She notes the areas of the current display that are not compliant with the contract. She uses this information to discuss corrections with the pharmacist.




20

Figure 5: Planogram

Configuration

To enable this feature for administrators:

1. Grant Create permission to the following objects:

• Planogram_vod

• Planogram_Line_vod 2. Grant FLS edit permission to all fields on the Planogram_vod object. 3. Grant FLS edit permission to all fields on the Planogram_Line_vod object. 4. Grant FLS edit permission to the following fields on the Product_vod object:

• Height_vod

• Width_vod 5. Grant FLS edit permission to the following fields on the Account_Partner_vod object:

• Inventory_Monitoring_Type_vod

• Planogram_vod 6. Enable the Planogram_vod record type on the Account_Partner_vod object. 7. Grant FLS edit permission to the Inventory_Monitoring_Type_vod field on the Account

Partner object if the planogram links to only one Inventory Monitoring record type.

If using custom Inventory Monitoring record types, picklist values for the

Inventory_Monitoring_Type_vod field must match the record type name on the

Inventory_Monitoring_vod object.

To enable this feature for users:

1. Grant FLS read permission to all fields on the Planogram_vod object. 2. Grant FLS read permission to all fields on the Planogram_Line_vod object. 3. Grant FLS read permission to the following fields on the Product_vod object:

• Height_vod

• Width_vod




21

4. Grant FLS read permission to the following fields on the Account_Partner_vod object:

• Inventory_Monitoring_Type_vod

• Planogram_vod

Grant edit permission if the user can create relationships between Accounts and Planograms.

5. Enable the Planogram_vod record type on the Account_Partner_vod object. 6. Grant FLS read permission to the Inventory_Monitoring_Type_vod field if Account

Partner is only specific for some Inventory Monitoring record types.

Use

Users can access a planogram from the Inventory Monitoring or Account Partners page if a planogram is associated to the account.

Figure 6: Planogram in Account Partner

If more than one planogram exists for an account, users can select from a list on the Inventory Monitorings page. The default planogram displays. If a default planogram is not set, the last updated planogram displays. This feature is available on the iPad platform.

Payment Terms per Delivery




22

Users are now able to define payment terms for Line Delivery Splitting when an order is split into more than one delivery. This allows for better negotiations for orders. For example, Sarah Jones creates an order for a pharmacy and splits the delivery to two dates. For the first delivery, she negotiates payment terms of 30 days, and 45 days for the second delivery in the order entry screen.

Configuration

To enable Payment Terms per Delivery admin users: Ensure Pricing Rule administration is enabled.

1. Grant FLS edit permission to the Delivery_Order_vod field on the Pricing_Rule_vod

object.

2. Add this field to the page layout for Payment Terms.

3. Grant FLS read permission to the Delivery_Payment_Rule_vod and grant FLS edit

permission to the Delivery_Payment_vod fields on the Order_vod object.

Mode 3 for Line Splitting is not supported with this feature.

To enable Payment Terms per Delivery for end users:

1. Ensure Order Management is enabled.

2. Ensure users have access to the Payment Terms rule record type.

3. Grant FLS read permission to the Delivery_Order_vod field on the Pricing_Rule_vod

object.

4. Grant FLS read to the zvod_Delivery_Payment_vod and

zvod_Delivery_Payment_Rule_vod fields and place them on the page layout in a

section dedicated to Line Splitting fields on the Order header.

5. Grant FLS edit to the Delivery_Payment_Rule_vod and the Delivery_Payment_vod

fields on the Order object. Optionally, place on the order header page layout.

Use

To use this feature, the pricing rule admin needs to:

1. Create a new pricing rule of type Payment_Terms_Rule_vod.

2. Enter the rule criteria and ensure the Product field does not have a value.

3. Select the Delivery Payment check box.

4. Save.

Only Total Order Payment Terms is supported at the delivery level.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Order_Management/OrderEntry/LineDeliverySplitting.htm




23

This feature is available on the iPad platform.

Events Management

Delegate Approvers

Events Management workflows now support delegate approvers, users authorized by the administrator to approve an event on behalf of another approver. This enables approval of events by a user other than the manager of the event organizer in cases where the event organizer is unable to approve. When enabled, this feature automatically adds all approver delegates to the event as event team members when the event is submitted for approval. For example, Sarah Jones plans an event involving an HCP. Her company requires all events involving an HCP be reviewed and approved by her manager. When Sarah submits the event for approval, both her manager and her manager’s delegate are added to the event team with the Approver role. Sarah’s manager is on vacation, so the delegate reviews and approves the event in place of Sarah’s approver.

Configuration

Prerequisites

To enable this feature, the following prerequisites are required:

1. Ensure the event approval process is defined using an SFDC workflow.

2. Navigate to the Manager Approval step of the event approval process.

3. Navigate to the Select Assigned Approver section.

4. Select Automatically assign using the user field selected earlier.

5. Select The approver’s delegate may also approve this request check box.




24

Figure 7: Configuring Delegate Approvers

To configure Delegate Approver Support for Events Management:

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

Add_Delegates_to_Event_vod field on the EM_Event_Action_vod object.

2. Grant administrators FLS read permission to the Delegate_Approver_vod field on the

EM_Event_History_vod object.

3. Add the Add_Delegates_to_Event_vod field to the appropriate EM_Event_Action_vod

object page layout.

4. Navigate to the appropriate EM_Event_Action_vod record.

5. Select the Add_Delegates_to_Event_vod check box.

Use

Setting Delegates for Users

To specify a delegate for a user:

1. Navigate to Manage Users.

2. Select the appropriate User record.

3. Select Edit.

4. Populate the Delegated Approver field with the appropriate user.

5. Select Save.

Users can automatically add delegate approvals to the event by selecting Yes from the Add_Delegates_to_Event_vod picklist on the associated Event Action that intiates the approval process step.




25

If delegates were added to the event, the Delegated_Approver_vod field on the associated EM_Event_history_vod record automatically stamps with the appropriate user. The team role of the delegate approver is the same as the primary approver. This feature is available on the Online, iPad, and Windows platforms.

Creating Calendar Reminders for Events Management Invites

When users send Events Management invitations via Approved Email, they can now include an .ICS file attachment. This file attachment allows recipients to add a calendar entry for the event on common calendar applications.

Configuration

The .ICS file automatically pulls in data from the Event. The user sending the email must have a minimum of read permission to the Start_Time_vod field on the EM_Event object for the .ICS file to generate. The following fields pull in optionally if the user sending the email has FLS read permission and the fields contain a value:

• End_Time_vod field on the EM_Event object

• Event_Display_Name_vod field on the EM_Event object. (Note: if this field is not populated or the user does not have read permission to the field, the Event’s Name is used as a fallback)

• Location_vod field on the EM_event object

• Webinar_Participant_URL_vod field on the EM_Attendee object

Use

To use this feature, Approved Email integration and end users must have the ability to send Events Management invitations with Approved Email. To provide recipients with a calendar reminder, content admins insert the {{addToCalendar}} token anywhere in the Email Template. This token attaches an .ICS (iCalendar) file to the Events Management email invitation. Content Admins can add this token to the Email Template manually or with the BEE Editor. If an event is rescheduled, or other key attributes of the event transmitted in the .ICS file are updated, the email template containing the {{addToCalendar}} token must be resent. When the .ICS attachment is opened, the existing calendar entry on the recipient’s calendar is updated to reflect the changes.

SAP Concur Data Centers

Company Administrators can now select either the US (North America) or EMEA (Europe) data center from the Concur Integration Admin page. A data center must be selected so transactions from Veeva to SAP Concur so data is transmitted to the correct environment.




26

A Veeva CRM instance can only connect to one data center at a time.

To determine which data center to connect to:

1. Sign into your SAP Concur Solutions account. 2. Select the Service Status link. Your SAP Concur data center displays.

Figure 8: The SAP Concur Data Center

Configuring the SAP Concur Data Center in CRM

Navigate to the Concur Admin page and select the appropriate option from the Concur Data Center Region.

Figure 9: The Concur Data Center Picklist

Use




27

The setting applies to all outbound integrations from Veeva to SAP Concur. When run, the integrations refer to the SAP Concur Data Center Region setting to determine to which data center all outbound expenses should be sent. This setting defaults to US. In the uncommon situation of changing SAP Concur data centers, it is necessary to re-enter the

mappings. This is because the SAP Concur fields, expense types, payment types, and other

configurations will contain different values in the new SAP Concur environment.

SAP Concur Auto-Add to Expense Setting SAP Concur has an expense setting that automatically creates an entry attendee association for the user who created the expense. This setting is managed in SAP Concur and can be enabled or disabled at the expense type level for each expense policy. The Events Management integration with SAP Concur supports this setting.

Figure 10: The Include user as an attendee by default check box

Use

If the Include user as an attendee by default check box is selected, the Events Management SAP Concur integration skips the creation of entry associations that were created in SAP Concur. If the entry association is skipped, it still displays in the transaction log accessible through the Concur Real-Time Administration page in Veeva.

Integration

NETWORK INTEGRATION

Creating Unverified Account by Record Types Users can now create DCR Unverified records by Account record type. Different Account record types may have different permissions or restrictions in Veeva CRM, so this enables flexibility of specifying which Account record types can be created as Unverified while still requiring other accounts to go through the DCR approval process.




28

For example, Sarah Jones visits Dr. Clinton Ackerman, who has recently hired a new nurse and a new radiology technician. Sarah’s org has record types for both nurses and technicians. The Technician record type is configured to be unverified. She creates an account in CRM for the new technician and can immediately capture an email opt-in signature for the technician. However, the new account for the nurse must still go through the DCR approval process.

Configuration


1. Ensure Unverified Records are configured. 2. Grant end-users and the integration user FLS edit permission to the

Network_Create_Unverified_vod field on the Data_Change_Request_vod object. 3. Populate the NETWORK_UNVERIFIED_ACCOUNT_TYPES_vod Network Setting with

which account record types in which countries can be unverified using the following format: <Account Record Type 1>:<List of Countries>;;<Account Record Type 2>:<List of Countries>

Use ALL for record types that can be unverified in all countries.

For example, the following defines in which countries the Professional, Nurse, and Technician record types can be unverified records: Professional:US;;Nurse:FR,DE,IT;;Technican:ALL If the list of record types and countries exceeds 255 characters, populate the setting with a

Veeva Message containing the appropriate information.

Account record types not included in this setting are processed with a DCR before the account is created in Network and CRM. This feature is available on the Online and iPad platforms.

Medical CRM

Key Medical Insights Restricted Words

Administrators can specify if restricted words should be treated as a partial string match or an exact string match. Additionally, administrators can define more restricted words using multiple Veeva Messages. This provides greater control over what words or phrases should be restricted and helps minimize unnecessary restrictions.

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

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

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




29

For example, while Sarah Jones is creating a Key Medical Insight, she types the word Cholecap. An error message displays because the word is a restricted word using an exact string match.

Configuration


1. Navigate to the Veeva Message noted in the Medical Insights Restricted Words Veeva

Setting.

2. Select Edit.

3. Enclose exact string matches in straight double quotes (""). Smart Quotes are not

supported (“”). Partial string matches should not use double quotes.

For example, the following text input into the Veeva Message: awesome;;"10 dollars" sets the word awesome as a partial string match and the phrase 10 dollars as an exact string match.

Spaces, newlines, tabs, and all other forms of whitespace are treated the same.

Exact string matches immediately after punctuation are restricted based on the specific language and platform. For example, the Online and Windows 10 platforms always restrict exact string matches that follow punctuation. On the iPad platform, this restriction is dependent on whether the language of the device regularly contains punctuation preceding a word (for example, Spanish uses the ¿ punctuation before words).

Use

Using Multiple Veeva Messages to Restrict Words

Administrators can define the list of restricted words in a series of Veeva Messages. This enables a list of restricted words larger than the 5000 character limit of a single Veeva Message. To enable this feature:

1. Create all appropriate Veeva Messages containing lists of restricted words.

Veeva Messages must be a unique combination of the Name, Category, and External ID fields.

2. Navigate to the Medical_Insights_Restricted_Veeva_Messages_vod Veeva Setting.

3. Enter the Veeva Messages as a comma-separated list. All Veeva Messages in this setting

must belong to the same category and use this format:

[Name1],[Name2],[Name3];;[Category].




30

For example, the following references three Veeva Messages for the list of restricted words: RESTRICTED,RESTRICTED2,RESTRICTED_jp;;MI

All Veeva Messages used must have the same Language field.


Configurable Lookups in Key Medical Insights Configurable lookup filters and search layouts are supported for some Veeva CRM objects and fields, and now include Key Medical Insights (KMI). See Configurable Lookups for more information. For example, Larry Lakes, an MSL, learns Dr. Ackerman has some safety concerns about Cholecap. Larry creates a KMI. On the page layout there are fields for Person Accounts and Business Accounts. Larry is able to select Dr. Ackerman from the Person Accounts.

Configuration

To configure this feature, ensure Configurable Lookups are configured for the Medical_insight_vod object. This feature is available on the Online, iPad, and Windows platforms.

Multichannel

APPROVED EMAIL

Approved Email Restricted Words Enhancement

Administrators can specify if restricted words should be treated as a partial string match or an exact string match. Additionally, administrators can define more restricted words with multiple Veeva Messages. This provides greater control over what words or phrases should be restricted and helps minimize unnecessary restrictions. For example, while Sarah Jones is writing an Approved Email, she types the word Cholecap. An error message displays because the word cap is a restricted word using a partial match.

Configuration


1. Navigate to the Veeva Message noted in the Approved Email Restricted Words

Approved Email Setting.

2. Select Edit.

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

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




31

3. Enclose exact string matches in straight double quotes (""). Smart Quotes are not

supported (“”). Partial string matches should not use double quotes.

For example, the following text input into the Veeva Message: awesome;;"10 dollars" sets the word awesome as a partial string match and the phrase 10 dollars as an exact string match.

Note: Spaces, newlines, tabs, and all other forms of whitespace are treated the same.

Exact string matches immediately after punctuation are restricted based on the specific language and platform. For example, the Online and Windows 10 platforms always restrict exact string matches that follow punctuation. On the iPad platform, this restriction is dependent on whether the language of the device regularly contains punctuation preceding a word (for example, Spanish uses the ¿ punctuation before words).

Use

Using Multiple Veeva Messages to Restrict Words

Administrators can define the list of restricted words as a series of Veeva Messages. This enables a list of restricted words larger than the 5000 character limit of a Veeva Message. To enable this feature:

1. Create all appropriate Veeva Messages containing lists of restricted words.

Veeva Messages must be a unique combination of the Name, Category, and External ID fields.

2. Navigate to the Approved Email Restricted Words Approved Email Setting.

3. Enter the Veeva Messages as a comma-separated list. All Veeva Messages in this setting

must belong to the same category and use the format

[Name1],[Name2],[Name3];;[Category].

For example, the following references three Veeva Messages for the list of restricted words: RESTRICTED,RESTRICTED2,RESTRICTED_jp;;AE

All Veeva Messages used must have the same Language field.


CLM

WKWebView Support Loading Local Files




32

Apple deprecated UIWebView in iOS 12. Veeva recommends all newly created CLM content be compatible with WKWebView.

As a result of the increased security policies in WKWebView, a new Multichannel setting, Allow Insecure Local File Access, is delivered enabled by default with this release. This setting initiates a local web server on the iPad, allowing Veeva CRM to load local files for CLM content in WKWebView without any CLM content modifications. For example, using AJAX in Javascript to load URLs or to GET files.

Disabling this setting minimizes security risks, however, no alternatives exist for loading local files in WKWebView.

CONSENT CAPTURE

Checking Consent at the Email Template Level

Administrators can control whether consent needs to be checked when using specific Approved Email Templates. This provides greater control when determining when consent is checked. For example, Sarah Jones organizes an Engage Meeting with Dr. Clinton Ackerman and sends an Approved Email with information regarding the meeting. The administrator configures the email template Sarah uses to always check for consent. Sarah has not captured consent from Dr. Ackerman, so she is blocked from sending this email and is prompted to capture consent from Dr. Ackerman before sending the email.

Configuration

To enable this feature: In CRM, grant the Integration user FLS edit permission and end-users FLS read permission to the Consent_Check_vod field on the Approved_Document_vod object. In Vault, grant the Content Creator and Integration user FLS edit to the consent_check__v field on the email_template__v object.

Use

To set consent check requirements for an email template in Vault:

1. Navigate to the appropriate email_template__v record.

2. Populate the consent_check__v picklist with the appropriate value:

The consent_check__v picklist is empty at initial configuration. When this picklist is empty, it

behaves as if Default value is selected.

• Yes – The template always checks for consent regardless of the entry point




33

• No – The template never checks for consent regardless of the entry point. If the template is sent to an account with an Approved_Email_Opt_Type_vod field of Never, the template still does not check for consent.

• Default – The template checks for consent based on the behavior of the relevant Approved Email entry point

The following entry points do not check for consent when Default is selected:

• Engage Meeting

• Medical Inquiries

• Case

• Receipts

• CoBrowse

• Double Opt-in

3. Select Save.

4. Sync with Veeva CRM.

Receipts and Double Opt-In emails always send without checking consent, regardless of the value of the Consent_Check_vod field. Setting the Consent_Check__v field to Yes means the system checks if consent is required to send the email. It does not mean consent is needed to send the email. For example, if a template with the consent_check__v set to Yes is sent to an account whose Consent Type is Opt-in Not Required, the email can be sent even though consent was not captured. Do not edit the Consent_Check_vod field in Veeva CRM as any changes are overridden when

the next sync occurs.

This feature is available on the Online and iPad platforms.

ENGAGE

Remote Meeting Indicator

Veeva Engage Meeting supports scheduling and launching a remote meeting directly from a call. To help distinguish a remote meeting from a standard call, a Remote Meeting Indicator displays on remote meeting calls. This enables users to quickly differentiate remote meetings calls. The Remote Meeting Indicator ( ) displays in the following areas if the corresponding Call2_vod record has a populated Remote_Meeting_vod field:

● Account Timeline

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

https://crmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/Capturing_consent/DoubleOptIn.htm




34

● Call Report

● My Schedule Agenda View

● My Schedule List Scheduler View

● My Schedule Map View

● My Schedule Month View

● My Schedule Week View

The Remote Meeting Indicator may not display based on space constraints. For example, the

indicator does not display in the My Schedule Month View on the Online platform if the Call

Conflict icon displays for that call. In this case, the Remote Meeting Indicator displays when

selecting the record.

Configuration

To enable the Remote Meeting Indicator, ensure users have at least FLS read permission to the Remote_Meeting_vod field on the Call2_vod object. The Remote Meeting Indicator displays to all users with this configuration, even if the user does

not have an Engage Meeting license.

Example Screenshots

The Remote Meeting Indicator displays in blue, white, or grey depending on the background color of the area of the application. This color does not differentiate functionalities.

iPad My Schedule Week View

Figure 11: iPad My Schedule




35

Online Timeline

Figure 12: Online Timeline

This feature is available on the Online, iPad, and iPhone platforms.

ENGAGE WEBINAR

Displaying Webinar Links and Codes Engage Webinar can be configured to immediately provide end-users with the participant URL and ID codes when adding an account as a speaker or an attendee. This enables end-users to share this information either in verbal or written form in instances where the account has not consented to receive emails. For example, Sarah Jones is coordinating a webinar and invites Dr. Clinton Ackerman. Dr. Ackerman wishes to attend the webinar but has not consented to receive emails. When Sarah adds Dr. Ackerman as an attendee, the generated webinar URL immediately displays and she is able to share the URL information with Dr. Ackerman by writing it down or delivering a printed invitation to the event.

Configuration

To configure this feature:

1. Grant end-users FLS read to the following fields on the following objects:

• EM_Attendee_vod o Webinar_Participant_URL_vod o Webinar_Participant_ID_vod

• EM_Event_Speaker_vod o Webinar_Panelist_URL_vod o Webinar_Panelist_ID_vod




36

2. Place the following fields on the appropriate EM_Attendee_vod object page layouts:

• Webinar_Participant_URL_vod

• Webinar_Participant_ID_vod

3. Place the following fields on the appropriate EM_Event_Speaker_vod object page layouts:

• Webinar_Panelist_URL_vod

• Webinar_Panelist_ID_vod

Connected Mode is required for this feature. If attendees are added from a mobile client

without an internet connection, the attendee link can only be generated by sending an email

invitation to that attendee or by removing and rea-adding the attendee when an internet

connection is reestablished.

Use

Webinar links and ID codes display in the appropriate field immediately after adding an account as a speaker or an attendee. Users can then share this information with the HCP using any appropriate method. This feature is available on the Online and iPad platforms.

Engage Webinar Web Client

The Engage Web Client now supports webinars enabling attendees to join without requiring additional software or plugins. The Web Client allows webinar attendees to join from devices otherwise restricted by IT policies. The Web Client is supported on the following desktop browsers:

● Internet Explorer 10 and higher – HCPs joining an Engage Meeting with Internet Explorer

8 or 9 are directed to download the Windows desktop client

● Microsoft Edge

● Chrome

● Firefox

● Safari

For example, Sarah Jones schedules an Engage Webinar with a number of HCPs including Dr. Clinton Ackerman to discuss Cholecap efficacy. Dr. Ackerman's hospital does not allow HCPs to install software on hospital computers. Dr. Ackerman joins the Engage Webinar via the Web Client using a supported desktop browser, enters his name when prompted, and is automatically entered into the event.




37

This feature is enabled by default.

Use

When an attendee receives an Engage Webinar invitation, navigating to the link in the invitation from a desktop browser displays the Web Client Join page. After the attendee enters their name, they are automatically entered into the webinar.

Figure 13: Engage Webinar Web Client

The Engage Webinar Web Client allows attendees to view screen shares. To receive audio, attendees must dial into the meeting using the information provided or use the VOIP option.

MULTICHANNEL CYCLE PLAN

Edit Product Goals by Priority in a Single Call Channel

MCCP Administrations can now enable users to edit their product goals by priority for the same product via one call channel. Product goals by priority for the same product via one call channel is already supported on the MCCP Targets tab, MCCP widget on the call report, and the My Schedule tab. This feature is available on the iPad platform.

Approved WeChat

Approved WeChat Notifications Notifications are now sent to users to indicate when an HCP progresses through the steps of the service account consent process of verifying their identity and subscribing to the service account. For example, Clinton Ackerman completes the WeChat verification process to verify his identity by scanning the QR code from Sarah Jones’s device. Sarah receives a notification in WeChat




38

when Dr. Ackerman completes this step. Dr. Ackerman must also subscribe to the service account for Cholecap 20 mg in order to receive information regarding the efficacy of this product. He selects the subscribe link. As soon as Dr. Ackerman is verified and subscribes to the service account, Sarah Jones receives another notification via a message in WeChat. This feature is enabled by default.

Approved WeChat Dashboard

Users are now able to view a MyInsights visualization of their territory’s Approved WeChat activity and coverage. These reports enable users to plan and determine next steps. For example, Sarah Jones reviews the open rate in the Approved WeChat dashboard. She sees that the open rate is 60%. She drills into the Sent Message History list to view the latest messages sent and whether they were opened. Sarah notes her Cholecap content is being opened at a high rate and decides to send it to her other target HCPs.

Configuration

MyInsights needs to be configured for all users. See MyInsights for more information. To configure the Approved WeChat Dashboard for end users:

1. Grant FLS read permission to the following fields:

Object Field

Sent_Message_vod ● Status_vod

● Sent_Datetime_vod

● Content_vod

● Account_vod

● Sent_Datetime_vod

● Last_Open_Datetime_vod

● Total_Duration_vod

● Content_Type_vod

Multichannel_Consent_vod

● RecordType

● Channel_Value_vod

● Opt_Type_vod

● Opt_Expiration_Date_vod

● Capture_Datetime_vod

● Content_Type_vod

● Account_vod

https://crmhelp.veeva.com/doc/Content/CRM_topics/My_Insights/MyInsights%20Overview/Overview.htm




39

TSF_vod ● Territory_vod

● My_Target_vod

● Account_vod

2. Grant access to the Territory_Insights_vod record type. 3. Ensure there are active VMOCs for the objects listed in Step 1. 4. Ensure users have Read access to the Content_Type_vod object and an active VMOC. 5. Download the Approved WeChat Dashboard HTML zip file.

Use

The following widgets are available to display on the Approved WeChat Dashboard:

● Activity - Provides information on the messages sent in the past 30, 60, or 90 days

○ Open Rate - Percentage of sent messages opened at least once

○ Sent Message History - List of the Approved WeChat messages sent

● Coverage - Provides information on the percentage of targets who can receive an

Approved WeChat message

○ Target HCP Opt-in - Percentage of target HCPs in a user’s territory who have

opted into receiving Approved WeChat messages

○ Target HCP Sent Message Coverage - Percentage of target HCPs who have

received an Approved WeChat message

○ Multichannel Consent History - List of the last 50 Multichannel Consents created

for verification or subscription to a Service Account

This feature is available on the iPad platform.

Parity

Core CRM

Surveys

Survey branching is now available on the iPhone and iPad platforms.

Call Reporting

Location Services (GPS)

iPhone users can now use GPS coordinates in Call Reports. See Location Services for more information.

https://cdnmc10.vod309.com/htmlreports/LR/wechat_rep_dashboard

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

https://crmhelp.veeva.com/doc/Content/CRM_topics/Activities/Call_Reporting/CapturingGPSCoordinates.htm




40

Scheduling and Planning

iPad users can now view additional historical data and planned activity on the Timeline View by using the swipe up or down gesture at the bottom or top of the Timeline. Three months of additional data loads at a time.

MyInsights

The Medical Discussion Dashboard is now available on the iPhone platform.

https://crmhelp.veeva.com/doc/Content/CRM_topics/Accounts/Components/TimeLineView.htm

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




41

Revision History

Feature Date Change

Platform/Enablement

Feature Platforms Enablement

Account Deep Linking iPad, iPhone By Default OpenData Veeva ID Matching All By Default

Display Order for Call Objectives Online, iPad, Windows

Needs Configuration

Displaying Account Identifies and Addresses in Call Location

Online, iPad Needs Configuration

Sampling on iPhone iPhone Needs Configuration

Planograms in Accounts and Inventory Monitoring

iPad Needs Configuration

Payment Terms per Delivery iPad Needs Configuration

Delegate Approvers for EM All Needs Configuration Calendar Reminders for EM Invites All Needs Configuration

SAP Concur Data Centers All By Default

SAP Concur Auto-Add Expense All By Default Creating Unverified Accounts by Record Types


KMI Restricted Words All Needs Configuration

Configurable LookUps in KMI All Needs Configuration

AE Restricted Words All Needs Configuration

WKWebView Support for Loading Local Files

iPad, iPhone By Default

Setting and Checking Consent at the Email Template Level


Remote Meeting Indicator Online, iPad, iPhone

Needs Configuration

Displaying Webinar Links and Codes Online, iPad Needs Configuration


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

Feature Platforms Enablement

Engage Webinar Web Client All By Default Edit Product Goals by Priority in a Single Call Channel

iPad By Default

Approved WeChat Notification Offline Devices By Default

Approved WeChat Dashboard iPad Needs Configuration

Table 3: Platform/Enablement

Appendix A: New Objects

The list below contains all objects added in Veeva CRM Version 19R1.

Object Label Description

Message_Template_Content_vod Message Template Content Planogram_Line_vod Planogram Line Planogram Line provides

drives positions and dimensions for gondolas, shelves and products in the planogram.

Planogram_vod Planogram Planogram header to establish how a set of products should be displayed in pharmacy/ mass market (accounts).

WeChat_Settings_vod WeChat Settings Customer Settings for WeChat CRM

Table 4: 19R1 Objects



Appendix B: New Fields

The list below contains all fields added in Veeva CRM Version 19R1. 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_vod Total_Sent_Message_vod

Total Sent Message The number of the messages have been sent

Number

Account_vod zvod_Account_QRcode_vod

Zvod_Account_QRcode Marker field for the QR code in the account page layout

Checkbox

Account_Partner_vod

Inventory_Monitoring_Type_vod

Inventory Monitoring Type Picklist

Account_Partner_vod

Planogram_vod Planogram Lookup

Action_Item_vod

Mobile_ID_vod Mobile ID System field used by mobile products to aid synchronization.

Text

Approved_Document_vod

Check_Consent Check Consent Check Consent overrides default consent set at Account

Picklist

Approved_Document_vod

WeChat_Template_ID_vod

WeChat Template ID Stores the service account template ID Text

Call_Objective_vod

Display_Order_vod Display Order A way to determine the order in which the Call Objective appears on the call report, based on ascending alphanumeric sorting.

Text

Content_Type_vod

Disclaimer_Page_Url_vod

Disclaimer Page URL Stores the disclaimer URL that is shown to an HCP during the subscription process to a service account

Text

Content_Type_vod

Service_Account_App_Id_vod

Service Account App Id Stores WeChat Service Account APP ID Text

Data_Change_Request_vod

Network_Create_Unverified_vod

Network Create Unverified Determines if the DCR will override the Network workflow settings and create an Unverified Record in Network.

Number




EM_Attendee_vod

Webinar_Participant_ID_vod

Webinar Participant ID Engage Webinar participant identifier Text

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_IDs_vod

Delegate Approver IDs Stores the IDs of all delegate approvers. Long Text Area

EM_Event_History_vod

Delegate_Approver_vod Delegate Approver The user selected as the delegate approver

Lookup

EM_Event_Speaker_vod

Webinar_Panelist_ID_vod

Webinar Panelist ID Webinar panelist identifier Text Engage

Multichannel_Activity_vod

Sent_Message_External_Id_vod

Sent Message External Id External ID to determine which Sent Message to write Multichannel Activity for

Text

Multichannel_Activity_vod

Sent_Message_vod Sent Message Indicates which Sent Message record the activity is associated with

Lookup


Captured_By_vod Captured By Captured_By_vod is a lookup to the user who invited the HCP to consent

Lookup


Channel_Source_vod Channel Source Stores the object and field API names of the channel source.

Text


User_Last_Notified_vod User Last Notified User_Last_Notified_vod contains the datetime of when the User has been notified that an Account has been verified

Date/Time

Order_vod Delivery_Payment_Rule_vod

Delivery Payment Rule Shows and stores the Delivery Payment Term that the rule has determined, not editable by users

Text

Order_vod Delivery_Payment_vod Delivery Payment Shows and store the Delivery Payment Term value that the user settled on

Text




Order_vod zvod_Delivery_Payment_Rule_vod

zvod_Delivery_Payment_Rule

Marker field used to display the Delivery Payment Term rule that was calculated by the pricing engine for a delivery order

Checkbox

Order_vod zvod_Delivery_Payment_vod

zvod_Delivery_Payment Marker field used to display the Payment Term selector for delivery orders

Checkbox

Product_vod Height_vod Height Number Product_vod Width_vod Width Number

Sent_Message_vod

Account_vod Account Lookup to the associated HCP account record.

Lookup

Sent_Message_vod

Capture_Datetime_vod Capture Datetime The date time when the user trigger to send content to the HCP

Date/Time

Sent_Message_vod

Content_Clicked_vod Content Clicked Content_Clicked_vod is a formula field which captures if there was at least single click event or not for sent content

Formula

Sent_Message_vod

Content_Type_vod Content Type Content_Type_vod stores the service account record in the Sent Message record if the record type of the Sent Message record is WeChat_vod

Lookup

Sent_Message_vod

Content_vod Content Content_vod represents the Multichannel Content to which the Sent_Message_vod record is associated

Lookup

Sent_Message_vod

Delivered_Datetime_vod Delivered Datetime Delivered_Datetime_vod is the datetime when the message has reached the recipient's inbox

Date/Time

Sent_Message_vod

Detail_Group_vod Detail Group Detail_Group_vod represents the detail group to which the Sent_Email_vod record is associated. This will correspond to the Detail Group to which the product (Product_vod) is aligned.

Lookup




Sent_Message_vod

Last_Open_Datetime_vod

Last Open Datetime The last date time when the account opened the content in WeChat

Date/Time

Sent_Message_vod

Opened_vod Opened Opened_vod captures if the message was opened at least once or not at all.

Number

Sent_Message_vod

Product_vod Product Product_vod represents the product to which the multichannel content is associated

Lookup

Sent_Message_vod

Sent_Datetime_vod Sent Datetime Sent_Datetime_vod is the datetime when the Tencent service dispatched the message.

Date/Time

Sent_Message_vod

Status_vod Status Status_vod captures the status of the message delivery. Picklist

Sent_Message_vod

Template_vod Template Template_vod represents the WeChat message template to which the Sent_Message_vod record is associated

Lookup

Sent_Message_vod

Territory_vod Territory The territory associated to the user who sent the message

Text

Sent_Message_vod

Total_Duration_vod Total Duration The sum of the duration that the account views the content (in seconds). This is updated by an APEX class job.

Number

Sent_Message_vod

Total_Interacts_With_Content_vod

Total Interaction The clickthrough action in the content Number

Sent_Message_vod

User_vod User User_vod is a Lookup to the User that sent the message

Lookup

Sent_Message_vod

VExternal_Id_vod VExternal ID External ID to determine which Sent Message to write Multichannel Activity for

Text

Sync_Tracking_vod

Successful_Sync_vod Successful Sync Contains 1 if the sync was successful. Formula




Sync_Tracking_vod

Sync_Type_vod Sync Type Type of synchronization that occurred, such as Incremental, User-triggered or Forced (a.k.a. triggered by the tablet because of new fields in the describe).

Picklist

Veeva_Settings_vod

KMI_RESTRICTED_WORDS_MESSAGES_vod

KIM Restricted Words Veeva Messages

This setting works with the corresponding Veeva Messages listed. It is used to filter for words or phrases that a customer wants to prevent a rep from entering in a Medical Insights record.

Text

Table 5: 19R1 New Fields

Documents

19R1 Release Notesdocs.veevacrm.com/ReleaseNotes/Veeva CRM 19R1... · as the Business_Professional_vod accounts Call Sampling iPad and Online: The address and Sample Indicator associated