The object floorplan is a collection of attributes surrounding one particular business object. It includes a header area, a content area, and an optional footer area, each made up of vertically-stacked sections. In most cases, users are able to drill down into specific attributes within the object floorplan.
- Use object floorplan for one leading business object that has multiple attributes.
- Use appropriate content section types to ensure screen length remain at a scrollable length.
- Do not use object floorplan for an overview of the entire app.
- Do not use object floorplan for one single attribute of an object (e.g., updates on that object).
The object floorplan is often used in the middle of a workflow to show a leading object that has multiple attributes. Objects can be accessed from an overview, a work list, a list report, or a related business object. To present more information about one specific attribute of an object, use the object details floorplan, which can be accessed via drill down from the object screen.
The object floorplan is a full-screen floorplan comprised of the following areas in sequence: a header area, a content area, and an optional action area. All areas are vertically-stacked together.
Task-based content hierarchy
The object floorplan follows a task-based content hierarchy designed to improve the user’s ability to complete the job at hand. In this task-based content hierarchy, none of the sections or section groups are mandatory, but when they appear, they should follow the suggested sequence.
Header is the leading content section of an object floorplan. It provides a quick view of the most important information about the intended business object. As the first and most important section, it is located in the header area to capture the user’s attention.
B. Contextual content section group
The contextual section provides supplemental information about an object in addition to what is shown in the header. It gives the user a comprehensive understanding of the task at hand.
C. Instructional content section group
The instructional section aims to help the user efficiently complete the current task. Content sections are prioritized based on the current scenario to maximize the user’s ability to complete the job.
D. Referential content section group
The referential content sections provide relevant information around an object. The information here is not always essential to the current job, but immediate access is always available if required. Content sections area arranged by frequency of use.
An optional toolbar can be used to place actions to the object.
The placement of sections is based on their level of priority and their frequency of use relative to the user’s intended task. Based on the actual business scenario, however, this suggested placement can be overridden. For instance, sections can move up to more prominent locations if they fulfill the priority rule or the frequency rule.
Use facets to avoid content overload
To avoid creating screens that are very long and require excessive scrolling, display low-frequency content using facets. These facets sit as the last section on the screen, and users can drill down into them to access more detailed information.
There are three types of layout for the object floorplan:
The standard object is the most frequently-used object layout. It includes an object header to display key information at the top of the screen. Examples of standard objects include work orders, tasks, issues, and parts.
The profile layout is used to display profile objects. It includes a profile header to display profile-specific information and actions.
The retail layout is used to display large images of retail products and to present the user with available purchasing options.
Object view supports both regular and compact widths. Sections in the content area maintain the same vertical structure across compact and regular widths. Individual cells expand horizontally to fit the actual screen size. The header area may behave differently based on different header styles.
The tab bar is an element exclusive to a flat navigation structure, whereas a hierarchical navigation structure will not use a tab bar.
The toolbar is a optional element within both flat and hierarchical navigation structures. For flat navigation, the toolbar is vertically stacked above the tab bar. For hierarchical navigation, when a toolbar exists, it is the only element in the footer area.