Skip to main content

AA Metabots

- Metabot-PAD Flow Mapping - Instruction.pdf ​​- RPA Framework Mapping.csv - Mapping Sheet with Example Data.csv Note : - Only csv file format is accepted - Not all columns need to be filled out for…

Sean Ellner
Updated by Sean Ellner
- Metabot-PAD Flow Mapping - Instruction.pdf
​​- RPA Framework Mapping.csv
- Mapping Sheet with Example Data.csv
Note:
- Only csv file format is accepted
- Not all columns need to be filled out for each mapping use case

When migrating Automation Anywhere v10 & v11 to Power Automate Desktop Blueprint has the ability to connect all Run Logic calls (e.g. calls to metabot logic) to the PAD flows that implement that logic.

There are two possible scenarios when exporting to PAD, either the target Flow already exists in PAD or Blueprint creates the target Flow automatically. Both of these scenarios are explained below.

Step 1: Generate Framework Mapping Sheet pre-populated with Metabot Logic signatures

  1. Download RPA Framework Mapping sheet from RPA Dashboard

The following columns will be auto-populated:

  • Column A ("SourceObjectId") = GUID of Metabot
  • Column B ("SourceObjectName")  = Metabot name
  • Column C ("SourceActionId")  = GUID of Action
  • Column D ("SourceActionName")= Name of Action within Metabot
  • Column F ("SourceActionType") = METABOT_LOGIC
  • Column G ("TargetActionType") = EXTERNAL_FLOW
  • Column M ("SourceParameterName") = Name of Parameter
  • Column N ("SourceParameterType") = Parameter Type (Input or Output)
  • Column O ("SourceParameterDataType") = Parameter Data Type (Text, Value, etc.)
  • Column T ("IsActive") = TRUE
A row will exist for every parameter. For example, a call to MyMetaBot.Add(NumOne, NumTwo) will create two rows, one for parameter NumOne, and another for parameter NumTwo

Step 2: Populate RPA Framework Mapping Sheet

Scenario 1: Flow Already Exists in PAD

In this situation, there are two assumptions:

  • The PAD flows representing the metabot is already be created along with their input/output parameters defined. This Flow can be anything from the metabot fully recreated in PAD, or a simple stub/placeholder for future implementation of the metabot logic in PAD.
  • A mapping sheet prepared and loaded into Blueprint that defines for each metabot logic and its parameters (signature), the corresponding PAD flows and parameters they will convert to

If these are both in place, exported flows will properly call the flow that represents the referenced metabot.

If either of these two are not in place, then Run Logic calls from Automation Anywhere will convert into TODO comments.

Read How to Find Target Names and IDs in PAD to learn how to fill in the necessary target columns to complete the mapping.

Scenario 2: Target Flow Does Not Exist in PAD

Users have two options, they can either manually create target Flows and follow the instructions above, or allow Blueprint to automatically create these Flows during Export. If users opt for Blueprint to create these Flows automatically, you can move onto the next step.

Step 3: Upload Finished Framework Mapping Sheet

Read Upload Completed Framework Mapping Sheet to learn how to complete your mappings!

How did we do?

Unresolved References

Work Queues Mapping

Contact