Working with SAP Fiori Design Guidelines

Use the dynamic page layout if you are building a freestyle application that uses the dynamic page header and footer toolbar features of SAP Fiori (versions 1.40 and higher)

Do not use the dynamic page layout if you are planning any of the following scenarios:

• Use SAP Fiori elements, such as the list report, analytical list page, overview page, or object page. These elements already incorporate the dynamic page layout.
• Implement an initial page or object page floorplan. These floorplans already incorporate snapping header and footer toolbar features. The behavior is similar to the dynamic page, but the technical foundation is different.
• Display a small amount of information. In this case, use a dialog instead. If you cannot avoid using the dynamic page layout, use letterboxing to mitigate the issue.

Use the flexible-column layout if you want to create a master-detail or master-detail-detail scenario in which the user can drill down or navigate.

Do not use the flexible-column layout if you are planning any of the following scenarios:

• You want to build a workbench or tools layout. The flexible-column layout is not meant to provide a main column with additional side columns on the left and right or either. If you want to display additional content to enrich the main content and to help users better perform their tasks, use the dynamic side content instead.
• You want to create a dashboard with context-independent pages.
• You want to open multiple instances of the same object type. Use the multi-instance-handling floorplan instead.
• You want to split a single object into multiple columns, or display only a small amount of information.
• You want to embed the SAP Fiori launchpad or overview page into one of the columns.

The following table should help to decide what layout should be used and what type of question you asked yourself for making a decision.

Now that you've learned about the SAP Fiori layouts, put on your thinking cap and help Marco make the right decision in this use case activity.

Do not use this floorplan when you want to show more than one object. In this case, the list report floorplan is a more appropriate solution.

When to use the wizard floorplans

• The wizard aims to help users by dividing large or complex tasks into segments. Use the wizard if the user has to accomplish a long task (such as filling out a long questionnaire) or a task that is unfamiliar to the user.
• The flow should consist of a minimum of 3 and a maximum of 8 steps.
• The wizard can be used for both create and edit scenarios. If your application contains both, consider using the same method for both scenarios – either the wizard, or another create or edit screen, (edit flow or object page).

When not to use the wizard floorplans

• If you have a task with only 2 steps or a format that the user is familiar with, for example, it is part of their daily routine, do not use the wizard as it only adds unnecessary clicks to the process.
• If your process needs more than 8 steps, the wizard will not support those steps as the process is too long and can be confusing for the user. In this case, you should consider restructuring the task.
• Consider if the classic edit screens (edit flow or object page), are more suitable for your use case.

Structure of the wizard floorplan walk-through screen.

1. After calling the wizard, the first step of the floorplan appears.
2. When all necessary fields are completed, a button labelled Step # appears.
3. When completing the last step, a button labelled Review appears.
4. The footer of the wizard holds the cancel button with standard SAP Fiori cancel behaviour.
5. It is possible to have a save or draft button when the form is very long

Displayed is the structure of the wizard floorplan summary page. The review button takes the user to the screen displaying the data.