Apex Health Logistics is implementing a custom Lightning Service Console app for its specialized tier-2 escalation support team. The support manager has outlined three strict functional layout requirements for the console interface: 1) When an agent opens an Account record from inside a Case, the Account record must open as a subtab under that Case rather than as a new primary tab; 2) Support agents must be able to view and edit associated Contact details directly from the Case record view without switching active tabs; and 3) Key case fields (Status, Priority, Account Name, and Contact Phone) must remain persistently visible at the top of the Case record page regardless of scrolling. Which combination of configuration actions should the Salesforce Administrator perform to fulfill these requirements?
- AConfigure Subtab Logs in App Manager; add a Record Detail component filtered by Contact on the Case Page Layout; and configure a Dynamic Forms section set to sticky positioning at the top of the page.
- Define tab navigation rules in Navigation Items settings to open Account as a subtab of Case; add a Related Record component for Contact to the Case Lightning Record Page; and customize the Case Compact Layout with the required fields.Cevap
- CAssign a dedicated Console Profile to support agents with Additive Subtab permissions; add a Lookup Field component for Contact to the Case page layout; and create a custom Visualforce page pinned to the utility bar.
- DConfigure Case Assignment Rules to automatically link Account subtabs upon case creation; embed a Chatter Feed Component set to Feed Tracking for Contact fields; and enable Data Category visibility on Case records.