Skip to main content

Using Rules

Process for Using Rules. There are three high-level steps for using rules. These are (1) Generating Rule Opportunities, (2) Analyzing Rules, (3) Configuring Rules. These are described below: Step1: Gā€¦

Tony Higgins
Updated by Tony Higgins

Process for Using Rules

There are three high-level steps for using rules. These are (1) Generating Rule Opportunities, (2) Analyzing Rules, (3) Configuring Rules. These are described below:

  1. Step1: Generate Rule Opportunities. You can generate rules for individual folders, entire projects, or multiple projects (bulk). Rules generation parses the imported RPA code and lists opportunities for each of the rules catagories. For example this might include all the custom actions that Blueprint detects being used, or all the unresolved references found during generation. Even if you don't choose to configure any of these rules, these lists of opportunities are useful when planning and estimating a migration project. You're able to generate rules when using the Rules Table and/or when using the Rules Wizard (see descriptions below).
  2. Step2: Analyze Rules. Generated Rule Opportunities are disabled by default. You need to analyze and decide which ones - if any - you'd like to configure and enable for use during export. Rule Opportunities with a high number of occurrences are the ones you'd consider using because the effort to configure the rule would be less than the alternative - fixing each occurrence by hand in PAD. For example, assume there is a rule opportunity for a custom action and Blueprint reports that this custom action is used 1,000 times. If you don't have a rule for this custom action, then 1,000 "TODO" comments will appear in your PAD flow, each of which you'll need to fix. By configuring the rule and then using during export, all 1,000 will be fixed automatically. Conversely if a custom action is used once, then it would be less effort just to fix that single occurrence in the PAD flow instead of taking the time to configure a rule. You're able to analyze rules using the Rules Table (see description below).
  3. Step3: Configure Rules. When you decide, after analyzing, that you'd like to use a rule for conversion you need to configure it, and enable it. Each type of rule does different things and has specific information it needs to work properly. This is described in the table below.

User Interfaces in the Process

As described in the Introduction to Rules article the three Rules User Interfaces offer different capabilities. The table below summarizes what is possible for each step in each of the User Interfaces.

User Interface

Step: Generate Rules

Step: Analyze Rules

Step: Configure Rules

Rules Table

All aspects of rule generation can be performed from the Rules Table. This includes generating rules for any folder within a project, for an entire project, or for multiple projects (bulk).

Details on frequency of rule occurrence and specific processes and steps of the occurrences are available in the Rules Table.

The majority of Rules Configurations can be performed in the Rules Table.

Rules CSV

NA

NA

Any possible Rules Configuration can be performed using the Rules CSV.

Rules Wizard

Rule generation for the entire project is the only option in the Wizard. When initiating the Rules Wizard if the project has changed since rules were last generated Blueprint will ask if you'd like to re-generate the rules for the project.

NA

Rules configuration for only three types of Rules can be performed (Reuse, Unresolved References, Queues). Guidance is provided to help configure, and live-pickers are provided to choose flows, subflows, and queues.

Rule Types

Different rule types are used to resolve the various cases where Blueprint is unable to convert. These are summarized in the table below.

For each it is also indicated whether Blueprint is able to automatically find and list rules within the source RPA code for each rule type and RPA tool ("Auto-generated").

Rule Type

Resolve from UiPath

Resolve from Blue Prism

Resolve from A360

Custom Actions

  • 3rd Party and Custom Actions
  • Unmapped Actions
  • Project Libraries
  • Custom classes from DLL assemblies
  • Static methods on target objects or types

Auto-generated: YES

  • Missing VBO action references
  • Custom classes from DLL assemblies
  • Static methods on target objects or types

Auto-generated: YES

  • 3rd Party and Custom Actions
  • Unmapped Actions
  • Custom classes from DLL assemblies
  • Static methods on target objects or types

Auto-generated: YES

Reuse

  • Duplicate xamls

Auto-generated: YES

  • Duplicate pages

Auto-generated: YES

  • Duplicate taskbots

Auto-generated: YES

Unresolved References

  • Missing bot files or dependencies
  • Variable/Expression references to bot files or dependencies

Auto-generated: YES

  • Missing Page references

Auto-generated: YES

  • Missing bot files or dependencies
  • Variable/Expression references to bot files or dependencies

Auto-generated: YES

Work Queues

  • Queue references

Auto-generated: YES

Queue references

Auto-generated: YES

NA

Environment Variables

NA

  • Define Flow Variable for Environment Variable and initialize it

Auto-generated: YES

NA

Initialize Variables

NA

NA

  • Initialize variables and assign values to variables before your main bot executes

Auto-generated: NO

Code Replace

  • Apply common repairs to TODOs/Errors across entire estate
  • Replace code with different code

Auto-generated: NO

  • Apply common repairs to TODOs/Errors across entire estate
  • Replace code with different code

Auto-generated: NO

  • Apply common repairs to TODOs/Errors across entire estate
  • Replace code with different code

Auto-generated: NO

How did we do?

Rule Pre-Requisites

Rules User Interfaces

Contact