Lesen und beachten Sie die Automation Anywhere-Dokumentation

Automation Anywhere Automation 360

Inhalt schließen

Inhalte

Inhalt öffnen

How AAApplicationpath variable is migrated

  • Aktualisiert: 10/11/2021
    • Automation 360 v.x
    • Erkunden
    • RPA Workspace

How AAApplicationpath variable is migrated

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

Migrate from 11.x using the restored 11.x database

When you migrate to Automation 360 using the restored 11.x database, the migration process creates the AAApplicationPath global value when the first Bot is migrated using the Bot-Migrationsassistent. The migration process also copies the value for the AAApplicationPath system variable specified for each user in 11.x and set that value to the AAApplicationPath global value for all those users in Automation 360. The migration process updates the references you have used in 11.x Bots with the AAApplicationPath global value available in the Automation 360 Control Room which eliminates any requirement for updating the migrated Bots to use the AAApplicationPath.

Wichtig: When you migrate Bots using the Bot Migration Paket, 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 11.x must update the AAApplicationPath global value with the value that is used in 11.x.

Migrate from 11.x using the restored 11.x database

Migrate from 10.x

When you migration from 10.x, 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 10.x must update the AAApplicationPath global value with the value that is used in 10.x. 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 10.x 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.

Anmerkung: Ensure that the CAN be changed option is selected when you create the AAApplicationPath global value. Bot Creators and Bot Runners must set the value for the AAAplicationPath global value before they run the migrated Bots.

Migration von 10.x zu Automation 360 On-Premises vorbereiten

Manually migrate from 11.x or 10.x

When you manually migration from 11.x or 10.x, 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 11.x or 10.x must update the AAApplicationPath global value with the value that is used in 11.x or 10.x.

Voraussetzungen für die manuelle Migration

Feedback senden