Select the best option to render dashboards in Oracle Analytics Cloud

February 1, 2023 | 3 minute read
Avinash Krishnaram
Director of Product Management - Oracle Analytics Cloud
Text Size 100%:

As an administrator or author in Oracle Analytics Cloud (OAC), you can select the best option for rendering content on dashboards for your users. This post describes how dashboard content is rendered and the advantages of each option.

Consider an example of a dashboard that has multiple tabs, and each tab includes multiple visualizations. A "dashboard construct" has the following elements in it:

  • Layout – The structure of the dashboard that includes:
    • The organization of the tabs.
    • The layout of visualizations on each tab.
    • Any prompts or filters.
  • Information related to each visualization such as:
    • Subject areas.
    • Columns on the subject areas.
    • The type of visualization (such as chart or table).

When a user opens a dashboard, the system starts to load the dashboard construct, determines where to place the tabs and visualizations, and runs the queries for each visualization as part of rendering the dashboard. You can decide whether users must wait for the dashboard metadata to be loaded completely before any dashboard content is rendered.

The loading of metadata generally happens quickly. For dashboards with many embedded objects (including conditions, dashboard prompts, and visualizations), the loading can take some time and can be sensitive to aspects of application design such as the availability and latency of the data source. As a result, the user might be waiting for the dashboard to render without any feedback and it might look like the dashboard is still loading or that the browser is hung.

Administrators control how dashboards are rendered using the system-level property called Enable Immediate Dashboard Rendering:

  • On – Specifies to render dashboard content immediately, even if some content is unavailable.
  • Off (default) – Specifies to wait for all dashboard content to be loaded before rendering (the behavior in earlier releases of OAC).

System property

Authors can control how dashboards are rendered individually at the dashboard level using options on the Dashboard Properties:

  • Render Content when Available (default) - Specifies to display dashboard content immediately even if some content is unavailable.
  • Wait for All Content - Specifies to wait for all dashboard content to be loaded before displaying content (the behavior in earlier releases of OAC).

Dashboard property

When you specify to display dashboard content immediately, visualizations start to render and data is loaded when the respective dashboard elements are completed, as shown below:

Dashboard render gif

Try the various options with your dashboards and see the results you achieve. For more details, see Performance and Compatibility Options. Visit Oracle Analytics Customer Connect to leave questions or feedback.

Avinash Krishnaram

Director of Product Management - Oracle Analytics Cloud


Previous Post

Five things you may not know you could do with dataset authoring in the Dataset Editor of Oracle Analytics Cloud

Luis Rivas | 6 min read

Next Post


Embedding Fusion Analytics Content in Oracle Application Cloud

Krithika Raghavan | 9 min read