--- title: Advanced Mappings slug: blueprint/advanced-mappings docTags: yO7XZ9PJxDCKZ-Mf4TSYB,HK_rxWrGo8iZHH4PvnxmZ createdAt: 2026-06-05T17:12:49.929Z --- :::CtaButton{label="🟢 Migrator" openInNewTab="false"} ::: This section is devoted to using the Rules CSV spreadsheet. Some of the items in this section can also be performed using the Rules Table in the user interface or the Rules Wizard, while other items can only be done using the CSV spreadsheet. See section [Using Rules CSV](docId:6pzVPHZ5f48VHRu3u7ua-) for how to import/export the spreadsheet. The rest of this article will cover how to configure the spreadsheet to perform specific mappings. *** # Variable Enumerations For variables that take values from an enumerated list, you can define how each valid value in the source RPA tool will convert to a value in the target RPA tool. You do this by providing the list of valid values for the source RPA tool, and the corresponding list of valid values for the target RPA tool (PAD). The conversion will be based on position in the list (e.g. value in 4th position in source list will convert to value in 4th postion in target list). Note that the lists must be of equal length. Fill in the following columns: - Column Q ("**SourceParameterValue**") = This column should be a list delimited by **\&#&** which contains an exhaustive list of possible values for this parameter. Eg: *START\&#\&STOP\&#\&INFO\&#\&WARN* - Column U ("**TargetParameterValue**") = A list of same length as Column Q delimited by **\&#&** which is a list of actions to map to. Eg. *Logger.START\&#\&Logger.STOP\&#\&Logger.INFO\&#\&Logger.WARN* 1. Import Rules CSV To import rules, from the Rules dashboard, click **Advanced** -> **Import Rules From CSV** *** # Queue Mappings 1. **Import CSV** To map the Work Queues, the user needs to configure the rules and then import the CSV. Fill in the following columns: - Column ("**IsActive**") = **1 (TRUE)** - Column ("**ScopeId**") = Blueprint Scope or Project Id where the bot is imported - Column ("**SourceObjectName**") = Name of the Queue in the Source tool - Column ("**SourceActionType**") = **WORK\_QUEUE** - Column ("**TargetObjectId**") = Work Queue Id from Work Queue created through PAD - Column ("**TargetObjectName**") = Work Queue Name from Work Queue created through PAD - Column ("**TargetActionType**") = **WORK\_QUEUE** - Column (**"DefaultValue")** = Used for defining Rules for Priority Property CSV file format is also accepted to edit rules. - To import rules, from the Rules dashboard, click **Advanced** -> **Import Rules From CSV** *** # Custom Actions - Mapping different library versions In some scenarios, project libraries are regularly updated and use version ranges. For example, a project may reference BPMathProjectLibrary v1.0.9 while the latest version is 1.0.10. Rules however, uses strict version mapping when looking for project libraries. Therefore, in scenarios where there are ranges, in addition to mapping namespace and action, the user needs to also map the versions. To do so The following columns will be already filled in by Rules generation - Column A ("**ScopeId**") = Scope for Rule. Blank implies Instance level - Column B ("**SourceActionType**") = **CUSTOM\_ACTION** - Column C ("**TargetActionType**") = **EXTERNAL\_FLOW** or **SUB\_FLOW** - Column E ("**SourceObjectName**")  = Project Library Namespace - Column G ("**SourceActionName**")= Project Library Method Name - Column N ("**SourceParameterName**") = Name of Parameter - Column R ("**TargetParameterName**") = Same as *SourceParameterName* - Column Y ("**IsActive**") = **FALSE** The following needs to be completed by the user - Column O ("**SourceParameterType**") = **Input** or **Output** - Column V ("**SourceVersion**") = The version of the project library that is imported in Blueprint - Column W ("**TargetVersion**") = The version of the project library that is referenced in the calling UiPath project - Column Y ("**IsActive**") = **TRUE** *** # Reuse Rule The following columns will be auto-populated: - Column A ("**ScopeId**") = Scope for Rule. Blank implies Instance level - Column B ("**SourceActionType**") = **REUSABLE\_FLOW** - Column C ("**TargetActionType**") = **EXTERNAL\_FLOW** - Column F ("**SourceActionId**")  = Checksum - Column G ("**SourceActionName**")= Method Name - Column Y ("**IsActive**") = **FALSE** If mapping to an existing flow and include the following: - Column K ("**TargetActionId**")= GUID of existing flow. - Column L ("**TargetActionName**") = Name of flow No configuration is necessary for Reuse Rules. Blueprint will auto generate all necessary values on the next export. The only column that needs to be modified is column Y ("**IsActive**") needs to be set to **TRUE** *** # Unresolved Reference **Advanced: Use Checksum to Map to Existing Process as External Flow or Subflow** In situations where VBOs were imported into Blueprint in separate imports, VBO's and Processes can be mapped to using Rules. The first step is finding the desired process to map's checksum, this can be found in the description of the artifact in Blueprint ::Image[]{src="https://api.archbee.com/api/optimize/HRPaq4oJ2h9pHAfcjJGa6/YaXvJuW7jrmLYlD8QsRDm_image-1730234838472.png" size="70" width="1072" height="745" darkWidth="1072" darkHeight="745" position="center" showCaption="false"} The following columns will be auto-populated by Blueprint's Rule Generator: - Column A ("**ScopeId**") = Scope for Rule. Blank implies Instance level - Column B ("**SourceActionType**") = **UNMAPPED\_ACTION** - Column C ("**TargetActionType**") = **EXTERNAL\_FLOW of SUB\_FLOW** - Column E ("**SourceObjectName**")  = Unmapped action Namespace - Column G ("**SourceActionName**")= Unmapped action Method Name - Column N ("**SourceParameterName**") = Name of Parameter - Column R ("**TargetParameterName**") = Same as *SourceParameterName* - Column Y ("**IsActive**") = **FALSE** Enter the following information to complete the mapping - Column F ("**SourceActionId**")  = Checksum - Column G ("**SourceActionName**")= Method Name - Column O ("**SourceParameterType**") = Input or Output - Column Y ("**IsActive**") = Set to TRUE to enable Rule *** ## Unmapped Actions The following columns will be auto-populated by Blueprint's Rule Generator: - Column A ("**ScopeId**") = Scope for Rule. Blank implies Instance level - Column B ("**SourceActionType**") = **UNMAPPED\_ACTION** - Column C ("**TargetActionType**") = **EXTERNAL\_FLOW** - Column E ("**SourceObjectName**")  = Unmapped action Namespace - Column G ("**SourceActionName**")= Unmapped action Method Name - Column N ("**SourceParameterName**") = Name of Parameter - Column R ("**TargetParameterName**") = Same as *SourceParameterName* - Column Y ("**IsActive**") = **FALSE** :::hint{type="info"} A row will exist for every parameter. For example, a call to *UnmappedActivity.Add(NumOne, NumTwo*) will create two rows, one for parameter *NumOne*, and another for parameter *NumTwo* ::: ### Scenario 1) Map to New Flow When mapping to a new flow, the only column that needs to be filled in by the user is O ("**SourceParameterType**") which can have one of two values: Input or Output. In some scenarios where a parameter is both an Input and Output, the row needs to be duplicated with one defined as the Input and the other as the Output. Finally, set Column Y ("**IsActive**") to TRUE to enable the Rule ### Scenario 2) Map to Existing Flow To map to an existing flow, the following columns must be defined by the user - Column O ("**SourceParameterType**") = Input or Output - Column K ("**TargetActionId**")= GUID of existing flow. [Finding PAD Flow Target ID and Name](docId\:tycDmAEDb3_KZHtIFh1Jn) - Column L ("**TargetActionName**") = Name of flow - Column R ("**TargetParameterName**") = Typically matches Column N ("**SourceParameterName**") - Column Y ("**IsActive**") = Set to TRUE to enable Rule ### Scenario 3) Map to PAD actions or Scripts - Column A ("**ScopeId**") = Scope for Rule. Blank implies Instance level - Column B ("**SourceActionType**") = **CUSTOM\_ACTION** - Column C ("**TargetActionType**") = **EXTERNAL\_FLOW** - Column E ("**SourceObjectName**")  = Custom Activity Namespace - Column G ("**SourceActionName**")= Custom Activity Method Name - Column N ("**SourceParameterName**") = Name of Parameter - Column R ("**TargetParameterName**") = Same as *SourceParameterName* - Column Y ("**IsActive**") = **FALSE** :::hint{type="info"} A row will exist for every parameter. For example, a call to *CustomActivity.Add(NumOne, NumTwo*) will create two rows, one for parameter *NumOne*, and another for parameter *NumTwo* ::: Update the following columns - Column C ("**TargetActionType**") Set this column to one of: *RUN\_VBSCRIPT, RUN\_JAVASCRIPT, RUN\_POWERSHELLSCRIPT, RUN\_PYTHONSCRIPT, RUN\_CSHARPDOTNETSCRIPT, RUN\_VBDOTNETSCRIPT, RUN\_ROBINSCRIPT* - Column X ("**DefaultValue**") Set this column to your described script. Scripts can be single or multi-line. ::Image[]{src="https://api.archbee.com/api/optimize/HRPaq4oJ2h9pHAfcjJGa6/d-j7edliSk7ghf-H7KF9X_script-mapping-screen-png.PNG" size="70" width="1206" height="96" darkWidth="1206" darkHeight="96" position="center" showCaption="false"} *** # Map DLL Method Calls 1. **Export CSV** To start using the CSV Rules sheet, the user must export the Rules table to CSV. To do so, from the Rules dashboard, click **Advanced** -> **Export Rules to CSV** The following columns will be auto-populated by Blueprint's Rule Generator: - Column A ("**ScopeId**") = Scope for Rule. Blank implies Instance level - Column B ("**SourceActionType**") = **DLL\_CALL** - Column C ("**TargetActionType**") = **EXTERNAL\_FLOW or SUB\_FLOW** - Column E ("**SourceObjectName**")  = DLL Namespace - Column G ("**SourceActionName**")= DLL Method Name - Column N ("**SourceParameterName**") = Name of Parameter - Column O ("**SourceParameterType**") = Type of Parameter. Input or Output - Column P ("**SourceParameterDataType**") = Data Type of Parameter - Column R ("**TargetParameterName**") = Same as *SourceParameterName* - Column S ("**TargetParameterType**") = Type of Parameter. Input or Output - Column T ("**Target\*\*\*\*ParameterDataType**") = Data Type of Parameter - Column Y ("**IsActive**") = **FALSE** *** ### Scenario 1) Map to New Flow When mapping to a new flow, the only column that needs to be filled in by the user is O ("**SourceParameterType**") which can have one of two values: Input or Output. In some scenarios where a parameter is both an Input and Output, the row needs to be duplicated with one defined as the Input and the other as the Output. Finally, set Column Y ("IsActive") to TRUE to enable the Rule ### Scenario 2) Map to Existing Flow To map to an existing flow, the following columns must be defined by the user - Column K ("**TargetActionId**")= GUID of existing flow. See [Finding PAD Flow Target ID and Name](docId\:tycDmAEDb3_KZHtIFh1Jn). - Column L ("**TargetActionName**") = Name of flow - Column R ("**TargetParameterName**") = Typically matches Column N ("**SourceParameterName**") - Column Y ("**IsActive**") = Set to **TRUE** to enable Rule ### Scenario 3) Map to PAD actions or Scripts 1. Import Rules CSV To import rules, from the Rules dashboard, click **Advanced** -> **Import Rules From CSV** 2. [Download the CSV](docId:6pzVPHZ5f48VHRu3u7ua-) from RPA Dashboard The following columns will be auto-populated: :::hint{type="info"} A row will exist for every parameter. For example, a call to *Custom.Activity.Add(NumOne, NumTwo*) will create two rows, one for parameter *NumOne*, and another for parameter *NumTwo* ::: 1. For a successful mapping, the following columns must be filled in: - Column J ("**TargetActionId**")  = GUID of PAD Flow - Column K ("**TargetActionName**")= Name of PAD Flow - Column Q ("**TargetParameterType**")= **INPUT** or **OUTPUT** :::hint{type="info"} The Target Flow does not need to be a complete Flow. It can be a simple stub however, the Flow signature must match what was entered in the Mapping sheet ::: 1. [Import CSV](docId:6pzVPHZ5f48VHRu3u7ua-) using **UiPath** as your **Source** and **PAD** as your **Target** **** **** **** **** **** ****