Scribd
Upload
22 views

Transitioning Bots Using The Automation 360 Control Room - Step List

This document provides steps to transition bots between Automation 360 Control Room environments during Bot Lifecycle Management. It outlines exporting a bot from one Control Room which generates a download link. It then describes importing the bot zip file into another Control Room, placing it in the public or private repository. The prerequisites are administrator credentials or permissions to export, import, and access folders.

Uploaded by

Food safety Project
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
22 views

Transitioning Bots Using The Automation 360 Control Room - Step List

This document provides steps to transition bots between Automation 360 Control Room environments during Bot Lifecycle Management. It outlines exporting a bot from one Control Room which generates a download link. It then describes importing the bot zip file into another Control Room, placing it in the public or private repository. The prerequisites are administrator credentials or permissions to export, import, and access folders.

Uploaded by

Food safety Project
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Transitioning Bots Using the Automation 360 Control Room - Step List

Introduction to the Course

This course provides the steps to deploy bots from the Automation 360 Control Room environment
to another Control Room during Bot Lifecycle Management (BLM).

Introduction
This demo will help you to move bots between Control Rooms.

Prerequisites
You need:
• Administrator credential, or
• Run as User with the following permission:
o Export Bot
o Import Bot and
o Folder access permission

1
Exporting and Importing Bots from One Automation 360 Control Room to Another
1. Exporting Bots from a Control Room

i. Login to the Automation 360 Control Room as Control Room administrator.


ii. Select Automation.
iii. Click Export bots.
iv. Enter a name for the export bot activity or accept the default export bot activity
name.
v. Select the required bot you want to export from the list of available files in the Bots
and files tab.
vi. Click the right-arrow button to confirm the bot selection.
Note: It is best practice to use the Search field to look for a specific bot. You can
search for a specific bot by name or type using the drop-down menu.
vii. Click Next. The bot dependent files, if any, will be displayed, in the Select
dependencies tab.
viii. Click Next. All related packages are displayed in the Select packages tab.
ix. Select any individual packages you wish to remove from the export file and click the
left arrow button or select the Exclude bot packages option to remove all packages
from the export.
x. Click Export bots and files. The bot and required files are exported and a download
link to the zip file is generated.
xi. To access the link, navigate to Activity > Historical to find an activity item which
corresponds to your export job. A download link is available inside the activity
historical item. If your Control Room is configured to send emails via SMTP, an email
will be sent to you with a download link inside.
xii. Download the zip file and save it to a location for import to another Control Room.
Notice that the zip file consists of the bot file in the Automation Anywhere folder,
the command packages and the .json file.

With this, you have successfully exported the bot and its corresponding files from the required Control
Room instance.

2. Importing Bots from a Control Room

i. Login to the Automation 360 Control Room as Control Room administrator.


ii. Select Automation.
iii. Click Import bots.
iv. Click Browse and select the bot to import.
v. Set the appropriate option based on whether the bot must be imported to the
Public repository or Private repository of the Control Room.
vi. Set the option for importing the bot based on whether or not a previous version of
the bot resides in the destination location.
Note: During import, if a file already exists, you can choose to either skip the bot or
file during the import process or overwrite the existing bot and file.

2
vii. Click Import bots. On completion, the imported Task Bot is placed in the public
repository and is ready for deployment from the new Control Room.

With this, you have successfully imported the bot to the required Control Room instance.

You might also like