{"id":6880,"date":"2022-03-16T12:21:00","date_gmt":"2022-03-16T11:21:00","guid":{"rendered":"https:\/\/sovanta.com\/?p=6880"},"modified":"2022-03-18T10:05:19","modified_gmt":"2022-03-18T09:05:19","slug":"6-guidelines-how-to-design-sap-fiori","status":"publish","type":"post","link":"https:\/\/sovanta.com\/en\/6-guidelines-how-to-design-sap-fiori\/","title":{"rendered":"6 Guidelines: How to design SAP Fiori"},"content":{"rendered":"\n

SAP Fiori is the fast track to applications with a good user experience. But although the SAP standard can do a lot out of the box, we often hear in customer conversations that the right use, the right configuration, and also useful extensions are required. To design SAP Fiori correctly for our customers, Daniel Grab is on board as UX designer at sovanta and tells us here a few guidelines he follows in SAP Fiori projects:<\/p>\n\n\n\n

1. Stay as close as possible to the standard! <\/h3>\n\n\n\n

In general, we always try to stay as close as possible to the SAP standard. This makes it easier for the customer to update to newer SAP UI5 versions later on. Because with custom elements, there is a possibility that they will no longer function as desired after an update and will have to be adapted again. However, if we can’t find a ready-made component in the standard that fits the solution, then we look around in the SAP Fiori Library or UI5 Library for existing components that we can combine in a meaningful way to become the solution. If that doesn’t work, then of course we build custom controls. Fortunately, there are already some available in our sovanta Fiori Extension Library.<\/p>\n\n\n\n

\n \n \n\n
\n\n
\n\n
You are not alone: SAP Fiori offers an extremely wide range of possibilities and correspondingly many sources of knowledge. To maintain an overview, it is always worthwhile to have close exchange with SAP Fiori experts from development and design.<\/div>\n \n \n <\/div>\n\n<\/div>\n\n\n <\/div>\n\n\n

2. Not everything is possible in every SAP Fiori version\u202f <\/h3>\n\n\n\n

The decisive factor for a SAP Fiori project is the version number with which a customer operates its SAP system landscape. For us designers, this means that some features cannot be used in earlier versions. In the SAP Fiori Design Guidelines<\/a> and the SAP UI5 Samples<\/a>, earlier versions can be selected and tested to make sure what is possible and what is not. <\/p>\n\n\n\n

3. Select floor plan according to the task <\/h3>\n\n\n\n

What task should the SAP Fiori app fulfill? We get to the bottom of this question together with our customers in a workshop at the beginning of a project. Only when we know the task can we select the right floor plan. The SAP Fiori page “When to Use Which Floorplan<\/a>” also helps here. In general, floor plans are to be understood as templates<\/a> that fulfill different tasks. There are floorplans to \u2026<\/p>\n\n\n\n