Visit Engagement page sidebar, fields and troubleshooting
Key Takeaway
If correctly configured fields appear in the Life Sciences Cloud mobile app but are missing on the desktop Visit Engagement page, check the user's locale first. Change any Language (Region, Currency) locale to Language (Region) format.
The Visit Engagement page is the main workspace field users work in during a visit with a customer. It has two main parts. A configurable sidebar lets users move between visit activities, such as Samples and Discussions. A main form for data entry starts with the Visit Information section. You shape both parts mainly by editing the page layouts on the Visit and Provider Visit objects. However, the page shows only certain fields and objects. A consultant needs to know what the layouts control, what they don't control, and how to diagnose fields that don't appear.
How the sidebar works
Each sidebar menu item corresponds to a related list on the Visit page layout. To add a feature to the sidebar, you add its related list. The order of the related lists on the layout sets the order of the sidebar.
| Sidebar menu item | Related list on the Visit page layout |
|---|---|
| Content | Presentation Forums |
| Product Details | Provider Visit Product Detailings |
| Samples | Product Disbursements |
| Direct to Practitioner | Provider Visit Requested Samples |
| Marketing Items | Provider Visit Marketing Items |
| Attendees | Child Visits (labeled Attendees) |
The sidebar supports only the standard objects in this mapping. Unlike custom objects, other standard objects can't be added through lookup fields.
You can rename related list labels in Setup with "Rename Tabs and Labels" so the sidebar matches your users' terms. For example, you can rename Product Disbursements as Samples.
The Recommendations menu appears automatically at the top of the sidebar when recommendations exist. You don't add it to the layout.
Every field in a Visit Engagement related list needs at least "Read" field-level security for all profiles and permission sets assigned to the layout. If a user can't read one of those fields, the related list can fail to load.