How AAApplicationPath variable is migrated

The AAApplicationPath variable is used in Enterprise 11 and Enterprise 10 to specify the physical path of a bot or file that is used in the current bot. The AAApplicationPath system variable returns the path that is set in Tool > Option of what is known as the “client application”.

Migrating from Enterprise 11 using restored Enterprise 11 database

When you migrate to Automation 360 using a restored Enterprise 11 database, the migration process performs the following actions:

  • Creates the AAApplicationPath global value when the first bot is migrated using the Bot Migration Wizard.
  • Copies the value for the AAApplicationPath system variable specified for each user in Enterprise 11 and sets that value to the AAApplicationPath global value for all these users in Automation 360.
  • Updates references you have used in Enterprise 11 bots with the AAApplicationPath global value available in the Automation 360 Control Room, eliminating any requirement to update the migrated bots to use the AAApplicationPath.
  • Updates the path in the Run Task command set in the Enterprise 11 bot. For example, if the path in the Run Task command is set to $AAApplicationPath$\Automation Anywhere\My Tasks\child-task.atmx in Enterprise 11, this path is automatically converted to Bots\My Tasks\child-task.atmx after migration.

    Therefore, no manual update is required and the bot runs as is after migration.

Important: When you migrate bots using the Bot Migration package, you must manually create the AAApplicationPath global value. After you have created the AAApplicationPath global value, all users who have used the AAApplicationPath system variable in Enterprise 11 must update the AAApplicationPath global value with the value that is used in Enterprise 11.

See Migrate from Enterprise 11 using a restored Enterprise 11 database.

Migrating from Enterprise 10

When you migrate from Enterprise 10, you must manually create the AAApplicationPath global value in Automation 360 with the CAN be changed option selected. After you have created the AAApplicationPath global value, all users who have used the AAApplicationPath system variable in Enterprise 10 must update the AAApplicationPath global value with the value that is used in Enterprise 10. This update ensures that when you run the bot in Automation 360, the AAApplicationPath folder value is uniquely resolved for each user.

Example: If the Enterprise 10 path value for AAApplicationPath is D:\John.Doe\My Documents\Automation Anywhere Files, then you must create the AAApplicationPath global value in Automation 360 and update with this path.

Note: Bot Runners and Bot Creators must update the global value for the AAApplicationPath in the Control Room before they run migrated bots in Automation 360.

See Prepare for Enterprise 10 to Automation 360 On-Premises migration.

Manually migrating from Enterprise 11 or Enterprise 10

When you manually migrate from Enterprise 11 or Enterprise 10, you must manually create the AAApplicationPath global value in Automation 360 with the CAN be changed option selected. After you have created the AAApplicationPath global value, all users who have used the AAApplicationPath system variable in Enterprise 11 or Enterprise 10 must update the AAApplicationPath global value with the value that is used in Enterprise 11 or Enterprise 10.

See