Oracle Design Guidelines – Queries Design (Part 1)

One of the most important features of a dashboard is its ability to filter information according to specific user queries. The dashboard user should be able to set certain criteria, such as time period, location or product, and then be provided with the relevant data only. The Oracle Design Guidelines explain how to achieve results of this kind efficiently and easily using their BI software.

It is important to remember three points when working on Queries Design. Firstly, ensure that only the required number of columns are featured in any report. The key to effective filtering is to exclude all unnecessary information, which of course includes columns. Secondly any aggregations should be conducted at the report level instead of views. Similarly all column formatting should be conducted at this level also.

In order to ensure that column formatting is conducted at the report level, the required formatting should be saved at this level. Do not save your formatting selections as system-wide defaults for your application. This will mean that the formatting will be carried out at the incorrect level. The column formats recommended by Oracle are:

  • Font: Size – 9, Style – Regular, Color – White
  • Column Format Column Heading: Size – 9, Style – Bold, Background Color – #E7E7F7
  • Data Format, Override Default Data Format Option – should be selected.

In terms of filters, presaved filters should not be used in Oracle BI content. It is also important to avoid any hardcoded values in the report filters if possible. However some reports will require these values to be included.