The “Show Filter” button helps to filter the robot based on the Robot Name, Machine Name, Status and Tags. The “Search” button can be clicked after entering the required data in the respective field(s).
The “Refresh” button which is present, helps to reload the Robots Details window so that the latest robot details can be viewed.
Each of the columns in the Jobs Tab is explained below with the help of a navigation workflow:
The Build 8 of RPA Genie has been released on 13 May 2024. This release notes lists out all the additional features, fixes and improvements that have been made to RPA Genie when compared to Build 7.x.x. The first version of RPA Genie is 8.1.0.0 and the final version is 8.6.0.0. Below you will find the comprehensive details about the features and updates for different versions of Build 8. Our relentless efforts are directed at enhancing its capabilities to deliver the best possible automation experience, exceeding expectations and enabling our users to reach new levels of productivity and efficiency.
Release Date: May 13, 2024
Release Date: July 23, 2024
Release Date: September 06, 2024
Release Date: September 26, 2024
Release Date: October 25, 2024
Release Date: January 06, 2025
Release Date: March 27, 2025
Release Date: May 12, 2025
Release Date: January 05, 2026
RPA Genie Health Monitoring Tool is a standalone service which is responsible for monitoring Genie Database and Genie Service connections to which the BOT Manager is connected. This is a new tool that helps in monitoring all the BOT machines connected to a particular BOT Manager which runs in the background and needs to be installed separately. It will notify the user through an Email if any of the connections are down.
It has been observed on various occasions where the BOT service and its database were not working as expected in the client machines. During these instances BOTs are throwing different errors and BOT will not be able to perform the automation. Our team has identified the root cause of the different scenarios where the BOTs can be down.
There are three main common cases where the BOT may stop working or throw errors. The first one is when the BOT machine is down, the second would be when someone may accidentally kill the particular service/process. In these two scenarios, the BOT manager will act effectively and push the notification to escalate the same. However, if the BOT Manager itself goes down, we wouldn’t get any notifications regarding the status of the services and the database. Here, the team took up this issue and introduced the RPA Genie Health Monitoring Tool.
RPA Genie Health Monitoring Tool has a separate installer file for configuring the service, which can be downloaded to a specific location in your system. After downloading the installer file, double-click and open it. A window named “RPA Genie Health Monitoring Installer” will appear as shown in the image below. Click on the “Install” button.
Check the License Agreement checkbox and click on the “Next” button to continue.
N.B: – License agreement is described in the box under License header.
Click on “Next” to continue.
Under the “Service Options” page, you need to provide the following details:
The Genie Database acts as a comprehensive storage system for storing all the metadata associated with a particular application or system. For effective data management, retrieval, and manipulation for various processes and functionalities, it preserves key information about data structures, configurations, and relationships within the application.
The following fields of the RPA Genie Service Database Settings page are editable by the users:
N.B: – If Windows authentication is selected provide the AD username and password. However, if it’s SQL authentication, provide the corresponding SQL username and password.
After providing all the required details, click on “Test Connection”. If the connection is successful, then a pop-up message, “Connection Success” will be displayed as shown in the image below and you can click on “OK” to proceed further. Click on the “Next” button to continue.
If the Notification settings are already added to the BOT Manager, then the fields in the Health Monitor Email Notification Settings page will be auto populated. If not, you can provide the respective SMTP details which the service will use to send out email notifications. Here, you can fill the SMTP Server details, SMTP port and From Address. Next, you will be able to configure SMTP Sender Email ID and Password. Finally, select the SMTP Secure Socket option from the available dropdown list.
In the Health Monitor Notify Mail Details page, you can provide the Email ID to which the notification has to be sent. You can also give multiple Email IDs separated by comma. Polling Interval is the interval in which the application will be checking for the status of the Service and Database. Default polling interval would be 10 minutes. Click on the “Install” button to install the application.
N.B: – Polling Interval can be changed according to user preference.
Finally, click on the “Finish” button to complete the installation.
Go to “Services” window and right-click on “RPA Genie Health Monitor”, select “Properties” from the given options.
Navigate to “Log On” section and choose “This account”. You can manually provide the Service account along with the domain. Also, fill the “Password” and “Confirm Password” field. Click on “OK”.
N.B: – A service account is a user account that’s created explicitly to provide a security context for services that are running on Windows operating systems. The security context determines the service’s ability to access local and network resources.
Click on the service and select the restart option.
N.B: – Make sure the status of the service is “running”.
Below is the sample error message sent via Email:
The RPA Genie Administrative Console is a diagnostic tool that can assess functionality, guide users about the status of a particular functionality, and let users review and modify the settings that regulate the way RPA Genie Service operates. It will be installed at the same time as the RPA Genie service and will be available on the Genie Server.
In the “Home Page” of the RPA Genie Admin Console, we can view the Service diagnostic Summary and Health monitoring status.
In the “Service Diagnostic Summary” section, the following fields can be seen:
The “Health Monitoring” section includes the following fields:
The user will be redirected to the Genie Diagnostic Validation when they click on the “Diagnostic” section of the RPA Genie Admin Console, where six primary validations are listed, as follows:
The 
(tick mark) next to each validation indicates that there have been no validation errors. But if any of the validations has a 
(cross mark) next to it, then the user can check the error by simply clicking on that particular 
(question mark) icon. Next, a wizard will appear and suggest possible resolutions as illustrated below:
As shown in the above figure, an error has occurred when RPA Genie SQL Connectivity was being validated. On clicking the (question mark) icon, a pop-up wizard will be displayed with a list of all possible solutions.
The following list of potential fixes has been provided for each validation if any of the validation is unsuccessful:
We can access a list of options in the RPA Genie Admin Console by clicking on the “Settings” tab, as illustrated in the image below.
IIS, or Internet Information Services, is a web server software by Microsoft that is used for Windows servers. It is utilized to host and manage websites, web applications, and services.
From the IIS page of RPA Genie Admin Console, users can configure the following fields:
Authentication methods are stored and managed centrally in the AppForms DataBase. It enables us to securely store and access authentication information, such as usernames and passwords, which can be used to confirm the legitimacy of users accessing applications or systems while improving security and access control.
The RPA Genie Admin Console’s AppForms Database page allows the user to make changes to the following fields:
Additional Settings Wizard:
The Genie Database acts as a comprehensive storage system for storing all metadata associated with a particular application or system. For effective data management, retrieval, and manipulation for various processes and functionalities, it preserves key information about data structures, configurations, and relationships within the application.
The following fields of the Genie Database page are editable by the users:
An application pool is a feature of the web server software (like IIS on Windows) that isolates and maintains web applications by giving them their own process space and resource allocation. Through the Application Pool page users can configure the username and password.
The Mail Notification page provides users with the ability to customize email-related settings. These settings help users to tailor their email notifications according to their preferences and needs.
If the “Use Default” checkbox is checked, then the default credentials will be used to send the
mail through the Microsoft server. If it is unchecked, then the mail is sent with the respective SMTP credentials provided in Bot Manager. This is only applicable to Microsoft SMTP Server.
A robot connection configuration defines the connection frequency, ping intervals, and idle timeout parameters used by a robot to communicate with a Service URL. Additionally, it controls how robots interact with the Service URL, determining whether they can connect automatically or whether they must manually register.
The Robot Connection page enables the user to customize the following fields:
Machine connection refers to the process of establishing and managing the network connection between a machine and a designated Service URL. Users can configure settings like connection frequency, disconnection idle timeout, and unique identifiers from the Machine Connection page to enable communication and data exchange between the machine and the designated service.
A job scheduler automates job execution by defining how often specific jobs will be running, their active execution intervals, and the maximum idle time before termination.
Following are the fields that the user can edit from the Job Scheduler page:
Establishing an RPA Genie environment necessitates a series of steps to guarantee the proper configuration of both infrastructure and software components which are essential for the seamless execution of automation tasks. Ideally, there should be six machines at disposal for the setup, catering to the requirements of Development (Dev), Quality Assurance (QA) and Production (Prod) environments.
The diagram provided below visually depicts the arrangement of the RPA Genie environment. Depending on the number of developers actively engaged in automation, there is flexibility to provision extra development machines. Furthermore, for efficient parallel process execution, additional QA or Production machines can be deployed as required.
NB: The Windows server and Database server can be shared between Development and Quality environments.
RPA Genie can be set up using Virtual Machines/Physical Machines for each of the BOTs. There are two different architectures that RPA Genie can set up:
In the independent Bot machine architecture, the resources for each machine will be allocated separately and the bots can be created based on the user license. In this case, there will be multiple bot machines based on the number of automations to be automated and the number of parallel automations that run at the same time. If a single machine fails then the other machines will not get affected and it will continue with the assigned automation.
In the Terminal Server architecture, it is possible to create multiple bots under different user accounts, each dedicated to interacting with distinct applications or processes. The execution of processes on the terminal server relies on “Terminal Server user licensing”. It’s important to note that each bot created within the terminal server environment will share the allocated resources of the terminal server.
RPA Genie Platform has three layers, they are Client, Server, and Data.
Client: This layer consists of a bot machine.
The Bot machines would consist of three components as outlined below.
Server: This Layer consists of a Bot Manager.
The Bot Manager server would consist of two components as outlined below.
Data: RPA Genie uses the relational Database SQL to store all the metadata of the RPA Genie components like Bot, Processes, Queues, Triggers, Resources, etc.
RPA Genie Bot Manager is a web application that connects multiple bots and can manage each of the bots connected to it. Using this component, you can connect multiple bots to the bot manager, add, schedule, monitor the automation, and control automated bots and processes.
Q: What is RPA Genie? what does it do? Explain RPA Genie BOT Manager.
A: RPA Genie is an automation platform developed by ClaySys. The core purpose of RPA Genie is to automate tasks and business processes.
RPA genie Bot Manager is built on AppForms that enables you to manage your Robots in executing business processes.
Q: What are key features of RPA Genie BOT Manager?
A: The key features of RPA Genie are as follows:
Q: Is RPA Genie Server a Windows service? Can it be run as an AD user account of our choosing?
A: RPA Genie Server is a service that is hosted on the IIS. Hence, you will be able to run as any AD user.
Q: RPA Genie BOT Manager – how often do the bots/agents report back into the Genie Bot Manager? And, what does that traffic overhead look like?
A: The traffic overhead will be based on the number of automation and the type of automation that is configured. BOTs perform the logging to the BOT Manager based on the actions performed by the BOTS. Each action is recorded to the BOT service.
Q: Since this is a web-based application, do you only utilize IIS or is there a lot of other software that complements the IIS web service (like a full-blown application install)?
A: We only use IIS.
Q: If we delete a process, is there a possibility of losing the statistical data that we were tracking such as time saved, number of transactions, etc.?
A: It will not affect statistical data.
Q: Is it possible for us to rename the Robot Name in BMT which wouldn’t affect the actual machine name or AD user name. We are aware that its possible in the Robot details part but would it affect the process in any way?
A: It’s possible to change the robot name on the Robot edit page of Bot Manager. And it won’t affect the actual machine name or AD user name. (Make Sure we have the latest stable Appforms Extension Installed).
Q: Can we restrict a BMT user to use only one bot machine?
A: Currently, We don’t have support to limit the users to use only one bot machine.