Intro

The SAP Fiori elements object page template supports the features and settings for the object page content area detailed below.

For design information, see the Object Page Floorplan guidelines and the links below.

Feature Availability

 

 

Content Area

 

Availabillity

Navigation Bar: Anchor Bar Default, you can turn it off when you only have one section.
Navigation Bar: Tab Bar Available
Sections and Subsections Available
Reuse Components as Sections Available
 

Subsections

 

Availabillity

Link Available

With SAP Fiori elements for OData V2, the default link shows the text and ID. You can remove the text or the ID.

Smart Link Contact Available, SAP Fiori elements for OData V2 only
Tables Available
Smart Charts Available
Variant Management for Tables and Charts Available
Address Available
Forms Available
Growing Text Control With SAP Fiori elements V4, the default length of the text entry area allows for four lines of text.

You can change the default and enable growing mode.

Dynamic Side Content Available with an extension
 

Subsection Behavior

 

Availabillity

Subsection Starts Loading After the Object Page Elements Are Loaded Default, you can change the behavior.
Adjustment of the Width for Content Display in a Subsection Available
 

Content Visibility

 

Availabillity

Visible Sections, Subsections, Quickviews, and Tables Default
Hiding Section, Subsection, Quickview and Table Content Available
User Control of Visibility with See More/See Less Links Available:

  • With SAP Fiori elements for OData V2, the links are See More/See Less.
  • With SAP Fiori elements for OData V4, the links are Show More/Show Less.
Visible Smart Form Fields Default, you can hide them in certain conditions.

Content Area


Navigation Bar

By default, the anchor bar is generated when the object page has at least one section.

It lets users navigate to the individual content area sections.

You can:

  • Hide the anchor bar when you only have one section.
  • Replace it with a tab bar.

With extensions, you can replace the buttons with another type of control.

For more information, see:


Sections and Subsections

You can add sections and subsections to the content area.

Sections contain only subsections. You build the subsection content with tables, charts, and forms.

For more information, see: Sections and Subsections.


Reuse Components as Sections

You can embed a reuse component as a section in the object page.

Warning
A reuse component that is used in an SAP Fiori elements-based application cannot be used in a freestyle application.

Consult the development team on the requirements for the reuse component.


Subsections

With SAP Fiori elements for OData V2, you can include one or more smart link contacts in the subsections.

The smart link contact can include a contact list and a quickview of the contact details.

For more information, see:


Tables

You can include a table in a subsection.

For more information on SAP Fiori elements capabilities for tables, see the articles under SAP Fiori Elements: Table, starting with Table Types.


Smart Charts

You can include a single smart chart facet in a subsection.

In a smart chart, you can:

  • Display measures, aggregations calculations, and dimension categories as labels in the chart.
  • Add actions to the toolbar for a smart chart and define whether they are enabled always or only after the user selects part of the chart for the action.

For more information, see Smart Chart.


Variant Management for Tables and Charts

You can turn variant management on for:

  • All the tables and charts on the page
  • Individual tables and charts

For more information, see Variant Management.


Address

You can add one or more address fields:

  • As a separate subsection
  • As part of a field group within a subsection
  • To a quick view with smart link navigation

For more information, see:


Forms

You can add action buttons to the toolbar for a form contained in a subsection.

In the subsection toolbar, the action types can be:

  • Actions that occur in the system while the user stays on the object page.
  • Actions that navigate to a different application, for example, when the user can open a purchase requisition from a specific purchase order.

Conditional Enablement of Navigation Buttons

You can enable buttons that navigate the user to another page or application based on the value of a specific field with SAP Fiori elements for OData V4. To achieve this with SAP Fiori elements for OData V2 requires extensions.

For example, you can enable the Generate Purchase Order button only for sales orders with the completed status.

Guidelines
Implement this feature only when the way to enable the button is obvious to end users.

Groups in a Form

You can group fields in a form and assign a name to the group.

Note that the group name is displayed only when a group contains fields.

Growing Text Control

By default, with SAP Fiori elements for OData V4, in edit mode, the default length of the text control allows for the entry of four lines of text.

You can:

  • Change the defaullt number.
  • Enable growing mode so the length of the text control on first load allows for the number of lines that you specificy. After the user has entered that number of lines, the length grows by the same number of lines and a scrollbar is displayed next to the text entry area.

Dynamic Side Content

You can display additional content to the right of an object page subsection. Consult with the development team on doing this with a standard extension.

With this feature, the subsection toolbar contains a Show Details/Hide Details action for users to control the display of the dynamic side content. By default, the side content is hidden. You can show it instead. You can also rename the action to make it meaningful to the end user.

    Guidelines

    • Do not use tables in the side content panel.
    • Do not add content that may introduce a horizontal scroll bar to the dynamic side content.
    • For the best view of the dynamic side content, set it to display in 50% of the screen.

    For more information, see:

    Developer Hint

    Subsection Behavior


    Subsection Loading Behavior

    By default, the subsection starts loading after the main object page elements are loaded.

    You can change the loading behavior to load the subsection after the header data is loaded.

    Example

    When the subsection contains a table or chart and you want to allow the user to filter in the header before subsection data loads.


    Width for Content Display in a Subsection

    When you mix content — such as forms and tables — in one subsection, you can adjust the width allotted to each content type to display a table next to a form.

    Content Visibility


    Sections, Subsections, Quickviews, and Tables

    By default, the object page displays these components.

    You can set the entire components or selected content in the components to be displayed or hidden in the content area, according to the object’s state. For example, you can hide the Delivery section in a Sales Order until the order has a status where the delivery is planned.


    User Control of Visibility

    You can turn on these links to allow users to control the display of subsections with the:

    • See More/See Less link with SAP Fiori elements for OData V2.
    • Show More/Show Less link with SAP Fiori elements for OData V4.

    The links display in the bottom right corner of the section:

    • When the subsection is hidden, the See More or Show More link is displayed.
    • When the subsection shows, the See Less or Show Less link is displayed.

    Visibility of Smart Form Fields

    By default, all smart form fields have the high importance setting and show on all screen sizes.

    You can lower the level of importance for the fields to hide them on smaller screens.

    According to the importance assigned to the field, it is displayed as follows:

    • High (default): On all (small, medium, and large) screen sizes.
    • Medium: On large and medium screens only.
    • Low: On large screens only

    For more information, see Responsiveness.

    Related Links

    Elements and Controls