Advanced Mappings

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 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 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 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 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 import rules csv to import rules, from the rules dashboard, click advanced > import rules from csv download the csv docid 6pzvphz5f48vhru3u7ua 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 docid 6pzvphz5f48vhru3u7ua using uipath as your source and pad as your target