Map Custom Actions

11 min

This article applies to:

Unmapped actions (missing activities), 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.

Ensure that the correct Scope and source RPA tool is selected and that Rules have been generated. For more information, see Using Rules.

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 times this custom action is used. Click the number to see a list. You can sort the table by this column, for example to bring the most-used actions to the top.
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 Note - If SUB_FLOW rules are set to Instance level, all projects must have the target subflow present for the Estimator Dashboard to work. Exports will still work, but the missing subflow will result in a TODO.
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 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
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 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

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 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 for instructions.

Map to a script. Refer to Map to a Script for instructions.

Map to a subflow. Refer to Map to a Subflow 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 for instructions.

Map to a script. Refer to Map to a Script for instructions.

Map to a subflow. Refer to Map to a Subflow 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 for instructions.

Map to a script. Refer to Map to a Script for instructions.

Map to a subflow. Refer to Map to a Subflow 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.