SAP Fiori elements is a framework that comprises the most commonly used floorplan templates and is designed to:

• Speed up development by reducing the amount of frontend code needed to build SAP Fiori apps.
• Drive UX consistency and compliance with the latest SAP Fiori design guidelines.

The articles in the “SAP Fiori Elements Framework” section of the guidelines cover all the design possibilities based on the current technical capabilities of the SAP Fiori elements framework and the version used to develop your application.

Video: What is SAP Fiori elements?

Versions

Ask your engineering colleagues what SAP Fiori elements version they will use to develop your app because there are differences in the design options that each version supports. The articles in this section of the guidelines indicate when such differences exist.

Each version of SAP Fiori elements supports a different version of OData (Open Data Protocol), as their names indicate:

• SAP Fiori elements for OData version 2 (V2)
• SAP Fiori elements for OData version 4 (V4)

Usage

Your ultimate decision about whether or not to use SAP Fiori elements should be based on two factors:

• Is the floorplan you want to use supported by SAP Fiori elements?
• Does the SAP Fiori elements floorplan deliver all the features you need to provide to your user? If not, consider building a freestyle application instead.

Please note that the analytical list page and the overview page are only available as SAP Fiori elements.

Supported Floorplans

The following floorplans are available as SAP Fiori elements templates:

Each floorplan can be placed inside the flexible column layout, except the overview page. The overview page must always be implemented as a standalone application that pulls in data from a minimum of two other applications.

Supported Features

Both SAP Fiori elements for OData V2 and for OData V4 offer:

• Message handling
• The global edit flow, which includes draft handling
• Keyboard shortcuts for basic operations
• Custom shortcuts for application-defined actions. Note that custom shortcuts for inline actions on table rows are not supported.
• Seamless navigation across applications with the:
  • Inner app state that stores the state of the current page when the user leaves it, including such details as filter values, table and chart personalization, and the selected tab or section. The app state restores these details when the user returns.
  • Support of the SAP Fiori Launchpad feature called sap-keep-alive mode.
    With sap-keep-alive mode, the app page is restored to the same state it was in when the user left it, including scroll position and table selection. It also improves the performance of the page reload after back navigation.
    However, ensuring the page reflects changes that the user made in an external application before returning to it requires explicit configuration by the application developers.

Only SAP Fiori elements for OData V2 supports the local edit flow without draft handling.

Placeholder Texts

Some UI texts provided by the SAP Fiori elements framework are generic placeholders. Always replace them with text that is meaningful to your user – for example:

For more information, see: Replacing Placeholder Text.

Extensions

It’s possible to create extensions to deliver features that are not supported by SAP Fiori elements. However, this is not recommended because the associated code will need to be maintained.

Related Links

Want to dive deeper? Follow the links below to find out more about related controls, the SAPUI5 implementation, and the visual design.