What energizes me most about Lightning Experience is the adaptability of the UI. With its module structure, and the capacity to dole out pages at a granular level, clients will see an improved navigational encounter and speedy access to basic information components (expecting you to realize how to adjust the client involvement with Lightning).
Yet, in contrast to Classic, there are more layers to oversee in Lightning. With adaptability comes a layer of multifaceted nature. Maybe this is on the grounds that the change from Classic to Lightning is as yet in progress and the two frameworks are not yet completely brought together in Setup, or maybe it's simply the inalienable tradeoff to modularization of the UI. In any case, it's imperative to learn and play with all components of Lightning so when issues emerge, you realize where to look.
In Customizing Salesforce's Lightning Experience, I investigated how to alter the vibe of feeling in Lightning. A great deal had changed in Lightning since distributing that post in 2016 (and I've executed a few Lightning organizations from that point forward as well!), so this post will investigate the components that control the UI.
Don't forget to check out: Salesforce Lightning Experience – Five Tips for Salespeople
Lightning Record Pages
These remarkable record pages are like the conventional page designs in Salesforce Classic, then again, actually Lightning Record Pages sit at a level over Classic's customary page format manager. (I'll clarify this somewhat later.) These remarkable pages give a system and layout to the Lightning Components. At the point when joined, Lightning Components and Lightning Record Pages drive 90% of the UI.
"Lightning pages involve a center ground between page designs and Visualforce pages. Like a page design, Lightning pages permit you to add custom things to a page. Nonetheless, these things, rather than being Visualforce parts, are Lightning segments, which permit significantly more adaptability." (Source)
These pages can be utilized to make an App Page (which resembles a one-page dashboard/landing page cross breed – completely tweaked by you), Record Detail Pages, and Home Pages. The focal point of this post is an ordinary record page, however, the entirety of different pages get made comparatively.
Right now, there are eight formats to look over! In this way, on the off chance that you need a 3 section format for your Opportunity page, think about what – you can do that! Or on the other hand, in the event that you want to make a progressively conventional structure to emulate Classic, you can (yet I don't know why you would)!
Here are the steps to creating Lightning Record Pages.
- Navigate to Setup and using the Quick Find search box, type in Lightning App Builder. Note, you can also navigate to the Object in Lightning, and click Lightning Record Pages.
- Click NEW to create a new page.
- Select Record Page to create a custom Opportunity layout. Click Next.
- Give the page a name (I usually do LEX_Opportunity or something similar) and choose the object this layout will be for.
- Select the desired template for this layout and click Finish
Lightning App Builder
The App Builder is a simplified interface that permits Administrators to make utilizing a templated canvas and Lightning Components. There are 4 key components to the Lightning App Builder page.
Toolbar – The toolbar, which ranges over the head of the page, gives the capacities to fix or re-try an activity, duplicate or glue a setting, review, and invigorate the page, and spare and allot the page to clients.
Component – the left route shows the rundown of accessible segments (both norm and custom) which can be utilized on the Lightning Record Page. Utilize the hunt box at the top to enter a catchphrase and locate the correct segment for the activity.
Component Canvas – the focal point of the page is the place you drag the segments to. Each component you find in the screen capture above is a case of what the UI will resemble with the different segments on the page. Evacuate all the segments in this screen capture, and you're left with a clear format.
Component C Properties – this region is utilized to refine or characterize different segments. For instance, in case you're utilizing the Related List (particular) segment, the Component Properties board is utilized to characterize which related record to turn upward to. Or then again, on the off chance that you add tabs to the page, utilize this properties board to characterize the request the tabs show in, and even the tab names that should show on the page.
Fields and field course of action in Lightning Experiences is as yet overseen through the conventional page format proofreader that we're all acquainted with. While including the Record Detail Lightning Component to the Lightning Record Page, Salesforce is showing the fields, with their proper groupings, precisely as they appear on the customary page layout. My wish is that we'll be able to make Record Detail Groups where fields can be gathered.
My desire is that we'll have the ability to make Record Detail Groups where fields can be organized and made into their part. This would give the greatest degree of page customization since fields could then be separated around the page, and even assembled into Tabs on the format.
Field level security isn't influenced and won't be affected depending on your task of the Lightning Record Page.
Check out another amazing blog by Sumit here: Triggers in Salesforce - The Complete Guide
Related records are marginally unique in that they speak to the half and half style customization I long for with fields. There are two Lightning Components accessible for this territory of Salesforce: Related List, and Related Lists. Notice the inconspicuous contrast?
The Related List segment shows the related rundown as it is arranged in the page format manager. Much like the Record Detail segment, it's a solitary square which copies the arrangement in Salesforce Classic.
The Related Lists segment, be that as it may, permits you to add a solitary related rundown to the Lightning Record Page, and select which related rundown to show. Along these lines, Admins now can put related records in explicit groupings that bode well for the organization. I've utilized this segment for a customer to gather related records into isolated tabs on the Lightning Record Page for a better logical route.
Things being what they are, with the entirety of this setup goodness, what sort of record pages will you structure? What are your preferred Lightning Components and Record Page formats? Drop a remark beneath!