Read and Review Automation Anywhere Documentation

Automation 360

Close Contents

Contents

Open Contents

Import an AARI process

  • Updated: 8/12/2021
    • Automation 360 v.x
    • Build
    • AARI
    • Process flow

Import an AARI process

You can import an Automation Anywhere Robotic Interface (AARI) process from one Control Room to another.

Prerequisites

  • Ensure that the following rights are enabled to import processes:
    • Import process permission
    • Create folder permission, if it is required
    • Check-in permission
    • Manage package permission
  • The process directory path is case-sensitive. So ensure that the export and import paths use the same case in the Control Room to avoid any process execution failure.
  • You require a Bot Creator license to import the process either into the private or public workspace.

In this task, the required process is already exported and an email is received with a link to the zip file containing the package to import.

Any previously exported process is located in the public repository and must be imported and checked in so that it can be deployed from the new Control Room.

You can import the process only into your private workspace. After the process is imported, you must then check in the imported files to the public workspace in order to complete the import process activity.

Procedure

  1. On the left pane, click Automation.
    A list of available bots and forms is displayed.
  2. Click Import bot and browse and select the process to import.
    Note: This option currently applies to both bots and processes.
  3. Select the option to import a process into the private or public workspace.
  4. Set the option for importing the process based on whether a previous version of the process resides in the destination location.
    During the import, if a file already exists, you can choose to either skip the process during import or overwrite the existing process and file.
  5. Click the Import bot icon.
  6. Navigate to the private repository to find and select the imported process.
  7. Click Check in process.
    Important: All related dependencies are checked in. If the process is imported to a public folder, then it has to be checked out and then checked in again for it to appear on the web interface. However, if the process is imported to a private folder, then it can only be checked in but not checked out.
  8. Update the comment for the check-in process.
  9. Click Check in.
    On completion, the imported process is placed in the public repository and is ready for deployment from the new Control Room.
Send Feedback