For Uploading a Bot to the Control Room
Use the Enterprise Customer to manually upload and download TaskBots, Master Bots, MetaBots, and Workflows with any related dependencies to and from the Repository.
From Version xi.3.iv and later, the Enterprise Customer automatically downloads the latest TaskBots and associated dependencies from the Command Room when a user with Attended Bot Runner license logs in to the Enterprise Client. Additionally, the Parent Task option allows a user with Attended Bot Runner license to automatically update parent TaskBotsouth and associated dependencies during run time. Run across Automatically update TaskBots
Note: When Version Control is enabled for Version xi.3 and later, automatic uploading and downloading of tasks and dependencies is available.
To admission the upload or download feature select a file and right click, or select a file and click upload or download in the menu.
Use the Export to CSV option to export the dependent files listing in the CSV format when y'all upload or download a TaskBot with dependent files to or from the Automation Anywhere Command Room repository.
Note: From Version eleven.three.four, the Relative Path of the dependent files is besides included in the CSV file when you apply the Export to CSV option.
The following list of dependent file types are automatically included when using the Enterprise Client uploaded or downloaded feature.
| ATMX - Automation Anywhere Task File | PDF - Portable Document Format |
| BMP - Bitmap | PKX - Rational XDE (IBM) |
| CSV - Comma Sepreated Values | PNG - Portable Network Graphic |
| Dr. - Microsoft Word Certificate | TXT - Text |
| DOCX - Microsoft Word Open XML | XLS - Microsoft Excel File |
| EXE - Executable File | XLSX - Microsoft Excel Open XML Spreadsheet |
| JPEG - Joint Photographic Experts Group | XML - Extensible Markup Language |
| MDB - Microsoft Access Database |
VCS enabled upload and download
When Version Control Service (VCS) is enabled, upload or download bots and whatsoever related dependencies, such as other TaskBots, MetaBots, IQ Bots, and other related dependencies. This simplifies the process of uploading and downloading TaskBots to Control Room, eliminating the need to upload dependencies separately.
-
To upload a Master Bot, you lot must checkout the file.
- All bots must have a unique name regardless of which user uploads the bot.
- The task dependency scanner and Uploading - Pending Changes or Files works for files that are new, checked-out, and eligible for upload.
- When VCS is enabled, you can download all the tasks and dependencies.
Upload and download failure remarks
When a bot or dependent files fails to upload or download, the Remarks column displays the reason for the failure.
- Invalid file format
- The file format is non supported by Automation Anywhere.
- File not constitute
- The file path to an application used in a TaskBot cannot be resolved.
- Not licensed
- A user without the correct role or license configuration cannot download or upload a bot with all of its related dependencies.
- Password protected bot
- A bot that is password protected cannot be uploaded or downloaded.
- Insufficient folder privileges
- When the user trying to upload or download a bot does not have the required access permissions for that particular binder.
- Cyclic dependency
- A potential cycle conflict exists betwixt bots when the aforementioned files are included in dependent bots.
- Variabalized path
- The specified variable in the file or binder path does non match the $AAAApplicationPath$ used to select, open, or relieve files and folders.
- Locally renamed MetaBot
- When a user renames a local copy of a MetaBot and information technology no longer matches the proper name of the MetaBot used in the associated TaskBot.
- File with same name already exists
- When VCS is enabled and a user tries to upload a file that already exits in the repository.
- File is force unlocked past server administrator
- When VCS is enable, an administrator force unlocked file cannot be uploaded to the repository.
Source: https://docs.automationanywhere.com/bundle/enterprise-v11.3/page/enterprise/topics/aae-client/bot-creator/working-with-automation-tasks/uploading_downloading_task_dependencies.html
0 Response to "For Uploading a Bot to the Control Room"
Post a Comment