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

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: Run Logic

This is a metabot. For now, users will need to manually add this with a Run Desktop Flow action.

*Note* Run Desktop Flow is only available on PAD version 2.10 and onward

TODO: String Operation

Because AA and PAD structure manipulate text in different ways, some that we have mapped will be brought over via migration. Any with this comment will need to be completed manually.

TODO: Insert Keystrokes

Because AA and PAD structure using hardware strokes in different ways, some that we have mapped will be brought over via migration. Any with this comment will need to be completed manually.

TODO: Verify Continue Flow Option

Review error block code that follows and check if correct.

TODO: Please verify value of _Counter variable

Review value of variable and check if correct.