SAP Fiori Flat Object View

Discussion Forum SAP Fiori Design SAP Fiori Flat Object View
Viewing 2 posts - 1 through 2 (of 2 total)

I am just getting started on SAP Fiori for one of my clients, reading through all the training material. Now I came across the section of Floorplans and in detail the Object view vs. Flat Object View. If I have an object view that contains multiple tabs than it is suggested in the guidelines that when the user goes into edit mode, the Flat Object View is presented. That means that the tabs are being removed and instead the content of the tabs are presented as a list. The argument for this is “prevents user input and validation errors from being scattered across multiple tabs”. But I cannot really follow the line of argumentation as from my point of view the change in layout from display to edit view is quite big. I would argue that the user is confused with the sudden change. My idea would be to visually fit the two modes to one another: the tabs on the display view would be treated like jumpmarks. All content would be displayed as a list and instead of opening the tabs in a new page clicking on them would result in “jumping” to the right position on the list. For me that would be more consistent behavior instead of changing the layout completely when going in edit mode. What do you think about it? Does anybody of you uses the two views and possibly performed a user test on it? I would be very interested in hearing your thoughts.

Chief Designer
SAP SE

Hi Cindy,

thank you for your comments and questions.

You are right. The transition between tabbed and flat layout is not ideal as it forces the user to orient again. On the other hand, we need to avoid heavy editing tasks in a tabbed interface as we used to have them on our traditional transactions. In the past, users had a hard time tracking validation issues and dependencies across multiple tabs and this is something we definitively need to avoid.

In the Object View floorplan, you can reduce the gap between edit and display either by using a flat design in both cases if the content allows (as scrolling usually is cheap) or by placing editable content within few tabs that then easily translates into a flat layouts. In general, we have seen this transition to work quite well with end users, so that I believe that when employed carefully, you will not run into issues with this approach (definitively better than data-loss on tab change or hidden error-messages).

What you suggest is to use¬†the “tabs” as anchors to scroll to the right position on the page. In fact, this is the behavior we have defined for a new floorplan called the Object Page, which will be available with UI5 1.32. The Object Page features exactly this anchor scrolling that you can use both in display and edit mode. Depending on the implementation the Object Page will be able to offer local edit per section or global edit for the entire page.

I hope this answer was helpful for you.

Best regards

Kai

Viewing 2 posts - 1 through 2 (of 2 total)
 

The forum ‘SAP Fiori Design’ is closed to new topics and replies.