Home & Global Resources
Blueprint Assess
Getting Started
Settings & Administration
Analyze
Overview
Scenario Demonstration
Features
Process Details
Blueprint Migrate
Getting Started
The Blueprint User Interface
Change Your Password
Open a Project
Organize Artifacts and Assets
Close a Project
Status Indicators
Jobs
Exporting from Source RPA Tools
How to export a UiPath Automation Project from UiPath Orchestrator
How to export .bprelease files from Blue Prism
Blue Prism VBO Matching on Import
How to Export .zip files from Automation A360 Control Room
Importing
Exporting
RPA Export from Blueprint
Variable Prefixing
Why We Create Multiple Similar Subflows During Migration
Understanding Wrapper Flows in Power Automate Desktop
Setting up defaultRunDotNetScriptReferences
AsEnumerable Support
XmlDocument Support
Bulk Reimport/Recalculate
Metabot Migration - Best Practices
Artifacts Management
Base Artifact Types
Creating and Managing Artifacts
View and Edit Artifacts in the Utility Panel
Concurrent User Activity in Artifacts (Steal Lock)
Using Descendants View
Global Actions
Rules
Introduction to Rules
Using Rules
Using Rules CSV
Common Procedures
Custom Action Mapping
Reuse Mapping to Power Automate Desktop
Manual Reuse
TODO, Error, and Robin Mapping
Script Mapping
Variable Name Dependency Mapping
Variable Renaming and Initialization
DLL/Method Invocation Mapping
Unresolved References
AA Metabots
Work Queues Mapping
Rules Wizard
Solutions & Best Practices
Working with Migration Output in Power Automate Desktop (PAD)
Blueprism to PAD Migration Output Details
UiPath to PAD Migration Output Details
AA to PAD Migration Output Details
RPA Value-Mapping Assessments
Why Choose Blueprint Cloud vs. On Premise ?
Setting up SAP for RPA
API & Developer Resources
REST API Request Header and Parameters
REST API Request Body and Parameters
REST API - Listing Artifacts in the Request Body
REST API - Defining an Artifact in the Request Body
REST API - Defining a Comment in the Request Body
REST API - Defining a Reply in the Request Body
REST API - Defining a Trace in the Request Body
REST API - Filter Parameter
REST API - Defining a User in the Request Body
REST API Requests
REST API - Add Attachment to Subartifact Request
REST API - Get Artifact Request
REST API - Add Traces Request
REST API - Get Project by Id Request
REST API - Update Custom Choice-Property Type Request
REST API - Publish Comments Request
REST API - Publish Artifact Request
REST API - Update Comment Request
REST API - Delete User Request
REST API - Add Comment Request
REST API - Close Review Request
REST API - Get Discussion Status Request
REST API - Update Reply Request
REST API - Get Attachment Request
REST API - Delete Comment Request
REST API - Create Project Request
REST API - Get Group Request
REST API - Rate Comment Request
REST API - Get Child Artifacts of Artifact Request
REST API - Discard Artifacts Request
REST API - List Artifacts Request
REST API - Rate Reply Request
REST API - Move Artifact Request
REST API - Delete Attachment Request
REST API - List Projects Request
REST API - Get Blueprint Product Version Request
REST API - Update Standard Choice Property Request
REST API - Get Review Request
REST API - Reply to Comment Request
REST API - Update User Request
REST API - Get Collection Request
REST API - Delete Artifact Request
REST API - List Collections Request
REST API - Authenticate Request
REST API - Get Artifact Type Request
REST API - List Artifact Types Request
REST API - Delete Reply Request
REST API - Get Root Artifacts of Project Request
REST API - Add Attachment Request
REST API - Create User Request
REST API - List Reviews Request
REST API - List Groups Request
REST API - Get User Request
REST API - Delete Traces Request
REST API - Add Artifact Request
REST API - List Users Request
REST API - Get Artifact Image Request
REST API - Update Artifacts Request
REST API - List Unpublished Artifacts Request
REST API HTTP Methods
REST API - HTTP HEAD Method
REST API - HTTP DELETE Method
REST API - HTTP GET Method
REST API - HTTP POST Method
REST API HTTP Status Codes
REST API - HTTP PATCH Method
Blueprint REST API
REST API Quick Start Example
REST API Requests and Responses
REST API Security and Authentication
REST API Known Issues & Constraints
REST API Requests
REST API Resources
REST API - Defining an ALM Job in the Request Body
Dashboards & Reports
Statistics Report Options
Using Scope and View
Statistics Dashboard
Statistics Reports
Applications Dashboard
Applications Report
Estimator Dashboard
Estimator Reports
How to Change the Main Process Label for Estimations
Bulk Reporting
Call Trees
Blueprint + PowerBI Dashboards
How to Create Microsoft Power Automate RPA Migration Estimates with Blueprint
Licensing
Settings & Administration
Overview of Blueprint Settings
System Reports
System Reports
License and Activity Reporting
User List
Project Activity
User Roles
Artifact Map
Project Usage
User Activity Report
Audit Log
System Logs
User Management
Creating and Managing Users
Creating and Managing Groups
Creating and Managing Instance Administrator Roles
Creating and Managing Project Administrator Roles
RPA Management
Microsoft 365 Authentication Settings
Integration Reporting
Migrate - Import/Export
Migrate - Dashboards
Migrate Settings
Advanced Settings
Projects
Installation
Blueprint Installation Guide
System Requirements
Supported Third-Party Components
Azure App Registration (Power Automate Export)
Release Notes
Table of Contents
- All Categories
- Settings & Administration
- RPA Management
- Migrate Settings
Migrate Settings
In Settings under RPA Management, you’ll find the RPA Settings section. Here, users can access various miscellaneous settings to fine-tune parameters related to RPA Migration.
Additional settings within RPA Management -> Migrate can be found to allow fine-tuning of parameters related to RPA Migrations.
Settings
Enable Rules
Blueprint Rules enables users to extend Blueprint's core migration tool to meet their specific needs to create custom mapping rules as needed.
To read more about rules, see Introduction to Rules
Migrate Passwords
By default, Blueprint does not allow for the import and migration of passwords for security reasons. However, Blueprint allows Instance Administrators to enable this setting as needed.
Behavior
- (Default) If disabled: Passwords will not be imported, stored, or migrated
- If enabled: Blueprint will import, securely store, and migrate passwords to the destination tool
Bulk Reimport/Recalculate
For information about this feature, see Bulk Reimport/Recalculate.
Enable Milestone Comments (A360 - PAD only)
If this feature is enabled, a comment will be added in PAD after every 15 lines of A360 code migrated. This makes it easier to track what A360 actions became once converted to PAD.
Export Wizard Options
Call or Embed Settings (Power Automate Desktop)
Users can also choose in the Call or Embed Settings dropdown between System Recommended or Call Everything.
- (Default) System Recommended will determine whether to call or embed each sub-process depending on a variety of factors.
- Call Everything should be used if all sub-processes should be called, regardless of usage or size.
If files have a sub-processes included in the export job, Blueprint can identify the hierarchy and allow users to have those sub-processes remain as separate processes that are called, or can allow the user to embed those sub-processes into the parent process.
Embedding sub-processes comes with the benefit of making the resulting process more readable. However, not all processes can be embedded. By default, a sub-process must be less than 50 steps and a parent process must end up with less than 500 steps. This can be changed by adjusting the Sub Process Embed Limit and the Parent Embed Limit respectively.
Enable Variable Prefix
When a sub-process is migrated to Power Automate Desktop (PAD), Blueprint allows Instance Administrators the option to remove variable prefixes to avoid variable collisions. PAD treats all variables as global variables.
Enable Variable Prefix is on by default. Blueprint enables variable prefixes to ensure that variables aren't overwriting values outside of their scope. However, Instance Administrators can disable this setting by unchecking Enable Variable Prefix checkbox.
These prefixes are created by taking the first letters of the subflow name.
If users are confident that the processes won't contain variable naming conventions that might cause collisions, turning this option off could increase readability and lessen future maintenance effort.
Migration Preferences
System administrators may now control which Blueprint items are added with the Migrated Code to Power Automate. By default, the below settings are enabled. Disabling the items will stop the additional text from being added to the Power Automate flows during the "Export to PAD" process.
The following options have been added in settings for optional migration settings:
Enable Original Comments | When disabled, original developer comments from UiPath are not exported to PAD |
Enable Blueprint Comments | When disabled, Blueprint-inserted comments (TODO, INFO, SRC, etc.) are not exported to PAD |
Enable Regions | When disabled, Blueprint-inserted Regions are not exported to PAD |
Enable Retries | When disabled, action retry logic is not exported to PAD |
Enable Error Handling | When disabled, error handling (ON ERROR) logic is not exported to PAD |
Enable Logs | When disabled, the Logging action is not exported to PAD |
Enable Dynamic Value Handling | When disabled, will use native PAD actions and remove .NET script when converting Dynamic Values |
Enable Native SAP Actions | When disabled, will use use PAD UI actions when interacting with SAP instead of PAD's native SAP actions |
How did we do?
Migrate - Dashboards