You are here:
Configure Visit Preview
Configure the visit preview to let your users view key visit details directly on the calendar grid by tapping a visit, without opening the visit record.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions with Life Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the Life Sciences Customer Engagement managed package. |
| User Permissions Needed | |
|---|---|
| To manage visit settings: | Life Sciences Commercial Admin permission set |
The visit preview screen supports the display of these sections.
- Attendees
- Samples
- Product Details
- Items
- Pre-Visit Objectives
- Next Visit Objectives
Note The visit preview displays the Invited By field for all visitors added to the
visit.
As a prerequisite, ensure that the Skip visit preview screen on planner setting is deselected in Visit settings. For more information, see Configure Visit Settings.
Add Attendees and Samples to the Visit Preview Layout
- From Setup, find and select Object Manager.
- Select Visit, and then select Page Layouts.
-
Add these related lists to the Visit page layout.
- Child Visits
- Product Disbursements
- Save your changes.
Add Product Details and Items to the Visit Preview Layout
- From Setup, find and select Object Manager.
- Select Provider Visit, and then select Page Layouts.
-
Add these related lists to the Provider Visit page layout.
- Provider Visit Product Detailings
- Provider Visit Marketing Items
- Save your changes.
Adding Objectives to the Visit Preview Layout
- From Setup, find and select Object Manager.
- Select Provider Visit, and then select Page Layouts.
-
Add these related lists to the Provider Visit page layout.
- Pre-Provider Visit Notes
- Next Visit Objective or Next Visit Objective Type
- Save your changes.
Note The display order of the sections in the visit preview is fixed. Rearranging related lists
or fields on the page layout will not change the preview's display order.
After you complete these changes, generate metadata cache. This step is important because it makes sure that the mobile app accesses the latest metadata definitions, including any schema changes for supported objects.
Did this article solve your issue?
Let us know so we can improve!
