Using Rules
Using Rules
Dashboard
The dashboard is the primary way to interact with Rules. Here you can generate, enable, configure, and delete rules. To access the dashboard, from the main Blueprint experience, click on Tools -> Rules from the top menu bar.
CSV
The CSV is for power users of Rules. Users have virtually limitless ability to create and modify rules to their exact specifications. This feature should be reserved for power users.
Step 1: Set Your Scope
When you first launch the Rules dashboard you will be asked to set a scope. After this initial setting, you can change your scope by clicking the Change Scope button. The scope, which can only be a project, will display and generate rules for that project. Rules however, can also be generated at an instance level which is discussed next.
Step 2: Generate Rules
When you're ready to start creating Rules, the next step is using Blueprint's Rule Generation feature. This will prepopulate the Rules table with all potential Rules that Blueprint has discovered on your behalf for the selected scope. You can scope to either a project or your entire Blueprint instance.
From the Rules dashboard, click Advanced -> Generate Rules. Once the job is complete you can refresh the page to see the Rules Blueprint has generated. By default these rules are disabled, once a user is finished configuring a Rule it can be enabled.
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 |
Custom Actions consist of any 3rd party dependencies, project libraries, or custom activities. | |
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 | |
Replace TODO messages, Errors, and Robin code with replacement Robin code. | |
Whether the dependency is missing, or using a variable expression as the name, Rules can help stitch your dependencies back together | |
CSV Only | Unmapped Actions and Method Invocations can only be done via CSV file for UiPath |
Need to Map Work Queue ID and Name to execute Work Queues |
Automation Anywhere v10/11/A360
Category | Details |
Custom Actions consist of any 3rd party dependencies, metabots, and custom packages. These assets can also be imported and linked to using Rules | |
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 | |
Replace TODO messages, Errors, and Robin code with replacement Robin code. | |
Whether the dependency is missing, or using a variable expression as the name, Rules can help stitch your dependencies back together | |
Initialize variables and assign values to variables before your main bot executes | |
CSV Only | Unmapped Actions and DLL invocations can only be done via CSV file for Automation Anywhere |
Blue Prism
Category | Details |
Custom Actions consist of any 3rd party or custom VBOs/Processes. | |
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 | |
Replace TODO messages, Errors, and Robin code with replacement Robin code. | |
Whether the dependency is missing, or using a variable expression as the name, Rules can help stitch your dependencies back together | |
Initialize variables and assign values to variables before your main bot executes | |
CSV Only | Unmapped Actions can only be done via CSV file for Blue Prism |
Need to Map Work Queue ID and Name to execute Work Queues |
Other Mappings
Category | Details |
When mapping to a custom action, sometimes a specific parameter is used as an action selector. |
Step 4: Enable Rules
Once a user has finished configuring their Rules, the next step is to enable them. Once enabled, for every future export, the Rules will be taken into consideration. Which Rules apply will depend on their scope, which can be either instance level or project level.