
Simplify these pages by consolidating the experience into as few pages as possible. A new page was created by the admin each time different users requested a change to the page. An Org Default was never set, and a new page was saved each time the admin clicked Edit Page from the Setup menu while on the record.ī. I’ve found there are two main reasons for a list like this to exist:Ī. I can’t tell you how many times I’ve logged into a client’s org for the first time to make some requested updates to a Lightning Record Page and I come to list like this: Here’s the article from when it launched, and is a great introduction to Salesforce Component Visibility.Īs I promised, I’m going to make you fall in love with Lightning Record Pages, by highlighting a few of my favourite things that I’ve discovered.

Why? Component Visibility – it’s a game-changer! When Lightning came out, I had a lot of resistance to switching, and It wasn’t until Winter ‘18 that I got really excited about the potential of Lightning.

You might seem dubious about this if you’re new to Lightning – I don’t blame you.
