Migrate Settings

Updated by Sean Ellner

Additional settings within RPA Management -> Migrate can be found to allow fine-tuning of parameters related to RPA Migrations.

Settings

Migrate Disabled Code

By default, Blueprint does not migrate disabled RPA code. However, Blueprint allows Instance Administrators to enable this setting as needed.

Behavior
  • (Default) If disabled: Disabled code will not migrate
  • If enabled: Disabled RPA code will migrate to PAD as TODO comments

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.

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.

Example: Alice is migrating from Blue Prism to Power Automate Desktop (PAD). Blue Prism uses Objects that are often only a few commands 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 commands within each, Blueprint can merge those all into the parent process for easier readability.

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.

Example: Subflow "Process Invoices" has a variable called "Config". If Variable Prefixes are toggled ON, in the subflow "Process Invoices" the variable will be renamed to "PI_Config"

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.

How did we do?