#Lightning app builder page in community how to

You can litter answers all throughout the system: on the home page, on record pages, for different profiles, or even down to a specific user who keeps forgetting the steps to log into their phone. Sit in the back of the room and find out what questions people have, think about what questions they’re going to have. If you’re about to launch a new org, I would suggest for you to still be a part of the training (even if you are not conducting the training). *but, still back this up with Validation Rules for data integrity.įollowing on from Instructions, ‘Training Wheels’ are another great use case. Instead, if they have a simple bulleted list to verify, they will more often only have to save it once*.

However, the one thing Validation Rules lack is telling you up-front what you need to do, and if there are several rules, do you really want a user to keep attempting to save a record just to see what new error will show up? That can be pretty frustrating.

Now, you might be wondering why I wouldn’t just use Validation Rules for this? Don’t get me wrong, I still use Validation Rules for this in many circumstances because it helps enforce data integrity. When they take the desired action, the component will show. a form or button, and use the opposite logic on a Rich Text Component to tell the user what they need to do to get the component to show up. Let me explain: I use to Component Visibility hide a component that has what the user needs, eg. I use Component Visibility to tell the user what they need to do to get the component they need to show up.

#Lightning app builder page in community how to

Have you ever wanted to give users a little more to go on than just Help Text? Or maybe you’ve got users hounding you about how to do something repeatedly? Or maybe some third-party vendor gave you a custom component that works great, but only under specific circumstances? Well, similar to the Alerts section above, the Rich Text Component is your new best friend. Just click on the Advanced tab in the Component Visibility and navigate to that field on the contact: You can use it to enforce data integrity by indicating that something is missing, or to traverse records – for example, let’s say you’re on a case and you want to remind users that the associated contact is missing an email address. My example used a checkbox that was updated manually, but there are so many other great use cases I’ve seen. Then when that box is checked, your users see the lovely banner you created: Here’s the filter in my component visibility: In Lightning you can still use that checkbox – but, in the Lightning Record Page, you can drop a Rich Text Component and format a message that will show for your users. Sure, we can make a checkbox only Tier 2 can see/edit, but making a dynamic Visualforce component to show on a page layout was beyond us at the time. Back in Salesforce Classic, this was a tough sell when it came to priority against other goals. The wish was a big banner that could not be missed, and they wanted only their Tier 2 team to be able to put the banner on the account. When I first became a Salesforce Admin, I remember there was a request to show on the account when a customer escalates a case to Tier 2 support. Naturally, your users will love that you’re able to turn around their request so fast! Both you and your users benefit from this, because the next time a change is requested, you can more quickly identify which page to change. 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.