Selecting a Scope and View in Dashboards
To change the scope or view in Dashboards:
- Click the View dropdown and select either Per Process View or Per Call Tree View.Note: The Estimator Dashboard only supports Per Call Tree View
- Click Change Scope at the top right. A pop up modal will appear. To select a scope, simply choose a Project, a Folder, or a Process and then click OK. This will display data for all processes within the selected Project/Folder/Process in the Statistics, Application, or Estimator Dashboards for analysis.
View Behavior:
- If Per Process View is selected, the scope will only contain the items within the Project, Folder, or Process selected.
- If Per Call Tree View is selected, Blueprint 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
- At the top right of the Select Dashboard Scope modal, there is a toggle for "Include All Roots" that is only present if the view is set to Per Call Tree View. A Root is a process that is not referenced by any other process. If you check this option, all Roots and their dependencies will be displayed as call trees. On the other hand, leaving this option unchecked will only include those processes flagged as a "Main" process and their dependencies in the scope.Note: Blueprint can only find and aggregate dependencies if they were uploaded to the same project
- At the top right of the Select Dashboard Scope modal, there is a toggle for "Include All Roots" that is only present if the view is set to Per Call Tree View. A Root is a process that is not referenced by any other process. If you check this option, all Roots and their dependencies will be displayed as call trees. On the other hand, leaving this option unchecked will only include those processes flagged as a "Main" process and their dependencies in the scope.
Call Tree View
The Call Tree view provides the advantage of allowing you to view analytics on processes and their dependencies (processes they call), rather than only the folder contents. When importing, users may bulk import bots in a .zip file or may have dependencies between processes that exist in separate folders. By providing the option to view statistics based on a call-tree, users don't have to reorganize processes to a common folder for analysis.
Note
"Main" processes are supposed to be the starting point for an automation. The call tree (i.e. all the processes called by a Main process, with all processes they call and so on) is all the code comprising the automation. A process is either designated to be a Main process, or a Sub-Process.
"Main" processes are supposed to be the starting point for an automation. The call tree (i.e. all the processes called by a Main process, with all processes they call and so on) is all the code comprising the automation. A process is either designated to be a Main process, or a Sub-Process.
For UiPath the Main is defined in project.json file.
For Blue Prism the Main is the Main Page of an imported Blue Prism process.
For Automation Anywhere v10/v11 and 360 all roots are identified as Mains.
If you believe that a process has been incorrectly labeled as a Main or Sub-Process, please refer to How to Change the Main Process Label for further instructions on how to modify the label.
For Blue Prism the Main is the Main Page of an imported Blue Prism process.
For Automation Anywhere v10/v11 and 360 all roots are identified as Mains.
If you believe that a process has been incorrectly labeled as a Main or Sub-Process, please refer to How to Change the Main Process Label for further instructions on how to modify the label.