Unmapped Activities

Updated by Luka Koczorowski

There are some scenarios where Blueprint cannot determine if an action is a custom action, unmapped, or unsopported. In those scenarios we have a Rule call "unmapped actions" which is described below.

Ensure you have the correct scope and source RPA tool selected, and that you have generate Rules. See Using Rules for details instructions

Using Rules Dashboard

Rules dashboard is currently mostly read-only. The only available functionality is to enable rules or bulk delete rules.

Using CSV

  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") = 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
  1. Configure Rules
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. Read How to find Flow GUID
  • 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

Read: Map Custom Actions or DLL calls to Inline Script

  1. Import Rules CSV

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

How did we do?