Activation and License Consumption

Updated by Stefenie Stockbridge

How Licenses are Consumed

An Assess license is consumed upon import to either Blueprint Analyze or Blueprint Migrate.

A Migrate license is consumed upon activation and export of the Main process (blue shaded box) within an RPA process. In the example below, exporting this process titled UiPath Sample 1 will consume one Blueprint license, as there is one main (titled Test) within the file. All associated sub-processes will be packaged up in the export, but will not consume additional licenses.

Once a license is consumed, it cannot be reversed or restored. Processes cannot be 'un-activated' and deleting activated processes does not release used licenses.

Activating Blueprint Processes

1. Activate Individually

Blueprint Processes can be activated one at a time by hitting the blue Activate button at the top of the Process Editor when the process is open.

  1. Select a project, folder, or process in the Explorer
  2. Click the Export button in the top right of the Main Content Area
  3. Select Export to Power Automate Desktop
  4. In the dialog box, users will have the option to Activate any processes that have not yet been activated. Additionally, the message will display the number of licenses that will be consumed.
Note: If a process is selected for this operation, the process will need to be activated individually (see Option 1 above) before the export option will be available.

3. Activate in Bulk via Descendants View

  1. Select a project or folder in the Explorer
  2. Click the Artifact Editor button in the top right of the Main Content Area and select Descendants (View). The contents of the project or folder selected is listed
  3. Check the box of all processes that should be Activated
  4. Click Actions at the top left of the table view and select Activate Bots
  5. In the dialog box, users will have the option to Activate any processes that have not yet been activated. Additionally, the message will display the number of licenses that will be consumed.

To learn more, see License and Activity Reporting.

How did we do?