Introduction to Rules

Updated by Sean Ellner

Blueprint Rules enables users to extend Blueprint's core migration tool to meet their specific needs to create custom mapping rules as needed. The main use cases for using Rules are:

Use Case

Examples

  1. Unresolved References
  • Missing bot files or dependencies
  • Variable/Expression references to bot files or dependencies
  1. DLL / Method Invocations
  • Custom classes from DLL assemblies
  • Static methods on target objects or types
  1. Code Replace, TODO, Error, and Default Settings
  • Apply common repairs to TODOs/Errors across entire estate
  • Replace code with different code
  1. Custom Actions/Libraries & Unsupported Actions
  • Add support for 3rd party and custom actions/libraries
  1. Map to Existing Migration
  • Adapt Blueprint migration to situations where some manual migration is also occurring
  1. Variable Initialization / Transformation
  • Variable manipulation during export
  • Environment variable initialization
  1. Work Queues
  • Process work queue items
  1. Reuse
  • Detect identical processes and reference one copy to simplify code duplication and dependencies

Platform Specific Rules

The following can be configured with custom Rules for each of the source RPA tools as shown:

AA v10/11
MetaBots and TaskBots that are called repeatedly
A360
TaskBots, Custom Packages, and Unmapped Actions
Blue Prism
Processes, VBOs, Unmapped Actions, Environment Variables, Work Queues
UiPath
XAMLs, Custom Activities, Project Libraries, Work Queues, Method Invocation

Rules Tips

User Permissions
If a mapping exists on Flows or processes out of your permission scope, neither will not be considered during your export.
RPA Dashboard Scope When Exporting
Only processes within your selected scope in RPA Dashboards will be considered when looking for rules opportunities or when exporting.
Limit on RPA Dashboard Scope When Exporting
There is a hard limit of 2,000 processes when exporting to PAD. If a user needs to export more than 2,000 processes, exporting will have to be performed in batches.

Next: Using Rules

How did we do?