Enhanced Page Layout Editor User Interface Elements | Salesforce
Enhanced Page Layout Editor User Interface Elements
Available in: both Salesforce Classic and Lightning Experience
Available in: All Editions
User Permissions Needed
To customize page layouts:
To view page layouts:
“View Setup and Configuration”
This list describes the enhanced page layout editor user interface elements and how you can use them in your page layout. To add elements, drag them from the palette to the layout. Valid drop locations show up in green. To remove elements, drag them off the layout and back to the palette.
Create the appropriate buttons, custom links, fields, custom s-controls, and Visualforce pages before editing your page layout.
Mobile smart actions appear as a single action element in the page layout editor. However, they appear in the action bar and action menu in Salesforce1 as distinct create actions. These distinct actions allow users to create records directly from the action bar. The create actions included in the set of mobile smart actions vary depending on the page layout’s object.
If you delete an action, the action is removed from all layouts that it’s assigned to.
Wave Analytics Assets
You can add and move a Wave Analytics
dashboard to any section on the page layout, except Mobile Cards.
For a Wave Analytics
dashboard element, use field mapping to map data fields in the dashboard to the object’s fields so that the dashboard shows only the data that’s relevant for the record being viewed. You can specify fields from multiple datasets. Identify each dataset by its system name, which is listed on the dataset’s edit page. Identify the data fields by row, and for the values, specify either the field names from the Salesforce object or specific values. The JSON field mapping follows this format:
You can add and move blank spaces to any section on the page layout, except Mobile Cards. Use blank spaces to visually align and distinguish elements on the page.
If you use the original page layout editor to view a page layout that was created in the enhanced page layout editor, the original page layout editor shows the blank spaces you added. You can’t move or add blank spaces in the original page layout editor, but you can remove them by dragging them to the box on the right.
Blank spaces aren’t supported in Lightning Experience.
You can control which standard and custom buttons are displayed and the order in which the custom buttons appear. You can’t rearrange the order of the standard buttons.
Standard and custom buttons are available as actions in Salesforce1 and Lightning Experience.
For the Canvas Apps category to appear in the palette, set the canvas app location to Visualforce Page when you create the canvas app in Salesforce.
If you add a canvas app to any section other than the Mobile Cards section, the canvas app appears in the page layout in the full Salesforce site or in the record detail page in Salesforce1.
If you add a canvas app to the Mobile Cards section, the canvas app appears as a card on the record related information page in Salesforce1.
When you add a component to the Mobile Cards section of a page layout, it displays as a card on a record’s related information page in Salesforce1. Components are supported only in the Mobile Cards section of a page layout, and they only appear in Salesforce1.
In organizations that are created after Spring ’14, the Twitter component is added by default to the Mobile Cards section of page layouts for objects that support it.
Social Accounts and Contacts must be enabled for your organization before you can add the Twitter component to a page layout.
The Twitter card that you see on account, contact, and lead record pages in Lightning Experience isn’t the same as the Twitter component available as a mobile card in the page layout editor. The Twitter card in Lightning Experience is a Lightning component. You must have Social Accounts and Contacts enabled for it to appear.
The Expanded Lookups category for the enhanced page layout editor contains fields with lookup relationships. These fields, when added to the Mobile Cards section of the layout, display as related lookup cards on a record’s related information page in Salesforce1. A page layout can have up to 20 expanded lookups.
The Expanded Lookups category only contains fields with lookup relationships to objects that support compact layouts.
Expanded lookups aren’t supported in Lightning Experience.
A field can display one or more of these icons:
―The field must have a value to save the record, but isn’t required on the page layout itself.
―The field must be included on the page layout because either an administrator configured the field as universally required or Salesforce automatically requires the field. Although you can’t remove such fields, you can move them to different locations.
―The field is a controlling field.
―The field is a dependent field.
―The field is read only.
To set which fields are required and read only, select one or more fields and click the wrench icon () on any of the selected fields.
The field properties of some standard fields cannot be changed. Custom fields can only be changed if they are not universally required fields.
Fields marked as read only are always editable by administrators and users with the “Edit Read Only Fields” permission.
If you make a picklist field read only, all new records contain the default value for that picklist.
Auto-number fields are always read only.
If you mark the opportunity Probability field as read only, the Probability value is still updated when a user changes the Stage value of an opportunity.
When working with fields:
In Personal, Contact Manager, and Group Editions, page layouts control which fields users can access in related lists, list views, reports, Connect Offline, email and mail merge templates, custom links, and when synchronizing data. In Professional, Enterprise, Unlimited, Performance, and Developer Editions, field-level security controls this access. Field-level security settings override field properties that you set on the page layout if the field-level security is more restrictive than the page layout setting.
Users can import values into a field only if they have read and edit access. Field access is determined by user permissions, page layout assignments, and field-level security settings.
A page layout can have up to 100 related lists. You can place related lists at the bottom of the page layout. To move a related list on the page layout, drag the handle located above the related list.
To customize a related list, double-click the related list handle or click the wrench icon () inside the handle. Use the related list properties to:
Specify which fields display as columns on the related list, the order in which they appear, and the sort order of the records in the related list. In Professional, Enterprise, Unlimited, and Performance Editions, you can also opt to apply the column information to other page layouts for the same type of object.
Specify which standard and custom buttons appear on the related list.
When working with related lists on page layouts, note the following:
The View All button only displays up to 2,000 items in a related list.
Some related lists aren’t customizable because they link to data rather than store it. Salesforce denotes related lists that aren’t customizable on the page layout.
You can’t add related lists to the page layouts for the User object.
You can also enable related list hover links for your organization so that record detail pages include links for each related list at the top of the page. Users can hover the mouse over a related list hover link to display the corresponding related list in an interactive overlay that allows them to quickly view and manage the related list items. Users can also click a related list hover link to jump down to the content of the related list without scrolling down the page.
In Professional, Enterprise, Unlimited, Performance, and Developer Edition, individual users can customize which related lists display for their personal use. Administrators can overwrite these user customizations and apply the related list configuration in the page layout to all users, even if they already customized their display. To overwrite users' related list customizations, click Yes on the Overwrite Users' Customized Related Lists popup window, which appears when saving a page layout if you moved or added a related list.
Related lists show up on the record related information page in Salesforce1.
A page layout can have up to 20 s-controls.
To change the properties of an s-control, double-click the s-control or click its wrench icon () and set the following attributes:
Width sets the horizontal size in pixels or a percent.
Height sets the vertical size in pixels.
Show scrollbars determines whether the iFrame in which the s-control displays contains scroll bars when necessary.
Show label determines whether the page layout includes the Label of the custom s-control. Remove the label to display the s-control in a wider area.
S-controls aren’t supported in Lightning Experience.
You can add and move sections anywhere above the related lists on the page layout. The sections you add can contain fields, s-controls, and blank spaces. In addition, each page layout has a default section that can only contain custom links and blank spaces. You can change the location of the custom link section, but you can’t remove it from the page.
The Section user interface element is the second option in the palette when you select the Fields or Custom S-Controls category on the palette.
To change the attributes of a section, double-click the section or select its associated wrench icon (). You can:
Enter a name for the section. Names of some standard page sections cannot be changed.
Specify whether the section has one or two columns.
Specify the order in which users can tab through the items in that section.
Specify whether the section heading is shown on the detail and edit pages.
If tags are enabled in your organization, click Layout Properties and use the checkboxes to indicate whether personal and public tags are included in the header section of the page layout. Users can’t tag a record if neither personal nor public tags are included in the header section. Also, the positioning of personal and public tags in the header cannot be modified.
Tags aren’t supported in Lightning Experience.
Visualforce pages can be added to any section on the page layout except for sections reserved for custom links and related lists. A page layout can have up to 20 Visualforce pages.
You can add a Visualforce page to a page layout only if the standard controller on the Visualforce page is set to the object for which you are creating the page layout. If you don’t have any Visualforce pages with a standard controller set to that object, the Visualforce Pages category doesn’t appear in the palette.
Only Visualforce pages with the Available for Salesforce mobile apps and Lightning Pages checkbox selected will display in Salesforce1.
Mobile-enabled Visualforce pages show up as slightly differently colored elements in the palette than their non-mobile-enabled counterparts. Hovering your mouse over a Visualforce page element in the palette shows whether the Visualforce page is mobile-enabled.