Variable Name Dependency Mapping
Variable Name Dependency Mapping
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.
Using Rules Dashboard
Custom Actions Rules dashboard is currently mostly read-only. The only available functionality is to enable rules or bulk delete rules.
Using CSV
- 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
- 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
- Import Rules CSV
To import rules, from the Rules dashboard, click Advanced -> Import Rules From CSV