Getting Started with Veeva CRM and Lightning

    Online

Lightning is Salesforce’s updated user experience with a focus on usability and efficiency. As Salesforce introduces new enhancements only available in the Lightning Experience, Veeva CRM customers can transition their online users from the existing Classic Experience to the Lightning Experience to take advantage of these enhancements.

To ensure existing functionality renders in Salesforce Classic and the Lightning Experience, some older out-of-the-box Veeva CRM online functionality needs to be replaced with versions compatible with both Salesforce Classic and Lightning.

The upgrade process makes the following configuration changes:

These changes will automatically be applied to all orgs with the 21R3.0 release.

  • Replacing embedded S-controls with equivalent Visualforce components in the Account, Address, and Analytics page layouts
  • Replacing S-control tabs with equivalent Visualforce tabs (e.g. My Accounts, My Schedule, My Setup Products, etc.). The following S-controls are not replaced:
  • An_RF_Acc_List_vod
  • An_TC_Sales_Trends_vod
  • An_RF_Reach_Details_vod
  • An_TSA_Sales_Details_By_Territory_vod
  • An_Territory_Payer_Top_Accts_vod
  • An_TC_Sales_Details_vod
  • An_JD_Dtl_Sum_vod
  • Updating S-control and custom JavaScript buttons

The upgrade process only updates the Lightning compatibility of out-of-the-box CRM components provided by Veeva Product. Customizations and other apps in the org, such as Global Account Search and AppExchange apps, are not affected by this upgrade process and need to be updated separately.

What You Need to Do

System admins can manage the upgrade process via the Veeva CRM Lightning Ready Upgrade tab to:

  • Generate a report detailing the specific configuration changes to the org made by the upgrade process
  • Deploy the upgrade to the org

Considerations

The Lightning Ready upgrade cannot be canceled or undone.

The Lightning Ready upgrade is not supported for orgs with VMobile tablet users.

To use Lightning components in an org, admins must deploy My Domain. See Salesforce's documentation about My Domain for more information.

Supported Browsers

See the Supported Browsers for Lightning Experience Salesforce documentation for a full list of supported browsers.

For troubleshooting browser issues, see the following Salesforce documentation:

Veeva does not support Lightning on IE11 due to Salesforce’s upcoming end of access date for the browser. Lightning is not supported on mobile browsers. However, Salesforce supports a beta version of Lightning on Mobile Safari. To ensure Visualforce pages display correctly, users must disable the Prevent Cross-Site Tracking setting in the Mobile Safari settings.

The embedded browser on the iPad is a mobile browser using WKWebView and displays Salesforce Classic. CRM online launches in the Lightning Experience when using Safari on iPadOS since it is a desktop browser. Users with devices on iPadOS and MacOS must disable the Prevent Cross-Site Tracking setting in the Safari settings. See Go Online for more information.

Limitations

There are known functional limitations of Veeva CRM in the Lightning Experience:

  • Salesforce Global Search does not search the Accounts object if the standard Salesforce Accounts tab is hidden
  • Changing the value of a VOD field in the Kanban view because this method of changing values currently bypasses our business logic
  • Changing the value of a VOD field via the Path because this method of changing values currently bypasses our business logic
  • Migrating Attachments to Files
  • Files related list

If a Veeva out-of-the-box Visualforce page is not working as expected, users should ensure the Available for Lightning Experience, Lightning Communities, and the mobile app setting on the Visualforce page detail is not selected. Additionally, after deploying the upgrade, users can upload Attachments and Files in View mode only for unsubmitted calls. See Using Salesforce Files in Veeva CRM with Lightning for more information.

Configuration

To view the Deploy button in a sandbox org, submit a support ticket to ensure the org is managed by Veeva. Admins can then select the button to deploy the upgrade.

Providing Visibility to the Lightning Ready Tab

After the Lightning Ready tab is available in the sandbox org, you need to provide visibility to the tab:

  1. Navigate to the System Administrator profile.
  2. Select Enabled Visualforce Page Access.
  3. Enable the VeevaCRMLightningReadyUpgradeVod Visualforce page.
  4. Select Save.
  5. Select Tab Settings.
  6. Select Default On or Default Off for Veeva CRM 'Lightning Ready' Upgrade.
  7. Select Save.

Generating the Lightning Ready Upgrade Report

Users with the System Administrator profile can generate the Veeva CRM Lightning Ready upgrade report from the Veeva CRM Lightning Ready Upgrade Visualforce tab using the Run Report button. The report is generated as a PDF and emailed to the requesting admin user.

Deploying the Lightning Ready Upgrade

Pending or in progress Apex jobs can interfere with deployment. Prior to deploying the upgrade, admins should do one of the following:

  • Cancel Apex jobs and reschedule them after deployment
  • Enable the Allow deployments of components when corresponding Apex jobs are pending or in progress setting in the Deployment Settings

Once the admin reviews the upgrade report and is ready to deploy the upgrade, the admin can deploy the upgrade from the Veeva CRM Lightning Ready Upgrade Visualforce tab using the Deploy button. This is the only supported method to deploy the upgrade.

The deployment of the Veeva CRM Lightning Ready upgrade takes approximately 30 minutes to complete.

Deploying the Lightning Ready upgrade is a prerequisite for transitioning to the Lightning Experience. See the Salesforce documentation for more information on preparing for and transitioning to Lightning.

After transitioning to the Lightning Experience, the default org-wide Home page is defined by Veeva. Customers can customize or reassign the Home page for different profiles. See the Salesforce documentation for more information about activating home pages and reassigning the Home page. Additionally, customers should recreate or upgrade existing Salesforce Classic apps to make them available in Lightning.

When populating lookup fields in the Lightning Experience, the standard + option to create records displays in the drop-down list of suggested options. Using this option bypasses Veeva-defined logic and the records created do not inherit necessary field values. See Configurable Lookup Filters and Layouts for more information about lookups with Veeva-defined logic.

Overriding Standard Lightning Components

To allow users edit and change record types for Account and Address records:

  1. Navigate to Setup > Object Manager > Account > Buttons, Link, and Actions.

  2. Select Edit from the dropdown for the Standard page Edit button.

  3. Select the Edit_Account_DCR_vod Visualforce page for the Salesforce Classic Override.

  4. Select the c:EditAccountLgtnVod Lightning component for the Lightning Experience Override.

  5. Select Save.

  6. Navigate to Setup > Object Manager > Address > Buttons, Link, and Actions.

  7. Select Edit from the dropdown for the Standard page Edit button.

  8. Select the Edit_Address_DCR_vod Visualforce page for the Salesforce Classic Override.

  9. Select the c:EditAddressLgtnVod Lightning component for the Lightning Experience Override.

  10. Select Save.