Variable Name Dependency Mapping

Updated by Luka Koczorowski

Certain RPA platforms allow for variables or expressions when invoking dependencies. Power Desktop Automate for example, does not allow for sub-flow or external flow invocations to use variables. This mapping activity closes the gap.

There are two main branches to go down when working with unresolved dependencies. If the underlining dependency has been imported into Blueprint and only needs to be connected with an export a user can use the checksum of the missing dependency. On the other hand, if the underlining dependency is not available in Blueprint then a user will have to continue without the checksum.

The fundamental difference is that with the checksum Blueprint can successfully resolve the missing reference and export its logic. Without the checksum the best Blueprint can do is put a place holder that would then need to be further developed.

With Checksum

Using Rules Dashboard

It is recommended to use the CSV when working with checksums as a checksum cannot be entered in the dashboard.

Using 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") = VARIABLENAME_FLOW
  • Column C ("TargetActionType") = EXTERNAL_FLOW
  • Column G ("SourceActionName")= [Variable or Expression] or Location
  • Column Y ("IsActive") = FALSE

Map to New Flow

To map to a new flow the following columns need to be filled in:

  • Column F ("SourceActionId") = Checksum of unresolved dependency
  • Column O ("SourceParameterType") = Input or Output
  • Column Y ("IsActive") = TRUE

Map to Subflow

To map to a subflow the following columns need to be filled in:

  • Column C ("TargetActionType") = SUB_FLOW
  • Column F ("SourceActionId") = Checksum of unresolved dependency
  • Column O ("SourceParameterType") = Input or Output
  • Column Y ("IsActive") = TRUE

Map to Existing Flow

Mapping to an existing flow with a checksum doesn't sense. Instead check mapping without a checksum instructions below.

Map to Script

Mapping to a script with a checksum doesn't sense. Instead check mapping without a checksum instructions below.

Without Checksum

Using Rules Dashboard

Map to New Flow

When choosing to create a new flow the flow will not contain any business logic, it will be an empty flow that the user will need to fill in later. After the first export, the new flow's ID and Name will be populated in the Rules table so that for every subsequent export, Rules will map to this newly created Flow.

Map to Existing Flow

To map to an existing flow, the ID and Name of the flow are required. If Rules generated these in a previous export then no action is required and they should already be populated. If they are not populated reference the following article on how to find an existing flow's Name and ID: How to Find Target Names and IDs in PAD

Map to Script

When mapping to a script the user is replacing the custom activity with new logic that is written in any of the available scripting languages. The most common is mapping directly to Robin Script, which is the underlining scripting language behind Power Automate Desktop. See Script Mapping for more detail.

Map to Subflow

Because without a checksum there is no no business logic to export Blueprint is unable to migrate these as subflows.

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") = VARIABLENAME_FLOW
  • Column C ("TargetActionType") = EXTERNAL_FLOW
  • Column G ("SourceActionName")= [Variable or Expression]
  • Column Y ("IsActive") = FALSE
  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 Subflow

Fill in the following columns

  • Column C ("TargetActionType") = SUB_FLOW
  • Column F ("SourceActionId") = Checksum of unresolved dependency
  • Column O ("SourceParameterType") = Input or Output
  • Column Y ("IsActive") = TRUE
Scenario 3) 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 4) 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?