Common Procedures
How to Download Rules CSV
- Navigate to the Tools -> Rules
- Select the Scope that contains the processes that should be mapped
- Click the Advanced dropdown on the right side and select Export Rules to CSV to export a prepopulated .csv
How to Upload Completed Rules CSV
- Complete the CSV Rules sheet.
- Navigate to Tools -> Rules.
- Click the Advanced dropdown on the right side and select Import Rules From CSV
- Selecting Choose File will bring up the File Explorer to allow users to choose the applicable Rules mapping file.
- User must have the "View/Edit Instance Configuration" privilege to upload a mapping
- Only one mapping is valid at a time, and newly uploaded mappings will overwrite the previous one
- There must not be any blank rows between data in the filled out sheet
- Any new upload will wipe the existing mappings. Ensure to upload your entire mapping sheet each time.
How to Find Target Names and IDs 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.
Rule Types
DLL/Method Invocation
Since DLL or Method invocations have a dependency on DLL file(s) it is necessary to tell Blueprint where these DLLs are so they can be invoked, or if there is another action the user would like to take.
Detailed Article: DLL/Method Invocation Mapping
Custom Activities or Project Library Mapping
It is possible to create a custom mapping from bots in your source RPA platform to your target RPA platform. By providing a few details, you can map a UiPath Custom Activity, or Project Library to an existing bot, an auto-generated bot, or to an inline script.
Detailed Article: Custom Activity or Project Library Mapping
Mapping Unsupported Activities
On occasion an activity may not be supported by the target RPA platform. Before these scenarios would generate TODOs, but now we can map them.
Detailed Article: Unmapped Activity Mapping
Reuse Mapping
RPA Export can detect duplicate bots and gives the opportunity to export one instance of duplicates instead of a copy of every instance. This works for UiPath XAMLs, Blue Prism Processes and VBOs, and AA v10/11/360 Taskbots.
Detailed Article: Reuse Mapping
Manual Reuse Mapping
There may be times when a user wants to explicitly define a process or sub-process as its own standalone
Detailed Article: Manual Reuse Mapping
Script Mapping
There are some situations where a user may want to map a custom activity or DLL/method invocation to a code block within PAD. For example, it may not be feasible to recompile a UiPath custom activity and a substitute must be used.
Detailed Article: Script Mapping
TODO, Error, and Robin Mapping
If a user finds that they have a common TODO or Error across many exported bots, they can configure a global fix during export to avoid having to repair bots one by one. Also, if a user isn't happy with particular output from Blueprint, they can override the exports behavior.
Detailed Article: TODO, Error, and Robin Mapping
Variable Name Dependency Mapping
Certain RPA platforms allow for variables or expressions when invoking dependencies. Power Desktop Automate for example, does not allow for sub-flow or external flow invocations to use variables. This mapping activity closes the gap.
Detailed Article: Variable Name Dependency Mapping
Metabot Mappings
For Automation Anywhere v11 to Power Automate Desktop, users can map their metabots to all exported processes that reference them.
Detailed Article: Framework Mapping - AA Metabots
Metabot Migration - Best Practices
Variable Renaming and Initialization
Some organizations might want to rename variables in bulk for all processes upon migration, or create new variables entirely.
Detailed Article: Variable Renaming and Initialization
Define Environment Variables
Some organizations might want to rename variables in bulk for all processes upon migration, or create new variables entirely.
Detailed Article: Variable Renaming and Initialization