How to Change the Main Process Label for Estimations

Updated by Sean Ellner

Mains vs. Sub-Processes

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

The Main-to-Subprocess switcher was designed to be used exclusively within Blueprint Estimator in an effort to map out and visualize automations and estimate migration timelines.

The Main-to-Subprocess switcher does not affect licensing.
  • A Main is defined differently based on the type of RPA file imported. Main processes are the starting point for any automation.
    • A Main will consume a license upon import (Assess) and activation (Migrate).
    • Once an item has been identified as a Main, Blueprint licensing will always consider it a Main.
  • A Sub-Process is any process that is called by a Main.
Mains in UiPath
The Main is defined in project.json file.
Mains in Blue Prism
The Main is the Main Page of an imported Blue Prism process.

IMPORTANT: If your Blue Prism automation has been developed with multiple Main Pages; when imported into Blueprint, each Blue Prism Main Page will be identified as a Main.
Automation Anywhere v10/v11 and A360
All Roots are identified as Mains in AAv10/v11 and A360.

Change Main/Sub-Process In Process Editor

In the Process Editor, users can switch processes between being labeled as either a Main or a Sub-Process by flipping the toggle at the top left.

Change Main/Sub-Process In Descendants View

Users can also edit Main or Sub-Process labels in bulk from the Descendants View. To do so, simply select the checkbox next to the processes you want to modify, click the actions dropdown, and choose either "Convert to Main" or "Convert to Sub-Process".

How did we do?