[AA-> PAD] Metabot Mapping

If you have bots in AA that call metabots, this is how to link the calls to the correct desktop flows in PAD.

It's recommended that users create a spreadsheet of SourceObjectID, SourceActionID, and TargetActionIDs that they can copy and paste for easier mappings.
Only Value variables from AA are currently supported.
If text was Masked in AA, it will migrate as Sensitive Text in PAD. Otherwise it will migrate as Text.

Metabot-PAD Flow Mapping - Instruction.pdf

Metabot-PAD Flow Mapping.csv

How to find SourceObjectID, SourceActionID, Source Object Name, and Source Action Name:

  1. Open up the Digital Blueprint of the uploaded .atmx file
  2. Navigate to the "Run Logic" action in the Blueprint
  3. Expand the Utility Panel
  4. Navigate to the Properties section
    You can expand the viewer by clicking "Expand/Reduce"
  5. SourceObjectID is MbtPath(String)
    SourceActionID is LogicID(String)
    MbtName is SourceObjectName(String)
    LogicName is SourceActionName(String)

How to find TargetActionID:

You will have to already have your metabots created as external flows within PAD
  1. Create a new flow in Power Automate Desktop or go to an existing flow
  2. Create action Run Desktop Flow and select the external flow representing the metabot you would like to call
  3. Copy the Run Desktop Flow action you just created into notepad/word
    1. Should look something like this:
  4. TargetActionID is FlowId

How to set up input/output variables:

  1. User will need to copy columns A through H for each input/output variable called by the same external flow
  2. User only needs to define columns I through N for each input/output variable
    1. TargetParameterName is the value that is labeled Variable Name in the Input / Output section in the desktop pad flow that is acting as a metabot:
      The External Name is just the name the variable appears as when using the Run Desktop Flow action in the main flow. It is not what should be used in the mapping file and is only for visual purposes within Power Automate.