Skip to main content

Using Scope and View

How to Set the Scope. The Scope dictates what Projects, Folders, and/or Processes' data is displayed in the dashboards and reports. Click Change Scope at the top right. Choose a Project, a Folder, or…

Sean Ellner
Updated by Sean Ellner

How to Set the Scope

The Scope dictates what Projects, Folders, and/or Processes' data is displayed in the dashboards and reports.

  1. Click Change Scope at the top right.
  2. 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.

How to Set the View

The View dictates how the data is displayed in the dashboards and reports.

  1. Click the View dropdown and select either Per Process View or Per Call Tree View.
    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. 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. Leaving this option unchecked will only include those processes flagged as a "Main" process and their dependencies in the scope.
The Estimator Dashboard only supports Per Call Tree View.

Blueprint can find and aggregate dependencies only if they were uploaded to the same project.

Call Tree View

The Call Tree view provides the advantage of allowing users to view analytics on processes and their dependencies (processes they call), rather than only the folder contents. The call tree (i.e. all the processes called by a Main process, with all processes they call and so on) is comprised of all the code for an automation. 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.

When importing, users may bulk import bots in a .zip file or may have dependencies between processes that exist in separate folders.

Upon import, Blueprint will attempt to label all processes as either a Main process or a Sub-Process.

  • A Main is defined differently based on the type of RPA file imported. Main processes are the starting point for an automation.
  • A Sub-Process is any process that is called by a Main.
If a Main or Sub-Process has been identified incorrectly by Blueprint, a user with proper permissions may change the designation as needed. For more information, see How to Change the Main Process Label.
Mains in UiPath
The Main is defined in project.json file.
Mains in Blue Prism
The Main is the Main Page plus all associated and called pages of an imported Blue Prism process.
Automation Anywhere v10/v11 and A360
All Roots are identified as Mains in AAv10/v11 and A360.

How did we do?

Statistics Dashboard

Contact