Bot Runner is a tool that you can use to run bots in any workspace and on any server or virtual machine. You can also execute multiple Bot Runners in parallel by adding them to multiple Windows accounts. To create an additional account, check this tutorial or contact your system administrator.
When the Bot Runner application is running, this icon is displayed in the system tray:
Right-click the icon to open a list of basic functions:
- "Run Bot"
- "Open Logs"
- "Check for updates"
Using the "Settings" button you can see Bot Runner's basic functionalities, which we overview in the section below.
Bot Runner tabs
Welcome is the starting tab of the Bot Runner. Use the “Run Bot” button to pick a .neex-file and run a workflow through it.
Login is the tab where you can log in to Bot Runner via token.
Once you are logged in, you can see the License tab. Here you find all the information about your account, including the availability of SaaS Orchestrator and Productivity Analytics.
Being logged in, you can also see the Orchestrator SaaS tab. Use it set the Bot Runner’s name you want to be displayed in the Orchestrator and connect any bot you have (.neex-file) to it.
Credentials is the place you must go to check the information about accounts. Here you can add a new account, manage the existing ones, or delete them. You can find more information on working with credentials in this article.
Go to Services if you want to log in to third-party platforms, so your bots can interact with them. That means you can use resources such as Google Sheets, Microsoft Office 365, or ABBYY OCR.
On the Proxy tab you can enable the use of this tool and specify the address of a proxy server. Read more about working with proxies in this article.
Certificates is a tab where you can enable or disable E-mail or HTTPS certificate verification. Note that disabling these resources can reduce the security of your network. Hence, check with your system administrator if this could have negative consequences in your case.
Here you find the Client certificates option too. If your workflow uses the "HTTP request" activity, you may need to use certain certificates to send the HTTP request, as some APIs require user authentication to receive the request.
Access the Execution tab to activate logging for each bot run. Read more about logs in this article.
Also, use the Status display option to choose how much information you want to see in the bot execution status window.
Here is what the complete status window looks like:
Finally, go to the Interface tab to select the theme that works better for you: Light or Dark.
As of version 8.4, you can maintain an active RDP session in Bot Runner. Manage this functionality from Orchestrator SaaS. Want to know more about RDP? So, check this article.