6. Dashboard Design

With our components set, they’re now displayable on each of our dashboards.

By now, you may have noticed that much of all of the data processing is handled earlier on in the data pipeline stage. The Dashboard is the final culmination of displaying data, but there are still a couple of points to reference.

Each dashboard utilises the exact same timespan (apart from Weekly Insights!*) where they are viewing data up to the length specified in the View in the Connection layer.

*Weekly Insights is, unsurprisingly, only showcasing data in the last rolling week. E.g. new data since the point of refresh up to, and including, 7 days ago.

Should you, or your customers, access the dashboards and wish to extend the timespan of what they can see, this is set in the View itself. It does however require you to ensure you have also collected up to the amount you are expecting to show. For example, you can set the View to showcase three years of information (1095), but if the database collating the Print Management data contains a year, it will only display up to a year of data onscreen. This point will also be covered in more detail in a separate topic for your desired Print Management connector, but this is an important detail to remember for support scenarios.

Each of the dashboards do utilise particular flags that have been set in the View, Datafeeds and Datasets. Each dashboard uses the flag of “Job Status Text” to only show jobs that have been defined as “Successful”.

The outlier of this is the “Savings” dashboard. This utilises the flag in the opposite way, where it only displays data for jobs marked as “Unsuccessful”, e.g. jobs that were cancelled or otherwise not fully performed, and marked by the Connections' SQL View as not fully successful.

Next Module - Organisations