Using Rules
Rules Overview
At a high level, the process is as follows:
- Use Blueprint's Rules Generation for a given scope to get a list of all Rules opportunities
- Use the Rules UI or CSV Mapping sheet and define rules to apply to future exports
- Upload completed CSV sheet or save changes in Rules UI
Accessing Rules
Via Dashboard
The dashboard is the primary way to interact with Rules via the UI. Here you can generate, enable, configure, and delete rules. To access the Rules Dashboard:
- Click on Tools from the main header
- Select Rules
Via CSV
With CSV mappings, users have virtually limitless ability to create and modify rules to their exact needs and specifications. See Using Rules CSV for more detail.
Step 1: Set the Scope
A Rule's "Scope", is the set of processes where the rule will be applied. The scope can be either a project or entire Blueprint instance. When using a project as a scope, the rule will apply to all applicable processes within the project. This flexibility allows users to haven different rule sets for different projects.
When Rules is first launched from the dashboard, users will be asked to set a Scope. After this initial setting, users can change Scope by clicking the Change Scope button in the top right of the page.
The Scope can only be set at the Project level and will display and generate Rules for that Project.
Step 2: Generate Rules
Generating Rules will prepopulate the Rules table with all potential Rules that Blueprint has discovered for the selected Scope. To generate Rules:
- From the Rules dashboard, click the blue report header in the center and choose the appropriate source RPA tool to PAD.
- Click the Advanced button in the top right corner
- Select Generate Rules
When the job completes, users can refresh the page to see generated Blueprint Rules.
Step 3: Configure Rules
Rule Categories
Each Rule category has its own tab in the Rules dashboard. These categories also depend on the source RPA platform where bots were imported from. Here a user can configure each Rule to their specification.
UiPath
Category | Details | Blueprint Rule Auto-Generation |
Custom Actions consist of any 3rd party dependencies, project libraries, custom activities, and Method Invocation. | Yes | |
Any time a XAML file is called more than once, instead of having carbon copies are for each automation, you can create a single copy | Yes | |
Replace TODO messages, Errors, and Robin code with replacement Robin code. | No | |
Whether the dependency is missing, or using a variable expression as the name, Rules can help stitch your dependencies back together | Yes | |
Need to Map Work Queue ID and Name to execute Work Queues | No | |
CSV Only | Unmapped Actions can only be done via CSV file for UiPath | No |
Automation Anywhere v10/11/A360
Category | Details | Blueprint Rule Auto-Generation |
Custom Actions | Custom Actions consist of any 3rd party dependencies, custom packages, and any unmapped actions. See Unmapped Activities to migrate these assets using Rules | Yes |
Any time a task bot or metabot is called more than once, instead of having carbon copies are for each automation, you can create a single copy | Yes | |
Replace TODO messages, Errors, and Robin code with replacement Robin code. | No | |
Whether a task bot is missing or using a variable expression as the name, Rules can help stitch your dependencies back together | Yes | |
Initialize variables and assign values to variables before your main bot executes | No |
Blue Prism
Category | Details | Blueprint Rule Auto-Generation |
Custom Actions | in the rare occasion that a dependency is missing Blueprism users can use Unmapped Activities to map these activities | Yes |
Any time a Process or VBO is called more than once, instead of having carbon copies are for each automation, you can create a single copy | Yes | |
Replace TODO messages, Errors, and Robin code with replacement Robin code. | No | |
Whether the dependency is missing, or using a variable expression as the name, Rules can help stitch your dependencies back together | Yes | |
Initialize variables and assign values to variables before your main bot executes | No | |
Need to Map Work Queue ID and Name to execute Work Queues | No |
Other Mappings
Category | Details | Blueprint Rule Auto-Generation |
When mapping to a custom action, sometimes a specific parameter is used as an action selector. | No |
Step 4: Enable Rules
Once Rules have been configured, the next step is to enable them. Once enabled, for every future export, the Rules will be applied. How Rules apply will depend on their Scope.