Oracle Usable Apps | Applications User Experience Simplicity, mobility, extensibility
   
 
Customer Role: How User Experience Research Is Conducted
 
Summary Page Layout
The Summary Page pattern set helps developers and product managers determine the best layout for the Summary Page based on user roles, usage patterns, and data needs. The pattern set helps them understand the advantages and disadvantages associated with displaying metrics, non-structured data, links, alerts, and prompts on the Summary Page.
 
   
   
 
Use the Analyzing and Acting pattern when you must customize a Summary Page or define default layouts for role- or domain-specific dashboards and business performance consoles. The Analyzing and Acting pattern also helps developers, product managers, and designers define page layouts for the Summary Page of a Business Intelligence (BI) application in a way that accommodates key information. Information on this page is used primarily for analyzing metric data, identifying problem areas, and responding accordingly (such as notifying or collaborating with managers, employees, and colleagues).
 
Selection Criteria for This Pattern Return to Top
The Analyzing and Acting pattern is useful for the following user roles:
  1. A middle manager (also an analyst) who reviews key metrics, analyzes problem areas, and acts accordingly.
  2. An analyst (also a process worker) who analyzes organizational metrics and performs data transactions.
  3. A process worker (customer service representative, clerk) who is responsible for analyzing specific metrics and performing transactions.
Required Screen Elements Return to Top

The Analyzing and Acting pattern contains the following screen elements:

Component Type
Required Component
Header Region
The header region should contain:
  • Branding logo
  • Links to other dashboards
  • Log out link
  • Links to other OBIEE apps such as Answers, Reports, and so on
Subpage Tabs
Multiple tabs with at least one tab for the summary view. The default name of this tab should be Summary. This page should be the default selection when the application launches.
Regions (Containers)
Use regions or containers to contain any structured and non-structured data. No information should appear without a region.
Navigation Links
The Summary Page tab has the navigation links in the top-right section. Every region may have links that enable drill-down navigation or movements to a different tab.
Icons
  • Use global Icons for quick actions. A tooltip is require for icon description.
  • Data tables use icons for the status columns.
  • The alert and prompts section uses status icons.
Drop-Downs Lists
Use drop-down lists within the regions as filters or to switch between views. Use a drop-down list in the header section to navigate to different applications within Oracle Business Intelligence Enterprise Edition (OBIEE).
 
 
Example Layouts of the Summary Page Return to Top

The following layout provides enough room to accommodate various metrics, reports, alerts, related actions, and collaboration tools used to analyze metrics and respond accordingly. The following example is a three-column arrangement of page regions. The first two columns contain various KPIs, metrics, and reports. The third column serves as a persistent space for related actions and various embedded collaboration tools, such as instant messaging, e-mails, and work lists.

The horizontal axis arrangement is useful for representing metrics with bigger timelines and complex data. Users can display the top four metrics or reports in the visible region and stack the rest of the metrics or reports below. Users can access these additional metrics or reports by scrolling the page vertically. However, if you have more than seven or eight metrics or reports, it is best to create more logical groupings and assign a new tab for these groups.

Figure 1: Three-Column Layout

Return to Top  
The following layout is useful when you want to focus on one primary metric or report. Other metrics or reports can be arranged below. Related actions and collaboration tools can remain in the right column for quick access.

Figure 2: Layout for Primary Metric Representation

Return to Top  
The following illustration represents a Related Actions area, where you can:
  1. Accommodate key links that enable you to navigate to other applications, share page information, and so on.
  2. Accommodate embedded collaboration tools, such as instant messaging, widgets, and gadgets.
  3. Display contextual information through real simple syndication (RSS) feeds.

Figure3: Local Action Area

 
 
Oracle.com  |  About Oracle  |  Careers  |  Contact Us  |  Legal Notices  |  Terms of Use  |  Your Privacy Rights