Automation Anywhere to Power Automate Desktop Post-Migration

After an AA process has been migrated over to PAD, there will be some actions that could not be migrated over/ require review to ensure correctness. Below are some actions that may require revisions:

  1. VARIABLES
    1. AA Global Variables
      Global Variables do not exist in PAD. User will need to find a way to recreate the necessary global variables to call them.
  2. LABELS
    1. Labels starting with L followed by a string of numbers
      User should delete these labels. Not relevant to AA to PAD migrations
    Labels exist post migration as they are used for a variety of different automation solutions, some of which require the use of labels after IF statements. In the case of AA, these can be deleted.
  3. NON-COMPLIANT ACTIONS
    Depending on your organization's security policies, some users may not be allowed to utilize certain actions, such as 'run scripts' or 'send email', due to compliance issues. If not, they will be brought over as a TODO comment (see below) that must be manually configured and completed.
    1. Send Email
    2. Run VBScript
    3. Any action involving sensitive/encrypted text
  4. PARTIALLY MIGRATED ACTIONS
    Some actions can only migrated partially and will be up to the user to complete. Usually, this is due to an action requiring credentials, which we do not migrate for security purposes.
    i.e., These actions will have an error in PAD after export, like an email action missing the relevant username and password.
  5. COMMENTS
    1. SRC
      SRC comments describe what the action originally was in AA. Use as a reference and review code that follows and check for correctness.
    2. TODO
      TODO comments describe what the user needs to do in various situations. It may be reviewing the next line(s) of code, adding an action that couldn’t be migrated, or asking for verification that migrated step looks correct.

Some of the more common TODOs and how to handle:

TODO: NO MATCH FOUND FOR "metabot name" IN EXTERNAL FLOW MAPPING TEMPLATE FOR DESKTOP CALL

This is a unmapped metabot. To map metabots please refer to https://blueprintsys.helpdocs.io/article/0zh0ewrbu2-aa-pad-metabot

TODO: String Operation

Any AA string operation that has an equivalent action in PAD will be mapped.

i.e., Some actions like Before-After do not have a PAD equivalent and will be left as a "TODO: String Operations: Before-After" for the user to adjust