Automation 360

Bot Runner device requirements

Download as PDF

Automation 360
Features, licenses, and deployment
- Platform licenses
  - Enterprise Platform
  - Automator AI Platform Base
- Deployment models
- Cloud licensing FAQ
Release Notes
- Automation 360 Release Notes
- Community Edition Release Notes
- Sandbox environment
- Package updates overview
- Previous Package SDK Release Notes
- Process Discovery Release Notes
- Browser extensions for Automation 360
- Automation 360 feature comparison matrix
- Automation 360 IQ Bot feature comparison matrix
- Automation 360 IQ Bot version compatibility
Automation 360 Cloud
- Automation 360 FAQ
- Automation 360 architecture and resiliency
- Automation 360 Cloud FAQ
- Automation 360 software lifecycle policy
- Automation resiliency
  - Managing unexpected pop-ups
    - Configure pop-up handling
  - Record automation execution
    - Configure automation recording
    - Manage automation recording
- Upcoming feature deprecations
- In-product user assistance
Automation and generative AI
- AI Agent Studio
- Automator AI
- Data security for generative AI - FAQ
Set up Automation 360
- Get started with Automation 360 Cloud
  - Automation 360 Cloud prerequisites
- Installing Control Room On-Premises
- Set up Community Edition
  - Community Edition capabilities
- Get started with Bot Agent
- Naming guidelines for Control Room URLs
- Post-installation user management
- Update Automation 360 to latest version
  - Update Automation 360 on Microsoft Windows Server using scripts
- Install and update Automation 360 IQ Bot
- Log in to Automation Anywhere Control Room
- Create your first bot
- Run your first bot
- Moving from Automation 360 On-Premises to Cloud
  - Moving data using Control Room operations
  - Migrate using Control Room APIs
- Migrate to Automation 360
Configure Automation 360
- Users
- Roles
- Manage licenses
  - View license details
  - Installing additional licenses
- Create your users and assign their licensed roles
- Configure Settings
- Edit My settings
  - Edit profile settings
- Set up your bot repository
- Working with repositories, credentials and roles
  - Manage user credentials
- Credentials and lockers in the Credential Vault
Manage Automation 360
- Devices
  - About multi-user devices
    - Configure RDP-based deployment for multi-user devices
    - Convert an existing device to a multi-user device
  - Edit multiple devices simultaneously
- About device pools
- Add queue, Bot Runner, and device pool
- Configure Active Directory in Control Room
- Configure OAuth connections in Control Room
- Packages
- External key vaults for Automation 360
- Workload management
- Bot Lifecycle Management
Monitor Automation 360
- Automation Command Center
- Automation program lifecycle with CoE Manager
- Activities
- Audit log
  - Audit events list
  - Export audit data to CSV
- Code analysis
- Notifications
- Control Room log files
Build automations
- Process Composer
- Interactive forms
  - Add a form to bot
- API Task
- Connector Builder
- Recorders
  - Universal Recorder for object-based automation
  - AISense for recording tasks from remote applications
- Task Bots
- Templates
- Bot Store
- Advanced bots and packages
- Troubleshooting and debugging
Automation Co-Pilot
Automation Co-Pilot for Business Users
- Embed automations in your application using Automation Co-Pilot
- Using Automation Co-Pilot for Business Users on desktop
- Automation Co-Pilot for Business Users on the web interface
- Approvals in Automation Co-Pilot
  - Using and sorting the Tasks view
- Automation Co-Pilot status and notifications
Users and roles for Automation Co-Pilot
- Create users for Automation Co-Pilot
- Create a team and assign roles to team members
- Manage roles and teams for Automation Co-Pilot
- Scheduler users and device pools in Automation Co-Pilot
- Configure deployment type for bots
Automation scenarios
- Scenario: Generating insurance quote with Automation Co-Pilot and Process Composer
- Scenario: Developing and using templates in an automation
Document Automation
- Document Automation processing workflow
- Document Automation FAQ
- Intelligent document processing solutions - feature comparison matrix
- Set up your Document Automation environment
- Create a learning instance in Document Automation
- Improve extraction accuracy through validation
  - Improve table data extraction
  - Lock the validation feedback
- Connect learning instance
  - Extracting data from check boxes
- Integrate third-party parser in learning instance
  - Create a parser and configure with learning instance
    - Sample codes for parser contracts
    - Sample SDK Project: AWS Textract
