RPA Export Wizard

When migrating an RPA process from one tool to another, a wizard will appear upon export with a variety of options the user can select to modify how they want their output to look.

For a walkthrough on how to export using Blueprint, please refer to: RPA Export from Blueprint

After following the steps to export a process, a wizard will pop up looking similar to the below:

Export Options

Call or Embed

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. Blueprint preselects what we recommended for each sub-process based on a variety of factors.

Embedding sub-processes comes with the benefit of making the resulting process more readable. For Example, let's say we are migrating from Blue Prism to Power Automate. Blue Prism uses Objects, that are often only a few actions that are meant to be reused in various processes. Instead of migrating a process with dozens of calls to sub-processes with only a handful of actions within each, we can merge those all into the parent process for easier readability.

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 in the Admin Portal > Instance Settings > Call or Embed.

Variable Prefix

In order to avoid variable collision, whenever a sub-process is migrated to Power Automate Desktop, the user will have the option to remove variable prefixes. This is because all variables in Power Automate Desktop are treated as global variables. To ensure that variables aren't overwriting values outside of their scope, we enable variable prefixes by default.

These prefixes are created by taking the first letters of each of the first 3 words of the sub-process name.

If users are confident that their processes won't contain variable naming conventions that might cause collisions, toggling this option off might increase readability and lessen maintenance work in the future.