Oracle Usable Apps | Applications User Experience Simplicity, mobility, extensibility
   
 
Customer Role: How User Experience Research Is Conducted
 
Page Regions

A typical Business Intelligence (BI) application usually contains various common user interface components, such as headers, filters, information containers, navigation links, and buttons. The information typically appears in page regions, which are also called containers. These regions are considered independent units that can accommodate data in various formats, such as graphs, charts, tables, and structured and non-structured data. Regions are subcomponents that are aggregated in a dashboard or a console.

In Oracle Business Intelligence Enterprise Edition (OBIEE), you can easily configure the dimensions, placement, and data type of these page regions using the Page Regions pattern. Using this pattern helps ensure the most ideal and consistent page design and maintenance across all BI applications in the enterprise.
   
 
Selection Criteria for This Pattern
Return to Top
 
 

The Page Regions pattern is useful for the following user role: A user (CXO, analyst, or process worker) who reviews metrics, KPIs, reports, and alerts in a dashboard or console. The information in the dashboard must be grouped into logical and independent regions.

 
 
Required Screen Elements
Return to Top
 
 
Component Type
Required and Optional Components
Page Region Header
The page region header should contain these elements:
  • A title
  • Actions in a drop-down component
  • An icon to collapse and expand the page region
Page Region Body
  • The page region body may contain these elements:
  • Data filters
  • Charts, graphs, tables, text
  • Navigation links
  • Action links
  • Footer information
Data Filters
Optional for page regions. Use data filters only when you must refine the data using one or more filters.
Charts, Graphs, and Tables
Use charts, graphs, and tables to represent analytical data.
Navigation Links
Use navigation links to navigate to different tabs, open new applications, or open Web pages.
Action Links
Use action links for actions related to data refresh, such as Save, Edit and Update.
Alerts
Use alerts to display information specific to a KPI or a report.
 
 
Pattern Sample
Return to Top
 
 

A range of functionality is available that affects the region itself or specific content. Depending on the content and the tasks, development teams may leverage the elements listed in this section as needed. Once the necessary functionality is identified, teams may refer to the region pattern in detail to understand functionality, usage, and types of dashboard regions.

 
 

Figure 1: A Typical OBIEE Page Region

 
 
Main Header
Return to Top
 
 

The header is composed of three elements:

  • Page region title: Describes the nature of content within the page region, such as KPIs, metrics, and alerts.
  • Page region actions: Contains key actions that are applicable to the content within the page region.
  • Minimize page region icon: Enables you to minimize the page region. The title remains visible in a collapsed state.
 
 

header

Figure 2: Page Region Header

 
 
Body Content
Return to Top
 
 

The body content contains the focus of the page region in the form of charts, graphs, text, and non-structured information. Many of these functions have drill-down capability.

 
 

body

Figure 3: Body Content

 
 
Additional Components
Return to Top
 
 

The following additional components to the page regions are also available to help structure and display information.

 
 

1. Extended Region Header

This additional extended region header is composed of three elements:

  • Page region icon: This thumbnail image highlights the nature of the page region content.
  • Page region heading: Includes a short description of the page region content.
  • Additional description: Provides a detailed description of the page region content.

pg reg heading

Figure 4: Region Header (Extended)

 

2. Filter or Actions

The filter values in the drop-down menus enable you to narrow the data that appears in the page region. You can use these filters if page regions contain large data sets in the form of charts, graphs, or tables. You can use one or two filters together. We do not recommend that you use more than three.

filters

Figure 5: Filters

 

Note: When the window is minimized, only one of the additional components appears. See Figure 2.

 
 
Definitions
Return to Top
 
 
Page Region
Refers to the total region covering two or more portlets that contain similar data with analytical and referential purposes. The end user can configure page regions to add more portlets or data containers within the same region.
Sub-regions or Containers
Refers to a subcomponent of the page region that contains the actual data.

layout

Figure 6: Example Showing the Usage of Multiple Sub-Regions in a Page Region

 
 
Example Page Region Layouts
Return to Top
 
 

The following layouts provide enough room to accommodate various metrics, reports, and alerts. The first layout example contains the minimum requirements for a page region. This arrangement is useful when you are trying to represent metrics with static data with few options for refining that data.

 
 

basic container

Figure 7: A Basic Page Region

 
  This second layout example shows the state of a region when it is minimized, displaying the very minimal requirements to restore and identify the region.  
 

minimised pae layout

Figure 8: A Minimized View of a Page Region

 
  The third layout example is another arrangement of the page region that OBIEE could easily generate when you need to display additional detailed metrics and report details. Structuring data with filters in this way is useful when you need to analyze and refine the available data.  
 

add comp region

Figure 9: Layout for the Page Region with an Additional Component

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