- Publish the learning instance to production
  - Build a bot to upload documents to Document Automation
  - Deploy the learning instance assets
- Validating documents through Automation Co-Pilot validator
  - Validate documents as Validator user
- Export or Import learning instances
  - Incorporating validation feedback in export/import of learning instances
- Create custom models in Document Automation using Standard Forms
- Document Automation support for Google Custom Document Extractor (CDE)
- Document Automation - Data extraction using generative AI
- Languages supported in Document Automation
  - Language support matrix and OCR engines
- Document Automation Community Edition
  - Create a learning instance in Community Edition
  - Process documents in Community Edition
Automation 360 IQ Bot
- IQ Bot architecture diagram
- Using Automation 360 IQ Bot On-Premises
- Using Automation 360 IQ Bot Cloud
- IQ Bot user personas and roles
  - Defining a custom role for IQ Bot
  - Creating a user with an IQ Bot specific role
- Languages supported in Automation 360 IQ Bot
- About the Classifier
  - Create a new document group
- Create a learning instance
- Train a learning instance
- Manage learning instances
- Rotate the external key
- Use the IQ Bot Validator
- Review the dashboard
  - Performance report page
  - Performance report details
- Custom domains in IQ Bot
- Using IQ Bot for standard forms
Process Discovery
- Overview of Process Discovery
  - Options to reduce exposure of sensitive data
- Process Discovery user roles
- Create Process Discovery users and assign roles
- Integrate SAML with SSO for Process Discovery
- Create your event reporting password
- Create a URL and application list
- Configure Observer activity
- Use Process Discovery with Kibana dashboard
  - Access the Kibana dashboard
- Create a cycle
- Classify application screens and create web applications
  - Applications with auto-assigned screen signatures
- Review Events and filter data
- Mining for processes
- Analyze and prioritize processes
- Creating groups for the process and generate a PDD
- Process Discovery - CoE Manager integration
- Getting started with Privacy Enhanced Gateway
- Process Discovery Sensor application
- Process Discovery FAQ
- Process discovery by using Discovery Bot
Bot Insight
- Business analytics through Bot Insight
- Accessing Bot Insight
- Using Bot Insight
  - Business analytics
    - Configuring a task for business analytics
- Using widgets
- Data connector for Power BI
- Configure Tableau web data connector in Bot Insight
API References
- Control Room APIs
- Filtering, pagination, and sorting
- API response codes
- Comparing Automation 360 and Enterprise 11 APIs
- Configure the Control Room
- Roles and permissions
- How to find a migration journalid
- Using Auto registration API
Glossary

Bot Runner device requirements

Download as PDF

Updated: 2024/07/08

Bot Runner device requirements

Review the hardware requirements, compatible operating system versions, and browser types supported for creating and running bots on a device. The same requirements are also valid for Automation 360 Community Edition.

Hardware requirements for registered devices

You communicate with the Control Room through a registered local machine (device). Bot Creators and Bot Runners use the registered devices to create and run bots. Part of registering a device with Automation 360 is installing a Bot Agent.

For more information on the minimum hardware requirements of a device for installing the Bot Agent, see Hardware requirements,

Additional CPU or processor on registered devices

AISense Recorder: Additional CPU or processor is required on a device if the existing CPUs are utilized by customer applications. It is also required in case of a VDI infrastructure where CPU or processors are shared across the infrastructure.

Platform compatibility for registered devices

A device used to connect to the Control Room and perform bot tasks must meet the platform requirements.

Note: Platform requirements are different for Control Room and Bot Agent.

Registered devices: Physical machines that you want to use for creating bots or deploying bots and running any of the supported operating systems.
Terminal servers: Using remote desktop (RDP), running any of the supported operating systems is supported on Automation 360 Version A2019.11 or later.
Virtual machines: Bot Agent is supported on all VMs where the supported Windows OS has been hosted on Version A2019.09 or later. For example, Virtual Desktop Infrastructure (VDI) are supported on Amazon Web Services, Microsoft Azure, Google Cloud Platform, VMware virtual machines, and Oracle Virtual Box.

Supported operating systems for registered devices

A device used to run the Bot Agent, connect to the Control Room, and perform bot tasks as a Bot Creator and Bot Runner must meet the operating system requirements.

For more information on the compatible operating systems for registered devices, see Operating system compatibility.