|
|
| |
| Design Patterns and Guidelines for Oracle Applications |
|
|
|
|
|
|
|
|
|
|
| |
Receive occasional updates on Applications User Experience such as new articles, new tools, meeting our staff, and opportunities to get involved in our Customer Programs. |
|
|
|
|
|
| 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 Correlating and Comparing pattern when you must customize a metric details page and define default layouts for role- or domain-specific dashboards and business performance consoles. The Correlating and Comparing pattern also helps developers, product managers, and designers define page layouts for the metric details page of a Business Intelligence (BI) application to accommodate key information. Information on this page is used primarily for comparing and correlating performance indicators and metrics. |
|
|
|
|
|
Selection Criteria for This Pattern |
 |
|
|
 |
|
|
|
|
|
The Correlating and Comparing pattern is useful for the following user roles:
- A CXO-level user who reviews the overall health of the organization and must be aware of any red flags and key alerts.
- A middle manager (also an analyst) who reviews key metrics, analyzes problem areas, and acts accordingly.
- A process worker (customer service representative, clerk) who is responsible for analyzing specific metrics and performing transactions.
|
|
|
|
|
|
Required Screen Elements |
|
|
|
|
|
|
|
|
|
The Correlating and Comparing 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 a Metric Details Page |
|
|
|
|
|
|
|
|
|
The following layout provides a typical arrangement of page regions to accommodate one or more metrics, KPIs and reports for key tasks related to data correlation and comparison in a metric details view. The example below is good for representing metrics with bigger timelines and complex data on the horizontal axis.
Figure 1: An Example of a Metric Details Page for Correlating and Comparing Tasks
A metric details page could also contain related actions and collaboration tools. The following example shows the layout for a metric details page with a fixed width area containing related actions.
Figure 2: An Example of a Metric Details Page with Related Actions
|
|
|
|
|
|
|
|
|
|
|
