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 Transactional BI Consoles pattern when you must customize the Summary Page and define default layouts for role- and domain-specific transactional dashboards or performance consoles. The Transactional BI Console pattern also helps developers, product managers, and designers define page layouts for the Summary Page of a transactional BI application in a way that accommodates key information. Information on this page is used primarily for reviewing metric data, performing key transactions, and responding accordingly (such as notifying or collaborating with managers, employees, and colleagues).
 
Selection Criteria for This Pattern Return to Top
The Transactional BI Consoles pattern is useful for the following user roles:
  1. An analyst (also a process worker) who analyzes organizational metrics and performs data transactions.
  2. A process worker (customer service representative, clerk) who is responsible for analyzing specific metrics and performing transactions.
Required Screen Elements Return to Top
Component Type
Required Component
Header Region
The header region should contain:
  • Branding logo
  • Links to other dashboards
  • Log out link
  • Links to other Oracle Business Intelligence Enterprise Edition (OBIEE) applications, such as Answers, Reports, and so on
Subpage Tabs
Multiple tabs with at least one tab for summary view. The default name of this tab should be “Summary”. This should be the default selection on launch of the application.
Regions (Containers)
Use regions or containers to contain any structured and non-structured data. No information should appear outside of 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 movement to other tabs.
Icons
Use global icons for quick actions. A tooltip is required for icon descriptions.
Use icons within the container with the tile description.
Data tables use icons for the status columns.
The Alerts and Prompts section uses status icons.
Drop- Down Lists
Use drop-down lists within the containers as filters or to switch between views.
Use a drop-down list in the header section to navigate to different applications within OBIEE.
 
Example Layout of Summary Page Return to Top
The following layout provides enough room to accommodate various metrics, reports, alerts, and transactions used to analyze metrics and perform key data transactions. This layout illustrates how you can place key metrics within the transactional area. The number of metrics on a Summary Page can range from two to four. Users of transactional BI consoles who monitor only a few metrics can place all key metrics and reports in a single row. Users can place critical transactions just below these key metrics. If users perform more than one kind of transaction, they can add additional transaction areas.

Layout 1

Return to Top  
When users must perform tasks apart from their normal transactions and review-related tasks, they can introduce an additional column on the right side of the console. This column serves as a persistent space for related actions and various embedded collaboration tools, such as instant messaging, e-mails, and work lists.

Layout 2

Return to Top  
When users monitor only a few metrics but require more screen areas for transactions, the following layout is recommended. This layout enables users to place KPIs and metrics related to transactional tasks in the left column, and to use two or more regions to the right of the Summary Page for the actual transactions.

Layout 3

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