Advanced Mappings

17 min

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 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

Import Rules CSV To import rules, from the Rules dashboard, click Advanced -> Import Rules From CSV

Queue Mappings

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

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

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

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

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.

Map DLL Method Calls

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

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.

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

Import Rules CSV To import rules, from the Rules dashboard, click Advanced -> Import Rules From CSV

Download the CSV from RPA Dashboard The following columns will be auto-populated:

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

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

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

Import CSV using UiPath as your Source and PAD as your Target