Admin overhead of Lightning
When setting up any new org there is a number of things I ALWAYS do in setting up Page Layouts and Views etc. Let's see what's involved in Classic vs Lightning
Area | Classic | Lightning | Do in Classic Anyway even if you set up Lightning |
---|---|---|---|
Apps | Create App with Logo for regular users to use | Create or Customise Lightning App | Maybe, depends on if you are just keeping Classic for power users / admin users |
Objects | Turn on Field History Tracking for each Object | ||
Turn on Feed Tracking for each Object | |||
Turn on Middle Names and Suffixes if Required | |||
Page Layout | Set Global Publisher Layouts | Very important - start with minimal, so you can customise each page as needed. | Less important |
Re-create all Page Layouts as Feed Layouts | |||
Set up Layouts so they make sense | But different things may make sense in Lightning | ||
Remove Standard Custom Links not used | |||
Different Layouts for different Record Types or Profiles | |||
Different Layouts for use in different apps - at least one new Layout for each object for Lightning Apps | |||
Mini Page Layouts for hovers | |||
Compact Layouts - one for each Layout | Only if using Console in Classic | ||
Ensure Related Lists for each Page Layout are consistent and make sense | |||
Re-think which Related Lists should be on display if Related List component is used | |||
Remove Activities and Open Activities from Related Lists | |||
Add Files and Notes to Related Lists. Remove Notes and Attachments | |||
Remove Notes and Attachments to Related Lists | |||
Add History Related List to Layouts | Not Available - scheduled Summer '17 #SafeHarbor | ||
Assign Page Layouts | |||
Views | Set up all Views | ||
Set up Search Layouts | These now controlled the Recently Viewed list view so are much more imporant | ||
Set up Tab Layouts | |||