Applications User Experience
Fusion Reporting
User Interface Design Document
Version 0.1
July 7, 2008
Copyright © 2008 Oracle Corp. All Rights Reserved. Confidential.
|
author: |
Heather Cottingham |
|
contributors: |
|
|
reviewers: |
|
|
approvers: |
|
Revision history
|
version
|
date |
author |
notes |
|
0.1 |
March
4, 2008 |
Heather
Cottingham |
Created |
|
|
|
|
|
Contents
About
this document
Executive summary
Assumptions
Definitions
Requirements
- Appearance
- Navigation
- Viewing
- Hover
- Folders
- Contents
About this document
This document specifies default state of the Fusion Reporting and Analytics pane. It is unknown how much functionality may need to be built. See the list below for details. Most content will be provided as part of other projects, but get surfaced here.
Executive Summary
The Reporting and Analytics pane will be a default pane in the regional area. It will contain a list of all reports in context from BIP and OBIEE that are available to the user.Assumptions
- Users will not always print reports out, they may be emailed, downloaded or viewed.
- Printing of non-reports is always immediate.
- Reports are not always run immediately. Some may be required to be scheduled.
- Not all reports can be accessed through the reporting pane.
- The Reporting pane will always be the bottom-most pane in the regional area.
- Users will be able to add reports to the pane, both during and after report creation.
Definitions
- Report - A document that can be scheduled by end users. A report is accessed by a local, regional, or global named report link which opens an OBIEE window. Reports are not required to be scheduled, but can be viewed immediately.
- Printable Content - Formatted information that can be printed by end users. A non-report document is accessed by a local print button or action
menu item which displays a PDF.
- Process - An automated activity that can be scheduled by end users. A non-report process is accessed by a local button or link which displays scheduling UI.
- OBIEE - Oracle Business Intelligence Enterprise Edition is a collection of dashboards, scorecards and other analytic tools including access to BIP.
- BIP - Business Intelligence Publisher reports, formerly known as XML Publisher, consist of a data template, layout template(s).
- Report Center - Common term for the OBIEE home page. Intended to be a globally accessible area where users can access all reports.
Requirements
In the default out-of-the-box state, the different reporting content will be offered for different roles.
Reporting and Analytics Pane - located in the regional area
Reporting and Analytics Dashboard Region - can be addded from the catalog
Reporting Center - contains links to all OBIEE and BIP reports (may contain links to Hyperion reports)
Appearance
The appearance of the Reports and Analytics pane will follow Fusion standards.
Navigation
- Ability to launch reporting engines from Reports and Analytics pane.
- Ability to launch Report Center and Hyperion from Navigation menu
Viewing
Users can view reports in the following ways:
- Clicking on the report name in the Reports and Analytics pane. The report will open in another window. The local area will not change.
- Clicking on the view icon in the hover bubble.
- Selecting a report name in a drop down button or link in the local area.
Folders
- Available reports are contextual based on the user's security, role and task.
- Not all reports will be available in the reporting and analytics pane. All reports should be available in the Report Center.
- Folder can have subfolders.
- If no reports are displayed for a folder, the folder should be hidden.
- Standard folder should exist in all applications:
- My Reports - Reports the user has created
- My Favorites - Reports the user has marked as Favorite
- Recent Reports - Reports that the user has recently run
- Open Issue: Implementation wise, do these corresponding with OBIEE folders?
- Folder name truncation should be automatic based on the width of the pane. If truncation is not available, short and long report names will be needed.
- Icons should not be used in the tree to increase space for report names.
- Open Issue: What is the mapping of Reporting Pane content and OBIEE foldering structure for the current user? Is this going to be handled by selecting folders for a particular context or by a tagging mechanism? What is possible technically?
Hover
Hovering over a report name in the reporting and analytics pane will display a pop-up window with additional information and actions.
- Contextual actions in the hover bubble are based on permissions and availability. These include:
- View / Open - Clicking on the report name in the page will immediately display the report in a new window.
- Create - will take the user to the create report screen. In certain cases, it will take the user to a set of pages to create complex reports. If the report is an OBIEE report, the user will be taken to the OBIEE create report page. If the report is an Essbase report, the user will be taken to the Hyperion Essbase create report page.
- Duplicate - will duplicate the report and open the properties dialog and require the user to give the report a new name
- Edit - will open the report properties dialog and allow the user to edit the parameters shown or the layout
- Rename - will open the report properties dialog and allow the user to save the report with a new name.
- Schedule - will take the user to the report properties dialog with the schedule section opened.
- History- will open a dialog showing the history of all reports run, if available. OBIEE reports will generally not have any history saved.
- Favorites - will add this report to the user's favorites.
- View / Open - Clicking on the report name in the page will immediately display the report in a new window.
- Information presented in the hover bubble will be pulled from existing metadata. Some examples may include:
- Full report name
- Create by user
- Create date
- Last run date
- Type
Content
Home
- Reporting and Analytics dashboard region (or portlet ?) -- not accordion pane -- is needed
- Should provide access to all OBIEE content that the user has access to. This may translate into the top level folders in OBIEE.
Workarea and Transaction Dashboards
- Need to provide access to OBIEE content relevant to the current context
- Dev team needs to have the ability to “tag” or register content that is relevant to a particular context (workarea or dashboard)
- Customers needs to be able to customize what is shipped out of the box, including creating new reports and registering them so they will appear in the appropriate Reporting & Analytics pane in workareas and dashboards.
Report Formats
Reports can be displayed in any of the following formats (.doc, .xls, .pdf, .rtf, .ppt, .html, Flash), although we expect most reports to be PDFs. Teams producing documents in these formats are responsible for the accessibility of their reports. For example, teams producing PDFs will need to follow Adobe's instructions on how to create accessible PDFs from their website at http://www.adobe.com/accessibility/
Frame Work Functionality Needed
- Add Report to Pane - A flag that will add the report to the reports and analytics page. This flag will need to be available starting at report creation time, although users will want to add reports at a later date as well.
- Max Number of Reports shown - The maximum number of reports shown in a single folder of the pane. This limitation will prevent the number of reports listed from getting too long.
Reporting Flow Chart
Open Issues
- Is there any possibility that the reporting pane will be empty for a particular user? If so, should we request that it be hidden?
- Who owns the Unified Report Catalog?
- Who owns Report Center? When will there be a detailed design for it?
- Will XML Publisher work for UX's needs?
- Will there be Discover like reporting to support ad hoc queries? (SCM)
Related Links