Oracle Usable Apps | Applications User Experience Simplicity, mobility, extensibility
   
 
Customer Role: How User Experience Research Is Conducted
 
Metric Details Page Layout
The Metric Details Page Layout pattern set helps developers and product managers define the layout of the metric details 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 details page.
 
   
   
 
Use the Transactional BI Consoles pattern when you must customize the metric details page and define default layouts for role- and domain-specific transactional dashboards or performance consoles. The Transactional BI Consoles pattern also helps developers, product managers, and designers define page layouts for the metric details 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

The Transactional BI Consoles 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 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 layout below provides enough room to accommodate various metrics, reports, alerts, and a transactional area to analyze various metrics and perform key data transactions. The example below demonstrates how key metrics could be placed with the transactional area. In case the users of the Transactional BI Consoles pattern need to monitor very few metrics while using the console, key metrics and reports could be placed in one single row. The number of metrics in a Summary Page could range from 2 to 4. However, do not clutter the Summary Page with too many metrics in a single row.

The transaction area just below the key metrics would be an ideal place to accommodate key transactions critical to the user. In case the user needs to perform more than one kind of transaction, an additional transaction area could be added below.

Layout 1

Return to Top  
In some cases, the user may also need to take additional actions, apart from his normal transactions, and review related tasks. In such situations, an additional column could be introduced and placed in the right column of the console. This additional column serves as a persistent space to place related actions as well as various embedded collaboration tools, such as instant messaging, emails, work list, etc.

Layout 2

Return to Top  
In case there are very few metrics that the user needs to monitor, and more screen areas are required for the transaction, the layout below could be used. This allows users to place KPIs and metrics related to the transaction tasks in the left column. The right side of the Summary Page could then be used to accommodate two or more page regions for the transactions.

Layout 3

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