5. Component Design

With the datasets presenting the data in their final phase, they can be utilised inside of components.

Components display information into such structures as charts, grids, gauges and HTML components.

With this latest version, we have streamlined the Dashboard Launchers (HTML components) that take users from one screen to another. Previously, this was multiple different launchers, all independently maintained. Whereas now, this is a single component, with updated styling.

This Dashboard Launcher also works in a fundamentally different way. Previously, any text in this Launcher would not have been easily translated. Whereas now, we have introduced software features to instead call the written text from the stored database objects referenced. For example, if a user clicks on “Executive Summary” in the dashboard launcher, this piece of text actually comes from the saved name of that Dashboard. Meaning, that the component itself isn’t translated, it’s calling elements internally that are already translated.

We also handle the Dashboard grouping in the same way. Where the “Cost” Dashboard is in the group of “Analysis”, this is a call internally to the group where the "Cost" dashboard resides in the internal group structure. If you explore the solution via the “View Dasboard”, you’ll see that Grouping in action, where each of the dashboards have been published into their own groups, and those group names are the ones being displayed.

We’ll cover the translations later, but when a French user signs in, the “Analysis” group container in the Dashboard Launcher is shown as “Analyse”, because that is the saved French name of the Group where Volume is published.

Next Module - Dashboard Design