What Are Saved Customizations for Dashboard Pages?

Saved customizations allow users to save and view later dashboard pages in their current state with their most frequently used or favorite choices for items such as filters, prompts, column sorts, drills in analyses, and section expansion and collapse. By saving customizations, users need not make these choices manually each time that they access the dashboard page.

Users with the appropriate permissions and dashboard access rights can perform the following activities:

Save various combinations of choices as saved customizations, for their personal use or use by others.
Specify a saved customization as the default customization for a dashboard page, for their personal use or use by others.
Switch between their saved customizations.

For information on using saved customizations, see "Applying Saved Customizations" and "Clearing Your Current Customization."

For information on saving customizations and editing saved customizations, see "Saving Customizations" and "Editing Saved Customizations."

Example Scenarios for Creating and Using Saved Customizations

This section describes two example scenarios that describe the creation and use of saved customizations.

Scenario 1: Saved Customizations Created by a Group for Use by Others

An IT group in a consumer goods company builds a master dashboard that contains the content that various product groups need to view. The dashboard contains filters and prompts from which members of the product groups would ordinarily make customizations to view relevant results.

The master dashboard contains two analyses, one that shows sales for the east, west, north, and south regions, and another that shows all products shipped in those regions. The analysis for sales by region contains a prompt that allows users to select their particular region. The analysis for all products shipped contains a filter that allows users to select their products.

An IT consultant customizes the view for the Fizzy Brands product group for each region. The consultant first selects the east region and the Fizzy Brand products from the filters and prompts on the dashboard, and then saves these choices as a customization that can be shared by other users. The consultant then assigns this customization as the default view customization to members of the east region group that sells Fizzy Brand products. The consultant repeats this process for the west, north, and south regions.

When a Fizzy Brands sales representative for the western region signs in to Oracle Business Intelligence and views the dashboard, the representative initially views sales and shipment information based on the region and product choices assigned as the default view customization for that group. All sales representatives in that group who would typically make identical choices for region and product no longer have to do so.

Scenario 2: Saved Customizations Created for Use by an Individual User

A business user's dashboard contains two reports, one that shows sales for all regions, and another that shows all products shipped. Each report contains a prompt, allowing the user to select a particular region and product. The user selects the eastern region and the Fizzy Brands product. The dashboard refreshes to show the user this view of the data. The user saves this view as a customization, indicates that the customization is for personal use, and that it is the default customization the user wants to see when viewing the dashboard. Then, this user creates additional combinations of the product and region sets in which the user is most interested, and saves them for later retrieval. The user can also access customizations that were saved by the IT group as shared customizations. To view sales in the western region for Fizzy Brands, the user clicks the Page Options button, selects Apply Saved Customizations, and selects the view named Dollar Sales, Western Region, Fizzy Brands. The dashboard refreshes with the new view of the data.