The object pattern 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 list report, or a related business object. Some object may have child objects which can be accessed via drill down from the object screen.
The object pattern 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.
The header section is the leading content section of an object page. 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 are arranged by frequency of use.
An optional toolbar can be used to hold action buttons related 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.
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 two common types of object:
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 child object page is used to show additional information about one attribute of a business object. It is usually the last screen in a workflow, therefore there will be no further drill down options. However, a child object page can include actions and modal views to display further details.
Child objects from the same level in a workflow can be accessed by implementing the sibling navigation pattern.
To learn more about object hierarchy, see Hierarchy.
Actions may be placed in the navigation bar of the object pattern. Common actions include add, edit, share or save. A tool bar can be used to display additional actions if a tab bar is not present.
Editing details of an object is done by tapping on the edit button on the navigation bar to trigger the edit mode. A modal with form cells will appear to allow the user to make changes on the object.