Using the Rules Table
Using the Rules Table. Selecting Tools -> Rules displays the Rules Table. It is very important to ensure you're looking at the right set of rules for the automations you are analyzing. This requires…
Using the Rules Table
Selecting Tools -> Rules displays the Rules Table. It is very important to ensure you're looking at the right set of rules for the automations you are analyzing. This requires two selections:
- Set the Scope: Click the Change Scope button at top-right of the Rules Table page, then choose your desired project. The currently-selected scope is always shown at top-left (see picture below).
- Choose RPA Tool: Rules are listed by RPA tool to ensure you select your desired RPA tool in the drop-down at center, above the table (see picture below).

Once you have chosen your Scope and the right RPA Tool, the rules are listed in the table separated into a tab for each Rule Type.
Columns in the Rule Type Tabs
The tables below give high-level information for each of the columns found within the various Rule Type tabs. More detailed information for each is found in the subsequent articles that describe specific rules.
Note in the tables below U=UiPath, B=Blue Prism, and A=A360.
Common Columns
Column | Description | Custom Actions | Reuse | Unresolved References | Work Queues | Environment Variables | Initialize Variables | Code Replace |
Enabled | Whether the rule is enabled or disabled for export | U B A | U B A | U B A | U B | B | A | U B A |
Occurrences | Number of times the rule appears in source code. Click to see list of occurrences | U B A | U B A | U B A | U B | B | A | |
Scope | Whether this rule applies to current project, or to all projects (instance) | U B A | U B A | U B A | U B | B | A | U B A |
Type | Type of action that was not mapped. Can be DLL for any RPA tool. Unmapped Action for Blue Prism or A360, and Custom Action for UiPath. | UBA | ||||||
Parameters | List of parameters for the action. Need to specify whether input or output | U B A | U B A | U B A |
Source Columns
Column | Description | Custom Actions | Reuse | Unresolved References | Work Queues | Environment Variables | Initialize Variables | Code Replace |
Source: Package Name | Name of the package in the source RPA tool. | U B A | ||||||
Source: Action Name | Name of the action or activity in the source RPA tool. | U B A | U B A | |||||
Source: ID | Source tool's process GUID or Blueprint checksum of process | U B A | U B A | |||||
Source: Filename | Name of xaml, page, or taskbot | U B A | ||||||
Source: Action Name | Name of the action from the source RPA tool. | |||||||
Source: Work Queue Name | Name of the queue from the source RPA tool. | U B |
Target Columns
Column | Description | Custom Actions | Reuse | Unresolved References | Work Queues | Environment Variables | Initialize Variables | Code Replace |
Target: Type | Solution in PAD | U B A | U B A | |||||
Target: ID | GUID of the solution in PAD (if flow chosen as type) | U B A | U B A | U B A | ||||
Target: Name | Name of the solution in PAD | U B A | U B A | U B A | ||||
Target: Script | Script to be used (if script chosen as type) | U B A | U B A | |||||
Target: Work Queue ID | GUID of queue in PAD | U B | ||||||
Target: Work Queue Name | Name of queue in PAD | U B | ||||||
Target: Work Queue Configuration | Set rules for queue key and priority | U B |
Other Columns
Column | Description | Custom Actions | Reuse | Unresolved References | Work Queues | Environment Variables | Initialize Variables | Code Replace |
Variable Name | B | A | ||||||
Variable Value | B | |||||||
Variable Type | A | |||||||
Initial Value | A | |||||||
Original Robin Code (single action) | U B A | |||||||
Replacement Robin Code (one or many actions) | U B A |
How to Find Target Names and GUIDs in PAD
To complete a manual mapping users must fill in the following columns in their Rules CSV:
- Column K ("TargetActionId") = PAD Flow ID
- How to get the FlowID in Power Automate Desktop:
- Find your target flow under the "My Flows" tab in Power Automate Desktop
- Right-click on your target flow and click "Properties"
- Click "Details" tab
- Copy the GUID under "Flow ID". The ID will in the following format: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX where X is a hex digit (0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F)
- How to get the FlowID in Power Automate Desktop:
- Column L ("TargetActionName") = The name of Flow in PAD
- For every Input variable for the flow, perform the following as a separate row for each Input/Output:
- Column P ("TargetParameterName") = PAD Variable Name
- This is the value in "Variable Name" in the Input/Output section of the PAD Flow:
- Column R ("TargetParameterType") = PAD Variable Type (e.g. INPUT/OUTPUT)
- Column P ("TargetParameterName") = PAD Variable Name
It is not what should be used in the mapping file and is only for visual purposes within Power Automate.
How did we do?
Rules User Interfaces
Using Rules CSV