Oracle Design Guidelines – Queries Views (Part 7)

In the previous six posts, we have been look at how to correctly generate reports that are based on user queries. In this, the final post of the series, we will discuss Pivot Tables, Column Selectors and Report-Level Prompts.

Pivot Tables are integral components of many dashboards, but they do require certain specific settings in order to correctly generate them in reports. Firstly, it is important to always set aggregations to column level preference. This preference should be set directly in the criteria tab, and pivot table aggregation should only be used when it is not possible to set it through the criteria tab. As with all tables, the formatting for lines and columns and of course font styles is very important. The Oracle Design Guidelines recommend that the same color code be used for the regular table lines in the pivot table, and they also recommend a standard font colour. This can be set easily using the Format Labels and Values options, as can be seen in the picture below, and on the Oracle Design Guidelines page.

It is important to avoid any prompts at report level, unless absolutely necessary. When a user requests a particular report, all filtering and formatting should occur automatically, without the need for any additional prompts. Instead prompts should be set up as dashboard page prompts, that are embedded into the dashboard itself.

Additional things to consider when setting up dashboard views include the use of HTML. No HTML content should be inserted into views, besides the basic tags that are permitted by the static text views. A large set of custom color schemes are also provided by the Oracle Design Guidelines, including hexadecimal codes.