Statistics Dashboard

Updated by Stefenie Stockbridge

The Statistics Dashboard (top) provides analytics about a set of imported process.

Accessing the Statistics Dashboard

  1. Choose RPA Dashboards and Reports dropdown in the main header.
  2. Select Statistics.
  3. Click the View dropdown and select either Per Process View or Per Call Tree View. This will change the available reports in the center dropdown.
Per Process View will only contain the items within the Project, Folder, or Process selected.

Per Call Tree View will search for dependencies of each Main or Root process and add them to the current scope, even if they weren't in the initial folder or process selected.
  1. Select the desired scope on the top right by clicking Change Scope and click on ok. For more information on selecting a scope, please see Selecting a Scope and View.

Using the Statistics Dashboard

Metrics available on the Statistics Dashboard include:

  1. Total Actions: This is the combined number of Commands and Variables the process has.
  2. Total Processes: The total number of processes in the selected Scope.
  3. Refresh: Retrieves the most current processes from the selected scope for analysis and display.
  4. Complexity of Processes Graph:  Shows a graph of every process in the selected scope in order of descending complexity. Complexity refers to the Cyclomatic complexity of a process. The user can hover over the bars on the graph to see which process it represents.
  1. Size vs Complexity: A scatter graph showing the “number of commands” vs “complexity” for the selected scope. Users can also click on the graph to expand it and hover their mouse over the dots to see which process the dots represent.
  1. Process Stats in Aggregate: Displays average, total and/or max (highest) metrics for all processes in the selected scope.
The count for Duplicate Processes row only includes absolute duplicate processes, which are determined algorithmically on import.

Duplicates are defined as the same bot being imported multiple times to Blueprint. The Bot ID from the source tool, time of creation, time of last edit, and contents must all be the same for a bot to be considered a duplicate.


How did we do?