Map Custom Actions

this article applies to invoke method activities and missing custom activities in uipath unmapped actions (missing vbos) and dll calls in blue prism unmapped actions (missing packages) and dll calls in a360 this article will describe details for everything other than dll calls which are addressed in the next article map dll method calls docid 8i8egl6fzb1 31pihxn3z ensure that the correct scope and source rpa tool is selected and that rules have been generated for more information, see using rules docid\ ln7dxyaelvpd89ii09xoz custom actions table explained column description enabled by default rules are disabled when disabled a rule will have no affect on export when enabled, rule will be applied where applicable best practice is to leave a rule disabled until it is fully configured occurrences number of occurrences of this unresolved reference click the number to see a list scope the scope can be either a project or entire blueprint instance when using a project as a scope, the rule will apply to all applicable processes within the project this flexibility allows users to haven different rule sets for different projects type uipath custom action, invoke method blue prism unmapped action, dll call a360 unmapped action, dll call parameters where to map inputs and outputs when clicked a modal will appear with a table to map which parameters are inputs and which are outputs package name also known as namespace, is a container that helps organize activities and avoid naming conflicts it is used to group related classes, interfaces, and objects for method invocations this is the target object action name the name of the specific activity within the namespace for method invocations this is the target method type what type of rule the user wishes to apply external flow, sub flow , run robinscript , run vbscript, run javascript, run powershellscript, run pythonscript, run csharpdotnetscript, run vbdotnetscript each one of these is explained in detail throughout this article id when using external flow, this is the guid of the flow in pad blueprint populates in some cases if you need to manually populate this value, refer to finding pad flow target id and name docid\ tycdmaedb3 kzhtifh1jn when using sub flow, this will be a unique checksum of the subflow that is populated when you choose the subflow using the picker refer to map to a subflow docid\ atrzkxb7fkb7lhmrdrfc6 name when using external flow, this is the name of the external (desktop) flow to map to blueprint populates in some cases if you need to manually populate this value, refer to finding pad flow target id and name docid\ tycdmaedb3 kzhtifh1jn when using sub flow, this will be the name of the subflow that is generated during export script when using any of run \<language>script you will enter your script here refer to map to a script docid aqs es0tizuhibx6x7ux uipath > pad mapping parameters the first step to any rule is mapping the parameters due to technical limitations blueprint is unable to always determine whether a parameter is an input or output and therefore has to be mapped by a user to do so, click on the parameters icon to expose the parameters modal seen below for each parameter indicate which is an input and which is an output when complete click apply to finish in some instances a parameter will be an input and an output in those situations the parameter will be listed twice one instance needs to be set to input and the second to output project libraries project libraries in uipath can be either c# libraries compiled versions of pro code (e g c#) that appear as drag drop activities in uipath studio (compiled libraries) in cases where activities in this library are referenced but the library is missing, these activities will appear in custom activities rules list xaml libraries a collection of xaml files that are invoked using the invoke workflow activity (xaml libraries) in cases where these xamls are referenced but the xaml is missing, these references will appear in the unresolved references rules list refer to map unresolved references docid\ av35upyjefmux238 3bpt for more information on xaml libraries in the case of c# compiled libraries, you'll need to locate the library and determine how to replicate the functionality in pad one approach is to recreate them as pad custom actions, then configure the blueprint rules to map those library's activities another is to rewrite them in one of blueprint's supported scripting languages, one of which is net/c#, and again configure the rule to map it still another is to recreate using pad locode actions in an external flow and configure a rule you can even do some combination, like rewrite in a script that you place in an external flow so that it's reused instead of embedded at each occurrence of the action under the custom actions tab in rule dashboard, custom actions detected as being used in the code will have a package name and action name along with a type for example mapping to a target you can use the rule to convert the action to a "target" solution you do this by using the drop down list to choose a target type and then providing details possibilities include map to a new or existing flow refer to map to an external flow docid\ nu3bqtvwhkapcb7yg ml7 for instructions map to a script refer to map to a script docid aqs es0tizuhibx6x7ux for instructions map to a subflow refer to map to a subflow docid\ atrzkxb7fkb7lhmrdrfc6 for instructions blue prism > pad missing vbos are fairly rare when migrating from blue prism typically bprelease files contain all needed dependencies and most pre packaged vbos are supported however, in the rare occasion that a vbo is missing, used actions from that vbo will appear in the list of of rules under custom actions with type unmapped actions the best way to resolve this is to locate the vbo in blue prism and re import a revised bprelease that contains the vbo otherwise, you can use rules to resolve but you will need to provide the code or scripts yourself since that code is missing from blueprint options include map to a new or existing flow refer to map to an external flow docid\ nu3bqtvwhkapcb7yg ml7 for instructions map to a script refer to map to a script docid aqs es0tizuhibx6x7ux for instructions map to a subflow refer to map to a subflow docid\ atrzkxb7fkb7lhmrdrfc6 for instructions if the vbo is missing and you choose not to resolve with a rule per above, then todo comments will be inserted into the generated pad code wherever those missing vbo actions are used automation anywhere a360 > pad actions in custom packages and unsupported packages from a360 will appear as unmapped actions in the custom actions rules tab the best way to resolve this is to locate the package in a360 and re imported a revised zip that contains the package otherwise, you can use rules to resolve but you will need to provide the code or scripts yourself since that code is missing from blueprint options include map to a new or existing flow refer to map to an external flow docid\ nu3bqtvwhkapcb7yg ml7 for instructions map to a script refer to map to a script docid aqs es0tizuhibx6x7ux for instructions map to a subflow refer to map to a subflow docid\ atrzkxb7fkb7lhmrdrfc6 for instructions if the package is missing and you choose not to resolve with a rule per above, then todo comments will be inserted into the generated pad code wherever those missing actions are used