Prerequisites for Discovery Bot

To use Discovery Bot for your enterprise business processes, you must have an Automation 360 working environment and the associated dependencies installed: Bot Agent, browser extension, and so on.

Supported versions and server requirements

Verify that you have the correct Control Room version installed. The Control Room deployment can be cloud or on-premises.

Ensure your Control Room server requirements are set up before installation. See Control Room server requirements.

System requirements

For Discovery Bot users' recording processes or assigned bot creation privileges, verify that your device meets the following system requirements:
  • Windows machine is only supported for recording sessions.
  • Oracle database is not supported on Discovery Bot.
  • Set your local device credentials for any device that is connected to the Control Room. This is a one-time setup for each device. Ensure each device that you use accepts the credentials in your profile.
  • Set user device credentials
  • Register your device and install the latest Bot Agent version on your machine. If you have not already installed the Bot Agent, when you log in initially, you will be prompted to install the Bot Agent from the Processes tab. Follow the prompts to install the Bot Agent. This will automatically add your user credentials.

    Install Bot Agent and register device

  • To record processes using Google Chrome, the Chrome plug-in must be installed.

    Browser requirements for Automation Workspace

  • Ensure your environment is ready to begin recording and analyzing processes using the Discovery Bot recorder. The prerequisites are similar to the Universal Recorder.

    Record a task with the Universal Recorder

  • Verify the Discovery Bot recorder requirements are completed.

    Supported applications and browsers for Discovery Bot

Update proxy settings

You must update your proxy settings to add the Automation Anywhere URL domain to the trusted list. The added URL domain is specific to your region of Automation Anywhere cloud. If you are using your proxy to access our cloud, you must avoid a redirect to your proxy. Remove any authentication type settings and policy acceptance.

Installation requirements

The Discovery Bot installer is integrated with the Automation 360 installer. No separate installation is required for Discovery Bot On-Premises users. The IT administrator in your organization performs this task. See Installing Control Room On-Premises.
Note: Ensure your database server requirements are met before using SQL authentication mode to connect to the Control Room: Installing Control Room using Custom mode.
For custom installation, you can now change the default repository path location to a new location on your server after installation. The default path is: C:\ProgramData\AutomationAnywhere\ServerFiles. The Process Discovery files now reside in the ServerFiles folder.
Note: For Control Room admin. You must manually copy and paste the existing data into the new location if you change the default path to the new location.
The generated PDD file for an opportunity is now stored locally on your server by Automation 360 On-Premises. The path to the file storage is: C:\ProgramData\AutomationAnywhere\ServerFiles\ProcessDiscovery\opportunity. The existing PDD files will automatically be moved to the new location and will not be deleted when a reinstall or upgrade occurs in the Control Room.

Verify installation

After the installation is complete, log in to your Control Room as an administrator. The Discovery Bot tab is available for use from the left panel.

Process Discovery package

The Process Discovery package contains actions that record various object operations such as click (right or left), recording, and window resizing that are used during process recording sessions. View information about the Process Discovery package from the View package page (Manage > Packages > Process Discovery).

The package is included in the default packages. You can preload the default package when you connect to your device. Preloading the package helps to speed the start time of the recorder the first time you begin recording a process.

The actions in the package are not available for use from the Bot editor.