The dashboards are a visual representation of the results from automation flows. With the dashboards, it's easy to monitor data and results, and share them with colleagues and management.
It's possible to create multiple dashboards, so that every user, project, business unit, or product unit can have their own visual overview.
A dashboard consists of one or more widgets, each showing results configured from the automation flows you've created.
The following widgets options are available under the Dashboard List:
- Flow Trending Area
- Flow Trending Bar
- Most Failed
- Pie Chart
Dashboards are made of individual widgets and we can add any number of widgets to a single dashboard view.
Step 1. Just as with the Report feature in Leapwork, we can set up filters for an individual widget.
Step 2. We can filter them by Flows, Agents, or Run Lists.
Depending on the widget type you select, we can add more filters, configure how they are aggregated, and view the computed results.
Step 3. For the Flow Trending Bar, we can set the timestamp and configure it to include the total time taken to execute the flows and aggregate the results by day.
Step 4. When we click Save, we can see how many flows Failed or Passed each day in the selected date range.
Step 5. To view the underlying data of a given report, we can right-click on the widget and select View as Report.
Step 6. This will open the corresponding report, allowing a deeper understanding of the flow result.
Step 7. Double click on any individual timeframe to get the details of the result. This will open up a panel that includes the view of the actual flow, a video recording of the execution flow, and the corresponding activity logs.
Step 8. We can export this report as a PDF, HTML, or an Excel file.
Step 9. We can choose to save the report for future usage.
Step 10. We can also change the size of the widget from the Dashboards.
Step 11. We can also maximize the individual widget.
Step 12. After maximize it will give a closer look at the chart.
Dashboards are good for a real-time overview and often provide the first signal that something needs to be taken care of. For example, the trend of more failing test cases for regression testing or a business process that generates an unacceptable number of failed flows.
For clarification, please contact our Priority Support.