FAQ
Post-Migration to Power Automate Desktop (PAD)
To learn more about Migration Output in PAD, please see Working with Migration Output in Power Automate Desktop (PAD).
What will my migrated code look like?
Bots will not be fully migrated due to disparate feature function between the source and target RPA tools. Code complete work will be required to get the bot 'production ready'.
1 line of code in the source tool may migrate as several lines in PAD. This is expected, as source and target RPA tools support different feature/functionalities and the core code is different between the source and target RPA tools.
Blueprint prioritizes equivalent functionality first and foremost; the second priority is clarity.
1 line of code in the source tool may migrate as several lines in PAD. This is expected, as source and target RPA tools support different feature/functionalities and the core code is different between the source and target RPA tools.
Blueprint prioritizes equivalent functionality first and foremost; the second priority is clarity.
Why does it look like Blueprint generates so many variables?
PAD does not support variable scoping. In order to simulate scope to avoid collisions and overriding variables we add prefixes for each subflow.
If you're not concerned with accidentally overriding values, Variable Prefixing can be toggled off in the Export Wizard.
If you're not concerned with accidentally overriding values, Variable Prefixing can be toggled off in the Export Wizard.
It doesn't seem like some variable datatype are migrated over?
PAD variables are given types at runtime and PAD supports a limited amount of variable datatypes, which means things may be modified to maintain functionality.
Why does it look like Blueprint is adding extra code?
Blueprint Migrate adds code, but it does so to maintain similar functionality to the original bot between the source and target RPA tools. Sometimes, one action in UiPath needs to migrate as many actions in PAD in order to function similarly.
If there is no combination of standard PAD actions to support the actions in the source bot OR if the migration result would have been too verbose or complicated, Blueprint may use a .NET script instead.
Blueprint also adds optional code like TODO comments, Regions, Logging, etc. If your organization doesn’t need certain optional code types, you can toggle them off in Migration Preferences.
If there is no combination of standard PAD actions to support the actions in the source bot OR if the migration result would have been too verbose or complicated, Blueprint may use a .NET script instead.
Blueprint also adds optional code like TODO comments, Regions, Logging, etc. If your organization doesn’t need certain optional code types, you can toggle them off in Migration Preferences.
Why is Blueprint making duplicate subflows?
The logic is the same, but the parameters we are passing are different because PAD doesn’t support variable scoping.
Why does it seem like some processes/sub-processes are missing?
Users can easily check the selected processes/sub-processes for export in the Export Wizard.
If something seems to be missing, look within the Blueprint folder for your import and open the RPAImportLog file. If any processes failed to import, they will be listed at the top. If there are no failures to report, search the applicable PAD flow for "INFO: SubFlow <subflowName> was inlined". Blueprint by default will inline subflows if they are a) only called once or b) is short.
This behavior is configurable. To change this behavior, go to Export Wizard Options and change Call or Embed Settings from System Recommended to Call Everything.
If something seems to be missing, look within the Blueprint folder for your import and open the RPAImportLog file. If any processes failed to import, they will be listed at the top. If there are no failures to report, search the applicable PAD flow for "INFO: SubFlow <subflowName> was inlined". Blueprint by default will inline subflows if they are a) only called once or b) is short.
This behavior is configurable. To change this behavior, go to Export Wizard Options and change Call or Embed Settings from System Recommended to Call Everything.
Do TODOs and Compiler Errors represent all the remaining work required to get a migrated bot production ready?
No. While TODOs and Compiler Errors make up the bulk of the work, selectors will need to be reviewed and tested as well. Blueprint cannot test the efficacy of the selectors when migrating to PAD because we likely will not have access to your applications.
If you notice an issue with selectors in your migrated bots, please reach out to our Blueprint Support team or your Customer Success Manager.
If you notice an issue with selectors in your migrated bots, please reach out to our Blueprint Support team or your Customer Success Manager.
What about my custom actions/libraries?
Blueprint can only migrate standard actions; however, Blueprint can still help with custom actions and libraries via Rules.
Licensing
What Blueprint licensing model is my site using?
See Licensing in Blueprint to learn how to determine your licensing model.
What consumes a license in Blueprint?
Blueprint charges a license based on Mains. Mains are defined differently across each source RPA platform:
Blue Prism
- Each Blue Prism process contains one Main page that serves as the root
- These Main pages are fixed and cannot be renamed or modified
- The total number of Main pages determines the Main count in Blueprint, therefore each Main page will be considered 1 license in Blueprint.
UiPath
- Each UiPath projet includes a Main.xaml file
- While this file can be renamed, it remains flagged as the Main in the UiPath codebase
- Blueprint's Main count matches the number of flagged UiPath Mains
Automation360
- Unlike other platforms, A360 does not have defined Mains in its architecture
- For A360 migrations, Blueprint counts root Task Bots as Mains
For added details, visit Licensing in Blueprint.
Blue Prism
- Each Blue Prism process contains one Main page that serves as the root
- These Main pages are fixed and cannot be renamed or modified
- The total number of Main pages determines the Main count in Blueprint, therefore each Main page will be considered 1 license in Blueprint.
UiPath
- Each UiPath projet includes a Main.xaml file
- While this file can be renamed, it remains flagged as the Main in the UiPath codebase
- Blueprint's Main count matches the number of flagged UiPath Mains
Automation360
- Unlike other platforms, A360 does not have defined Mains in its architecture
- For A360 migrations, Blueprint counts root Task Bots as Mains
For added details, visit Licensing in Blueprint.
How many Bot activation licenses have I used / do I have left?
See Licensing and Activity Reporting to learn how to identify used and remaining license counts.
Will a bot license be used if I activate a process multiple times?
No. Blueprint detects if an identical component has been imported before. It will be flagged as a 'duplicate', separated out on Dashboards and Reports, and will not consume additional bot activation licenses.
Do "hidden steps" consume Blueprint licenses?
No. Some RPA tools allow users to disable or hide code steps. Since Blueprint doesn't migrate these, they do not consume licenses.
What causes a "Licenses Running Low" warning to be displayed?
When a user attempts to Activate processes and the number of remaining licenses is low (e.g. approximately 80% consumed), Blueprint will display a warning message to ensure license consumption status transparency and to prompt users that additional licenses may need to be procured to continue the migration effort.
What causes an "Out of Licenses" error to be displayed?
When a user attempts to Activate processes that require more licenses than are available, the user will receive an error message indicating that there are not enough unused licenses for the requested Activation operation and that the selected processes will not be Activated. Additional licenses must be procured to continue the migration effort.
How can I procure additional licenses?
Please contact your Blueprint Sales Representative, Customer Success Manager, or Blueprint Support.
How To's
How do I activate and export a Bot?
Please see RPA Export from Blueprint.
How do I reset my password?
Please see Change Your Password.
How do I create a new project in Blueprint?
Please see Create a New Project.
How do I export a Blueprint report?
Please see How to Export Reports.
Dashboards & Reports
How large are my automations?
You can see the overall number of processes and overall number of actions for your entire estate at a glance, as well as the average number of actions per process, and the largest process in terms of number of actions. All of this is available at the top-right of the Statistics Dashboard.
You can also see the Number of Actions within each individual process, and how many of those Actions are Commands and how many are Variables. All of these aspects can be sorted to easily find processes with the most actions, commands, or variables for example. This information is found in Statistics Reports at the bottom of the Statistics Dashboard.
You can also see the Number of Actions within each individual process, and how many of those Actions are Commands and how many are Variables. All of these aspects can be sorted to easily find processes with the most actions, commands, or variables for example. This information is found in Statistics Reports at the bottom of the Statistics Dashboard.
How complex are my automations?
Blueprint calculates the complexity of each individual process to get a complexity score, then categorizes as High, Moderate, or Low. This information is available for each process in the Statistics Reports, and graphically in a histogram of all processes at top-left of the Statistics Dashboard.
How can I see the worst case automations for size and complexity?
A graphic of size vs. complexity is provided at the top-center of the Statistics Dashboard with a dot representing each process in the selected scope. Hovering over any dot gives the name of the process. The entire graph can be expanded to provide greater precision simply by clicking on it.
Where can I find information on how my automation is constructed?
Information for each process including commands, variables, complexity, decisions, includes, applications, and total actions is in the Statistics Reports at the bottom of the Statistics Dashboard. You can search to find any of your processes within the selected scope, and can sort any of the detailed information columns.
Where can I find more details on how my automation is constructed?
All of the commands that comprise each process is available in an exported report. To get the report, select "Export All Commands to Excel" in the Actions dropdown for the Statistics Report at the bottom of the Statistics Dashboard.
What are all the processes that comprise my automation?
Automations are typically comprised of a main process that calls other processes, that in turn call others, to form a tree-like structure. You can generate that call tree for a selected scope by clicking the "Download Call Tree" button in the Statistics Dashboard. To learn more about Call Trees, see Call Trees.
The resulting file is in SVG format that can be opened in any internet browser. Since the contents can be very large, this format allows it to be zoomed to any extent and still be readable. It is also searchable using the browser's search (CTL-F), an example shown in the diagram here.
The resulting file is in SVG format that can be opened in any internet browser. Since the contents can be very large, this format allows it to be zoomed to any extent and still be readable. It is also searchable using the browser's search (CTL-F), an example shown in the diagram here.
What applications are my processes using?
Automations interact with applications and its often required to know how many applications, which applications, and how often these interactions occur. Information about process and application interaction can be found in the Applications Dashboard and Applications Report.
On the left side of this dashboard is summary information about how often particular applications are referenced.
On the right side is the ability to select an application and see the specific processes that reference it, or the opposite: select a process and the applications it references. See more information here.
On the left side of this dashboard is summary information about how often particular applications are referenced.
On the right side is the ability to select an application and see the specific processes that reference it, or the opposite: select a process and the applications it references. See more information here.
Is anything called that wasn't included in the import?
It's important to know if you have the required components when analyzing an estate for migration, or if anything is missing. Blueprint provides a Missing Processes report that lists any components being called that don't currently exist in Blueprint.
Which components are currently being reused in my estate?
Components being called more multiple times are being "reused". Reuse is beneficial in a numerous ways and should be encouraged. The alternative of having multiple copies of the same or highly-similar code can be very detrimental.
Blueprint provides a Reuse Report to show how many times components are being called in the estate.
Blueprint provides a Reuse Report to show how many times components are being called in the estate.