Show
Naming standards for record pages use the title case and Pascal case conventions. Learn more about title case and Pascal case in Component Design Guidelines. CreationNimble AMS includes at least one record page for every object. Some Nimble AMS objects that use record types also include a record page for each record type. Nimble AMS record pages are not directly editable, but they can be cloned. Also, custom objects automatically create a default record page. Therefore, the scenarios in which you generally need to create a new record page are:
NamingSince Lightning App Builder is also used to create other types of pages, such as home pages, it is important to distinguish the type of page you are creating within the name. The standard for naming a record page depends on whether the record page is used as a default for all records or if it is assigned to a specific record type. Default Record PagesFor a record page that is not assigned to a specific record type, enter a name in title case and an API name in Pascal case with the format: [association acronym] [object name] Record Page For example, the association acronym for the International Society for the Exceptionally Nimble is ISEN. For a custom Widget object with no record types:
Nimble AMS record pages that are not assigned to a record type are named Nimble AMS [object name] Record Page with the API name in Pascal case. For example, Order has no record types and therefore has a single record page:
Record Type Record PagesFor a record page assigned to a specific record type, enter a name in title case and an API name in Pascal case with the format: [association acronym] [object name] Record Page - [record type name] For example, the association acronym for the International Society for the Exceptionally Nimble is ISEN. For a custom Widget object with a record type of "Adjustable:"
Nimble AMS record pages assigned to specific record types are named with the format Nimble AMS [object name] Record Page - [record type name] with the API name in Pascal case. For example, the Product record type Donation has a record page assigned to it:
TemplateSalesforce provides several page template options when creating a new record page. We recommend two templates to maximize consistency across record pages. The template you select depends on how the record is used:
In the header, place the following Lightning components in this sequence:
Naming TabsWhen naming a tab, use standard labels whenever possible. Specifically, we recommend the following standard labels:
You can use Lightning record pages to place related lists in any sequence anywhere on the record page. To take advantage of this, we recommend using the Related List - Single Lightning component instead of the Related Lists Lightning component. Instead of having a single Related tab that contains all related lists for the record, offload object-based related lists—that is, related lists that are not standard such as Files, Notes, and object history—into up to three additional "related list group" tabs. Each related list group tab contains a subset of related lists that share a similar relationship with the record and they reduce page scrolling and loading times. Most Nimble AMS objects have at least one related list group. We recommend creating a tab for the following related list groups wherever possible:
If an object includes more than one related list group tab, we recommend placing them in the sequence indicated by their rank. The "Main Column" and "Right Sidebar" sections below provide specific sequence recommendations. For objects with a lot of related lists or configuration information, you can nest a Tabs Lightning component within another Tabs Lightning component to create sub-tabs. For example, sub-tabs are used on the Nimble AMS Entity Record Page. Main ColumnPlace a single Tabs Lightning component in the main column and create applicable tabs—and Lightning components inside each tab—with the following sequence and configuration:
In the Tabs Lightning component, set Details as the default tab. Place a single Tabs Lightning component in the right sidebar and create applicable tabs—and Lightning components inside each tab—with the following sequence and configuration:
In the Tabs Lightning component, set the first tab as the default tab. What is true about custom lightning page template component?Lightning page templates are components that define a page's regions and can be used for Home, Record or App pages. Both standard and custom templates appear in the App Builder's New Page Wizard and can be used to create new pages for an app. They are pretty easy to create, so let's dive in!
How can you create lightning record pages in Salesforce what to choose?Let's get started.. From Setup, enter App Builder in the Quick Find box, then select Lightning App Builder.. Click New.. Select Record Page and start stepping through the wizard.. Name your page New Opportunity Page , and select Opportunity. ... . Choose the Header, Subheader, Right Sidebar template, and click Finish.. Which components are supported when building lightning pages with the lightning app Builder?Lightning Components
A Lightning component is a compact, configurable, and reusable element that you can add to a Lightning page in the Lightning App Builder. Lightning pages support these components: Standard Components - Standard components are Lightning components built by Salesforce.
What actions can be performed to customize a record page in the lightning app Builder?What actions can be performed to customize a record page in the Lightning App Builder. 1) Components can be removed. 2) Components can be added.. Required fields can be applied to text, number and picklist fields.. The field cannot be hidden.. The field is automatically added to all page layouts.. |