About Lightning Pages

A Lightning Page consists of a list of a single region, named “main”, containing ComponentInstances. A ComponentInstance contains a set of properties for an instance of a particular component, such as which Lightning component the instance points to, and a set of name/value pairs representing a subset of the Lightning component’s attributes.

Available Standard Lightning Components

Not every Lightning component can be specified in a ComponentInstance. Even among those that are allowed, not all of their attributes can be specified. Currently, five Lightning components are supported for use in Lightning Pages.

flexipage:filterListCard
Points to a list view and displays the first few records from that view.
The flexipage:filterListCard component supports all list views that are associated with standard and custom objects except:
  • Activity
  • ContentVersion (Files)
  • Task
  • User
  • UserProfile
flexipage:recentItems
A list of most recently used items that supports these objects, based on the specified properties:
  • All custom objects
  • All standard objects for which both of these conditions are true:
    • A compact layout is defined for the object.
    • The object is tracked in the most recently used objects list.
    If an object is tracked in the most recently used objects list, one or both of the LastViewedDate or LastReferencedDate fields will be present.
The Recent Items component doesn’t support these objects:
  • ContentVersion (Files)
  • User
  • UserProfile
flexipage:reportChart
Use the Report Chart component to include a chart from a report in your Lightning Page.
Properties:
  • label: If you leave this property blank, the component label is taken from the label of the report instead.
  • reportName: the API name of the report

This component is supported in API version 32.0 and later. It doesn’t work with reports that are located in the My Personal Custom Reports folder. Report Chart components that refer to reports in the Unfiled Public Reports folder aren’t deployable if you include them in a package.

flexipage:richText
Use the Rich Text component to add text and simple HTML markup to your Lightning Page.
Properties:
  • richTextValue: the HTML or text to display

    JavaScript, CSS, iframes, and other advanced markup aren’t supported. To use advanced HTML elements in a component, we recommend using a Visualforce page component.

    Note

The Rich Text component is limited to 4,000 characters. This component is supported in API version 32.0 and later.

flexipage:visualforcePage
Use the Visualforce Page component to include a Visualforce page in your Lightning Page.
Properties:
  • label: the component label. If you leave this property blank, the component label is taken from the label of the Visualforce page.
  • pageName: the API name of the Visualforce page to render
  • height: the height of the Visualforce page in pixels. This value must be a whole number, and not negative. If this property is left blank, a default height of 300 pixels is assigned.

This component is supported in API version 32.0 and later.

To appear in Salesforce1, the Visualforce page must have the Available for Salesforce mobile apps option selected. This option is available for pages that are set to API version 27.0 and later.

So, what can a Lightning Page contain?

Lightning Pages can include:
  • Components that display list views, recent items, a report chart, rich text, or a Visualforce page
  • Global actions