To do this, think about whether a separate status detail or status reason field should be added. Likewise, most people (here in the UK at least) expect things to run from left to right like when reading, so you’d want to make sure your picklist values are arranged so that most records will flow from left to right on the path component.įor example, displaying the status of a record going through a review process you’d want fully reviewed and no further work needed on the right while ‘draft’ or similar on the left. A larger number of values makes the graphics less useful as your users won’t be able to see the text at a glance as each value will get truncated. A few things to think about here are the order of the values and the number of values in your picklist.
This is great for showing progress through a process. When path is enabled it can use a picklist field to display a graphic. You can configure the highlights panel to show up to 10 buttons before creating a drop down so the order of the buttons can mean you can keep the most regularly used actions on the bar with less common ones in the drop down. Think about whether it might actually be useful to have the delete button in the drop down where it's hard to hit it accidentally and arrange your actions and buttons accordingly. More than ever here the order of buttons matters as by default it shows three buttons and the rest will gather in a drop down. Firstly, it displays the compact page layout for the record and displays the actions and standard buttons from the Salesforce Mobile and Lightning Experience Actions section of the page layout. Whatever fields you have set to display on a user’s page layout will display wherever you put this component. Record Details – this component gives you access to the page layout as defined on the object. I’ll also mention a couple that I feel are often under used, mainly because they seem to have such an obvious use, but you can actually do much more with them. There’s plenty to say here and a lot of them are self-explanatory, but some need a little more understanding to be able to set up successfully.
Let’s start with understanding what makes up our Lightning pages.įirstly, we’ll take a look at some of the standard components provided by Salesforce for a record page. This is the first of a multi part blog series on how you can use Lightning pages and the flexibility they can bring you, without jumping into heavy Salesforce development. Over the past couple of years we’ve seen big changes to page layouts and Lightning pages, which might seem overwhelming or confusing.
0 kommentar(er)
