Bot Runner is a tool that allows you to run bots in any workspace and on any server or virtual machine. You can also run multiple Bot Runners in parallel by creating multiple Windows accounts and running one Bot Runner on each account. To create an additional account, you can contact your system administrator, or you can do it yourself by, for example, following this tutorial. When the application is running, a Bot Runner icon is displayed in the system tray.
Bot Runner icon in the system tray
Right-clicking on the icon will open a list of basic functions: "Settings", "Start Bot", "Stop tracking", "Open Logs", and "Quit". The "Exit" button closes Bot Runner. The "Settings" button allows you to see the basic functionality of the program, which we overview in the section below.
Bot Runner interface
Bot Runner tabs
Welcome - starting tab of the Bot Runner. The “Run Bot” button allows you to pick a .neex-file to launch the workflow.
Login - here you can log in to work with full functionality of the Bot Runner.
License - in this tab you can find all the information about your account, including availability of Orchestrator SaaS and Productivity Analytics. You need to log in to make this tab appear.
Orchestrator SaaS - here you can set the Bot Runner’s name, which will be displayed in the Orchestrator. You can also connect the created bot (.neex-file) to the Orchestrator in this tab.
Credentials - this tab contains the information about the accounts you use to work with bots. Here you can add a new account, manage the existing accounts, or delete them. You can find more information on working with credentials in this article.
Services - you can log in to services that your bots interact with in this tab. It is necessary to use the functionality that uses Google services (Google Sheets), Microsoft services (Office 365) or ABBYY OCR.
Web browser - here you can pick the browser that the bot will interact with.
- Load user profile with cookies, extensions, etc. - If this option is enabled, the bot will load all user data when launching the browser. For example, if the bot will interact with some website that requires authorization, then enabling this option will be necessary, otherwise the bot will not be able to perform these actions.
It is important to make sure that the browser is closed before starting the workflow. If this option is disabled, the bot will open the browser in a new window, and no saved data of profiles or sites will be loaded.
- Don’t close the browser after execution of a bot - if this option is disabled, then the bot will close the browser after execution of a workflow.
- Command line arguments work with Google Chrome and Microsoft Edge. This option allows you to enter command line arguments to start the browser with additional parameters.
Proxy - use a proxy server. Click the switch to enable the use of proxies and specify the address of the proxy server you want. You can read more about working with proxies in this article.
Certificates - in this tab, you can enable or disable E-mail or HTTPS certificate verification. Note that disabling certificate verification can reduce the security of your network. Check with your system administrator if this could have negative consequences in your case.
- Client certificates. If your workflow uses the "HTTP request" activity, you will probably need to use certain certificates to send the HTTP request, as some APIs require user authentication to receive the request.
Execution - here you can activate logging for each bot run (Automatically create logs for each run). Read more about logs in this article.
- Enable status window - this setting allows you to enable or disable displaying a window showing the bot's run status.