1. Robility Manager
1.1 Get Started
Robility Manager is a centralized platform designed to manage, monitor, and deploy robotic process automation (RPA) workflows seamlessly across an organization. It serves as the command center for all automation activities, ensuring efficient execution and orchestration of processes at scale.
Key Features of Robility Manager
Robot Management
a. Facilitates the management of attended and unattended robots within the automation ecosystem.
b. Allows efficient assignment and monitoring of robot activities to optimize resource utilization.
Scheduling Robots
a. Provides advanced scheduling capabilities to trigger automation processes at specific times or events.
b. Supports recurring schedules and ad-hoc executions for flexible task automation.
Asset Management
a. Centralizes management of critical assets like credentials, configuration data, and reusable components.
b. Ensures secure storage and controlled access to sensitive information.
Interact
a. Enables the creation and management of dynamic work queues to distribute tasks across robots effectively.
b. Offers prioritization, retry mechanisms, and workload balancing for enhanced productivity.
Monitoring and Logging
a. Delivers real-time monitoring of robots, workflows, and processes.
b. Provides detailed logs and insights to troubleshoot issues and maintain operational efficiency.
Analytics and Reporting
a. Generates performance metrics and customizable dashboards for tracking automation outcomes.
b. Provides actionable insights to optimize processes and scale automation efforts.
Role-Based Access Control (RBAC)
a. Ensures secure and role-based access to Manager functionalities.
b. Enables granular permissions for different users, enhancing security and compliance.
Version Control
a. Maintains a history of deployed workflows, allowing easy updates or rollbacks when needed.
b. Supports managing multiple versions of automation processes.
API Integration
a. Offers robust APIs for integrating Robility Manager with third-party tools and custom applications.
b. Ensures seamless orchestration of automation workflows within broader enterprise systems.
Multi-Tenancy
a. Supports multiple tenants on the same platform, providing resource isolation and scalability.
b. Ideal for organizations with diverse departments or multiple client environments.
Deployment Options
a. Available as a cloud-based solution or on-premises deployment, tailored to meet business requirements.
b. Scalable to align with organizational growth and automation needs.
Customizable Workflows
a. Empowers users to define and customize workflows with ease, enhancing automation flexibility.
b. Promotes faster deployment of solutions that align with specific business processes.
1.1.1 Sign-In
To access Robility Manager, users must first receive an invitation to the platform. (Click here to refer) Once invited, they can sign in using one of two methods, depending on the identity provider chosen by their organization. Robility’s identity provider ensures secure authentication, providing seamless and protected access to the platform.
Using Username and password:
The username and password method is the initial and default sign-up process for all users, even when Azure SSO is selected. It is essential for account creation and identity verification within the platform.
1. Users can set up their own username and password to access Robility Manager.
2. This foundational step ensures a secure and seamless onboarding experience.
Using Azure AD authentication:
Following the initial sign-up with a username and password, users can log in using the Azure AD Single Sign-On (SSO) option if the organization has configured the setup with Azure. This ensures secure account creation and identity verification. Once set up, Azure AD SSO manages authentications for all future logins, providing seamless and secure access.
Click here to know how to setup with Azure AD authentication.
1.1.2 Tenancy
In Robility, tenants provide self-contained environments for centrally managing data, resources, users, and configurations, streamlining automation processes within a single platform. Organizations can create multiple tenants with the same structure to address specific business needs.
Who Can Create Multiple Tenants?
The organization admin has the privilege to add multiple tenants under their organization, but this depends on the chosen structure:
a. Multiple-organization, multiple-tenant structure
b. Single-organization, multiple-tenant structure
However, if the admin selects a single-organization, single-tenant structure, they will not be able to create or add additional tenants later. Click here for more details.
Who manages the tenant?
The Tenant Admin is responsible for centralized control, ensuring seamless operations and optimizing automation processes. The Tenant Admin can manage the following features:
1. User Management:
Admins can invite users, assign roles, and manage access rights to ensure appropriate permissions.
2. Configuring Projects
Admins can create and customize multiple projects to meet business needs, including defining scope and aligning resources.
3. Storage and Key Vaults
Admins can manage storage and key vault configurations to securely handle project data, ensuring reliable automation processes.
4. License Management
Admins can procure and manage licenses for Robility products and resources at the tenant level.
5. HarmonyAI Integration
Admins can configure HarmonyAI and integrate it into projects to enhance automation capabilities.
When will tenant expire?
Tenants with a 365-day or 90-day license package will expire at the end of their license period unless renewed. The organization administrator will receive an email notification five days before the license expiration, ensuring sufficient time to take necessary action. Click here for more details.
To avoid disruptions, timely renewal is essential.
Who can renew the license?
Both the organization administrator and the tenant administrator can renew the license. To ensure uninterrupted operations:
1. Navigate to the “License” page under the Settings menu in the Robility Manager platform.
2. Submit a request for a new license.
3. Review the remaining days of the current license, displayed for reference.
If license expiration affects products such as Robility Designer and Runner, these must also be reactivated. Click here for detailed guidance.
What happens after a tenant expires?
Failure to renew the license will result in:
a. Loss of access for all users and resources within the tenant.
b. Halted automation processes, including bot deployment.
To restore services, administrators should promptly request a license renewal. Follow the steps below to renew:
1. After logging in to the Robility platform, the tenant status will appear as Expired.
2. Click the Renewal button.
3. You will be redirected to the License Request page within the tenant and prompted to submit the renewal request.
4. Click Submit to complete the process.
1.2 Tenant Management
Tenant Management serves as the backbone of efficient automation in Robility. It simplifies operations, ensures secure access, and empowers tenant administrators to oversee all critical aspects of automation.
Key Functionalities for Tenant Administrators
Tenant administrators have the privilege to manage resources, users, and configurations effectively. The key functionalities include:
1. User Management
2. Project Creation and Management
3. Resource Allocation and Optimization
4. Templates and Marketplace Access
5. License Management
6. Feature and Product Updates
7. Key Vault and Storage configuration
8. IP Configuration and Security
9. Harmony AI Integration
1.2.1 User Management
User management is a centralized section for adding users, assigning roles, and managing access within the tenant. Only the tenant administrators have the privilege to access this section to modify the permissions of the users and ensures secure and efficient access control.
This section uses a Role-Based Access Control (RBAC) system, enabling users to have role-dependent capabilities in Robility Manager. The primary goals of the RBAC system ensure users have the appropriate level of access based on their roles, to streamline access management, and to enhance overall security. For detailed information on default roles and their permissions, click here.
Roles in the platform
Each role comes with predefined permissions that determine what users can access and modify within the platform. The roles are as follows,
1. Tenant Admin: This role has full administrative privileges across the platform, allowing users to configure settings, manage users, and access all platform features. Tenant Admins are responsible for overseeing the platform’s operations and ensuring that everything is set up according to the organization’s needs.
2. RPA Developer: RPA Developers is intended for users who are responsible for designing and deploying automation workflows with Designer and Runner.
3. User: The User role typically refers to standard users who interact with the platform without needing access to the administrative or any Robility products. These users can perform tasks assigned to them but have limited access in the platform.
1.2.2 Project Creation
Creating a Project
Each organization has unique automation needs. Based on these requirements, different projects are created, and robots are assigned accordingly. This customization ensures that each project receives the automation support it requires, tailored to the specific tasks and processes of the organization.
How to navigate to the projects?
1. Login to Robility AI™ using your credentials.
a. To learn how to sign up with Robility Manager, click here.
2. If you have access to only one tenant, upon logging in, you will be directed to the Home page of Robility Manager.
a. If you have access to multiple tenants, select the tenant to which you want to invite users.
3. On the left-hand side menu, click on the “Projects”.
4. Here we can view, manage and perform action of all the projects created under this tenant.
How to add a project?
1. Click on the “Add” from the right-hand side top corner.
2. An “Add project” screen will pop up to fill out the basic information about the project.
3. Fill in all the mandatory fields. Below is a detailed explanation of what each field desribes.
Default Settings
ProjectName: Indicates to specify the name for your project to start automation.
Project Code: Indicates to specify the “Code” for unique identification during the automation.
Project Description: Indicates to specify the description of what your automation project does.
Project Owner: Indicates to choose the active users to set as owner of the project.
Project Logo: Indicates to choose the “Logo” of your project.
Skin Color: Customize your project’s skin color with options available. By default, “Charcoal” will be selected.
Overview
1. Serial number: Shows the number of projects under this tenant.
2. Project Name: Shows the project name created by the client.
3. Description: Shows the description given against the specific project.
4. Robot Status: Shows a number and color code depending on the status of the robot inside a project.
a. Red: When the robot status shows red with a number, it means that those many numbers of robots are idle.
b. Green: When the robot status shows green with a number, it means that those many numbers of robots are running.
c. Yellow: When the robot status shows yellow with a number, it means that those many numbers of robots are in ToCheck.
d. No Color: When the robot status doesn’t have any number or color code to it, there are no robots assigned to that project.
5. Updated by: Displays the username who has updated the project recently.
6. Updated On: Shows the date in which the project was updated.
7. Action: There are two different actions that can be performed in a project.
a. Edit: Click on this to make any changes to the project.
b. Go: Click on this to get into the project’s command center where we can add the robots to be deployed to the machines.
What can be seen on the command center screen?
1. Dashboard: This screen overviews the status of all the bots under the project, number of machines utilized, and summary of the projects automated from “Interact.”
2. Roles and Users: This menu is used to invite users to the current project and assign different roles based on the work assigned to them.
3. InteractWorkflow: RobilityInteract’ s advanced features make it a powerful tool for businesses seeking to enhance their automation processes. Click here to get more information.
4. Workflow: This menu list downs the workflows published within the “Project” from Designer.
5. Credential Manager: This is useful for keeping the tools or applications credentials always secure. Click on it to configure and start to set up your vault credentials. To get more information, refer the documentation of Credential Manager.
6. DeployRobots: This menu allows the user to map and manage the “Robots” assigned inside the project.
7. License: This menu allows the “Project admin” to request more licenses required for the Project.
8. Scheduler: This menu allows the user to schedule and manage the bots and machines here.
1.2.3 Resources
Resources are the machines allocated for scheduling and executing automation robots. In Robility, the “Resources” menu on the tenant page serves as a centralized interface for managing these machines across all projects within the tenant.
This menu allows you to view, add, and manage resources, ensuring seamless allocation and utilization. When adding resources, you can choose from two types of licenses based on your automation needs.
Types of Licenses
There are two types of licenses available for automation:
1. Unattended Robots – Use this license when the bot operates without user intervention. Each machine can have only one unattended bot, which is ideal for automating repetitive, rule-based tasks that do not require supervision.
2. High-Density Bots – Suitable for machines with multiple users logged in simultaneously, without requiring user intervention. This functions similarly to unattended bots but supports multiple users on the same system.
Machine Provisioning at the Tenant Level
Users can provision machines at the tenant level rather than assigning them to individual projects, enabling centralized control and efficient resource allocation across multiple projects. The license key required to connect the Runner with Robility Manager on the provisioned machine will be managed at the tenant level, ensuring consistency and eliminating the need for repetitive configuration at the project level.
Multi-Project Machine Assignment
A single machine can be assigned to multiple projects without requiring the removal of resources, enabling flexible utilization across various automation workflows. However, if a machine is actively connected and executing a process in one project, it cannot be used concurrently in another project.
How to add a resource?
Let’s walk through the following steps to add a machine to the manager.
1. Login to RobilityAI Manager using your credentials.
2. Navigate to the “Resources” menu.
3. Click on “Add” from the top right corner to add a new machine.
4. Choose the license type from the license type drop down.
5. Fill in the other mandatory details and click on save.
Overview
1. Serial Number: Shows the number of machines added.
2. Resource: Shows the name of the machine added.
3. Username: Displays the username of the machine added.
4. Updated By: Shows the track of the person who has updated recently.
5. Status: Indicates the current status of the machine. There are three statuses:
a. Not Connected – The machine has been added but is yet to be provisioned.
b. Not Provisioned – The machine has been added, and the license is connected, but it has not yet been provisioned to any projects.
c. Provisioned – The machine has been added, the license is connected, and it has been successfully provisioned to one or more projects
6. Updated On: Shows the date and time when the machine was added to the manager.
7. License Key – Enables users to copy the license key for executing the bot in Runner. The license key will be enabled only when the machine is deployed in the project.
8. Action: There are two action buttons in the machine screen.
a. Manage: This option displays another set of action where it allows the user to perform the following,
i. Edit the password of the machine added.
ii. View and remove the projects provisioned when it is in “Idle” state.
iii. View all the information about the machine details.
b. Delete: This allows us to remove the machine from the manager.
Click here to learn more about adding the resource to the projects.
1.2.4 Templates
Templates
Templates act as reusable workflows that can be customized and deployed across your automation solutions within the tenant. These pre-built templates offer detailed outlines or processes of automation workflows, providing a structured framework for building specific automation solutions. They serve as starting point for various solutions, allowing users to easily integrate them into their workflows and are beneficial for performing repetitive tasks or actions efficiently.
How to publish the templates through Designer?
Once the template has been completed, the users can publish the templates in two different options. Private and Public.
To publish the templates privately, follow the below steps,
1. Save the template solution.
2. Navigate to the bottom of the Designer and click on the Publish option.
3. Choose the option as “Private (TenantName)”.
4. Now, under the home menu, go to the Publish option.
5. Mention the solution description and choose the release type either as Major, Minor or Bug.
6. Based on the release type the new version will change accordingly.
7. Enter the release notes for the template and click on Publish.
8. A success message will appear on the screen displaying that your template has been published.
When the user publishes the templates against the tenant’s name, it will be viewable and re-usable only to the users invited to the tenant.
After publishing the templates, it might take a few minutes to upload them to the cloud and to the tenant.
How to check updates, inactive and download the templates?
The published templates will be available in the RobilityManager at “Templates” menu. The templates that are published within the tenant can be accessed and re-used by the invited RPA developers in the tenant. can check if there are any updates available for the published templates in the Robility Manager.
1. Login to the Robility Manager.
2. Navigate to the Tenant where the published templates are available. (Only when published privately).
3. Select the “Templates” Menu.
4. Now, click on the “View” button under the “History” field.
a. This ‘View’ option provides a list of versions published for each specific template and allows the tenant admin to check for updates, setting inactive status for templates or download the templates.
1.2.5 MarketPlace
MarketPlace
MarketPlace is designed to be the go-to centralized hub for a meticulously curated collection of automation scripts and connectors, meticulously crafted to elevate and expedite your automation projects. Whether you are a seasoned automation professional or a newcomer looking to streamline your processes, MarketPlace offers a diverse array of tools and resources to meet your specific needs.
Our platform brings together a vibrant community of developers, engineers, and automation enthusiasts who contribute their expertise to create a dynamic ecosystem. Each script and connector undergo a rigorous vetting process to ensure quality, reliability, and security. This commitment to excellence ensures that users can confidently integrate these resources into their projects without compromising performance or stability.
Discover an extensive range of automation solutions, spanning various industries and applications. From IT and finance to healthcare and manufacturing, MarketPlace hosts a rich assortment of scripts tailored to address the unique challenges of different sectors. This diversity empowers users to find the perfect automation tools that align with their industry requirements.
The user-friendly interface of MarketPlace facilitates easy navigation, allowing users to quickly search, preview, and download scripts and connectors that suit their project objectives.
In addition to individual scripts and connectors, MarketPlace also features curated collections and bundles that address specific automation needs. These collections streamline the process of finding complementary resources, saving users time and effort in building comprehensive automation solutions.
As automation continues to play a pivotal role in transforming industries, MarketPlace stands as a beacon of innovation and collaboration.
How to download the listings?
All the scripts and solutions added in the Marketplace will be able to access in the Manager, empowering users with a rich library of pre-built components. This library includes integrations that facilitate seamless connections to external services, as well as custom activities, allowing users to incorporate specialized functionalities into their automation workflows.
Follow the below steps to download and integrate the scripts:
1. Launch the RobilityManager.
2. Navigate to the “MarketPlace”.
3. Here chose the specified template that is suitable for your solutions.
4. Here I am choosing the “OpenCV” specified as “Reusable component” and select the “Download” button.
a. Review the “Terms & Conditions” and then proceed to click on the “Agree” button.
b. Now, the listing will be downloaded in your local system, you can easily integrate the script in your automations.
1.2.6 Data Retention and Policy
Data Retention enables organizations to store project data for a defined duration to meet operational, compliance, regulatory, and audit requirements. Once the configured retention period expires, the system securely archives or permanently removes the data based on the defined policy, ensuring controlled and structured data lifecycle management.
Configuration & Management
The retention policy can be configured by the Tenant Administrator at the project level. Each project may have its own retention period based on business or regulatory needs.
Scope of the Policy
The data retention policy specifically governs the storage and retrieval of Interact workflow data only. It does not impact other components inside the Project.
Key Benefits
• Controlled Data Storage: Ensures project data is stored only for the required period.
• Compliance: Helps meet organizational, security, and audit requirements.
• Data Protection: Automatically removes outdated or unnecessary records to safeguard sensitive information.
• System Performance: Manages database size efficiently to maintain smooth operations.
Configuring Data Retention
Data retention settings are configured at the project level. Only users with the Tenant Admin role can manage these settings.
Steps to Enable and Configure:
1. Navigate to the Edit option for the project.
2. Enable the Data Retention option.
3. Configure the retention parameters by selecting values from:
a. Archival Days
b. Purge Days
Default Settings: Archival Days: 90 and Purge Days: 180
Archival Days
1. Defines the period during which data remains fully accessible for review, reporting, and workflow operations.
2. After the archival period ends, data moves to the purge phase.
3. Configurable values: 30, 60, or 90 days
Purge Days
1. Defines the duration after archival during which data is retained in a purged state before permanent deletion.
2. After this period, data is permanently deleted and cannot be recovered.
3. Configurable values: 120, 160, or 180 days
1.2.7 License Expiry Notification
The License Expiry Notification panel provides a consolidated view of licenses that have expired or are approaching their expiry date. Licenses are categorized into four groups:
a. Tenant
b. Designer
c. Resource
d. Machine Template
This centralized view enables administrators to efficiently monitor and manage license statuses across applications from a single location.
Administrators can directly navigate to the License Request and License Renewal pages to take appropriate action and ensure uninterrupted platform access.
Expiring Soon Criteria
A license is marked as Expiring Soon when it is within 7 days of its expiry date. Once the expiry date has passed, the license status is automatically updated to Expired.
Categories
| Category | Description |
|---|---|
| Tenant | Displays expired and expiring licenses associated with tenants. |
| Designer | Displays expired and expiring licenses associated with designer accounts. |
| Resource | Displays expired and expiring licenses associated with resources. |
| Machine Template | Displays expired and expiring licenses associated with machine templates. |
Each category displays a count badge indicating the number of licenses requiring attention.
Status Indicators
| Indicator | Status | Description |
|---|---|---|
| 🔴 Dark Red | Expired | The license expiry date has passed |
| 🟡 Amber | Expiring Soon | The license will expire within the next 7 days |
Closing the Panel
The panel can be closed using the × icon at the top-right or the Close button at the bottom-right.
1.2.8 Settings
Settings
RobilityManager provides real-time monitoring that helps to keep track of the health and state of the system. With the enhanced version, it’s easier to monitor and configure mails,
schedule jobs and have visibility over the logs of the system.
1.3 Project Management
Project Management in Robility Manager provides a structured management to creating, configuring, and managing automation projects within a tenant. It ensures that automation workflows are organized, resources are efficiently allocated, and access is properly controlled, enabling smooth execution and monitoring of automated processes.
Key Capabilities of Project Management:
1. Project Creation and Organization: Administrators and authorized users can create projects within the tenant, defining their scope and purpose. Projects serve as dedicated spaces for managing automation workflows, ensuring that related processes, resources, and configurations are grouped logically.
2. Resource Allocation: Users can assign resources such as bots and developers to specific projects, ensuring the right personnel and automation agents are linked to each initiative. Proper resource allocation helps streamline execution and optimize workload distribution.
3. Role-Based Access Control: Project Management allows administrators to define project-level roles and permissions, ensuring that users have appropriate access based on their responsibilities. This enhances security and governance by preventing unauthorized modifications to automation workflows.
4. Deploy Robots and Scheduler: Users can manage automation workflows by deploying them in the Robility Runner. The scheduler ensures that automated tasks run at predefined times, improving efficiency and reducing manual intervention.
5. Integration and Credential Management
Project Management facilitates seamless integration with various tools and platforms, including:
- Interact: To enable human-in-the-loop interactions within automated workflows.
- Credential Vault: For secure storage and retrieval of sensitive authentication details.
- App Integrations: To connect with external applications and services, expanding automation capabilities.
By bringing all these elements together, Project Management in Robility Manager ensures a structured, secure, and scalable automation environment. It fosters collaboration, governance, and efficiency, making it easier for enterprises to deploy and maintain automation solutions effectively.
1.3.1 Roles & Permissions
The roles and permissions in project level provides the users to perform actions within the specific project inside the tenant.
Roles:
1. ProjectAdmin
2. ProcessAdmin
3. InteractUser
4. Developer
5. CredentialAdmin
The below is the detailed documentation of each role and their permissions within the project. To learn more about the roles in the tenant, click here.
Project Admin
Users invited as “Project Admin ” are referred as the administrator of the specific project created and assigned to them. They will be granted access to manage project-level data.
Permissions:
1. Map and manage users in the project.
2. Add or remove resources as needed.
3. Schedule robots for automation tasks.
4. Request licenses for Runner (Unattended, Attended, Service account and High density).
5. Add, edit and manage credentials for applications.
6. Have overall control over the Interact menu.
a. Note that access to the Interact queues can be restricted to view and manage for this role.
7. Manage workflows published for projects.
The below table guides you with the permissions and actions assigned to the Project Admin.
| Pages | View | Add | Edit | Delete | Action |
|---|---|---|---|---|---|
|
Dashboard |
|
|
|
|
|
|
Roles & Users - Manage Users |
|
|
|
|
|
|
Roles & Users - Manage Roles |
|
|
|
|
|
|
Vault |
|
x |
|
|
|
|
Automation Ops |
|
|
|
|
|
|
License |
|
|
|
|
|
|
Schedule Robot |
|
|
|
|
|
|
Interact Workflow - Queues |
|
|
|
|
|
|
Interact Workflow - URN Management |
|
|
|
|
|
|
Interact Workflow - Reports |
|
|
|
|
|
|
Interact Workflow - Project Configuration |
|
|
|
|
|
|
Workflow |
|
|
|
|
|
|
App Integrations |
|
|
|
|
|
Process Admin
The process admin is assigned to users who are responsible for overseeing and managing the automation processes within the specific project. Users with this role have the below permissions,
Permissions:
1. Access, review, manage, and generate reports in the Interact menu for specific projects.
a. Access to the Interact queues can be restricted to viewing and managing for this role.
2. Access to view credentials for applications and can perform actions to deactivate, lock, and unlock credentials within the project.
3. Request licenses for additional Runner required for project.
4. Add the resource, schedule and manage robots for automation processes within the project.
5. Monitor the status of deployed robots in real-time.
The below table guides you with the permissions and actions assigned to the Process Admin with each module.
| Pages | View | Add | Edit | Delete | Action |
|---|---|---|---|---|---|
|
Dashboard |
|
NA |
NA |
NA |
|
|
Roles & Users - Manage Users |
x |
NA |
NA |
NA |
NA |
|
Roles & Users - Manage Roles |
x |
NA |
NA |
NA |
NA |
|
Vault |
|
x |
x |
x |
|
|
Automation Ops |
|
|
|
|
|
|
License |
|
|
NA |
NA |
NA |
|
Schedule Robot |
|
|
|
|
|
|
Interact Workflow - Queues |
|
|
|
NA |
NA |
|
Interact Workflow - URN Management |
|
|
|
NA |
NA |
|
Interact Workflow - Reports |
|
|
|
NA |
NA |
|
Interact Workflow - Project Configuration |
x |
NA |
NA |
NA |
NA |
|
Workflow |
x |
NA |
NA |
NA |
NA |
|
App Integrations |
|
|
|
|
|
Interact User
The Interact User role is assigned to users who are responsible for viewing and managing cases in the assigned Interact queues. The permissions associated with this role are listed below:
Permissions:
1. Access the dashboard for project monitoring.
2. Monitor transactions on the Interact page for the assigned queues.
3. Review transaction details, and perform actions such as back-pushing, unlocking, and viewing the history of transactions within Interact
The below table guides you with the permissions and actions assigned to the Interact User with each module.
| Pages | View | Add | Edit | Delete | Action |
|---|---|---|---|---|---|
|
Dashboard |
|
NA |
NA |
NA |
|
|
Roles & Users - Manage Users |
x |
NA |
NA |
NA |
NA |
|
Roles & Users - Manage Roles |
x |
NA |
NA |
NA |
NA |
|
Vault |
x |
NA |
NA |
NA |
NA |
|
Automation Ops |
x |
NA |
NA |
NA |
NA |
|
License |
x |
NA |
NA |
NA |
NA |
|
Schedule Robot |
x |
NA |
NA |
NA |
NA |
|
Interact Workflow - Queues |
|
|
|
NA |
|
|
Interact Workflow - URN Management |
x |
NA |
NA |
NA |
NA |
|
Interact Workflow - Reports |
x |
NA |
NA |
NA |
NA |
|
Interact Workflow - Project Configuration |
x |
NA |
NA |
NA |
NA |
|
Workflow |
x |
NA |
NA |
NA |
NA |
|
App Integrations |
|
|
|
|
|
Developer
This role is responsible for developing, maintaining and deploying automation workflows, ensuring their seamless integration with Interact, the credential vault, and App Integrations within the specific project. Below are the permissions,
Permissions:
1. Access the dashboard for project and robot monitoring in real time.
2. View credentials for applications and perform actions to deactivate, lock, and unlock credentials within the project.
3. Have overall access to the Interact menu.
4. View and perform actions such as inactivating and downloading published workflows.
5. Has privilege to schedule robots for automation.
6. View and perform actions such as start and stop the deployed robots within the project.
The below table guides you with the permissions and actions assigned to the Developer with each module.
| Pages | View | Add | Edit | Delete | Action |
|---|---|---|---|---|---|
|
Dashboard |
|
NA |
NA |
NA |
NA |
|
Roles & Users - Manage Users |
x |
NA |
NA |
NA |
NA |
|
Roles & Users - Manage Roles |
x |
NA |
NA |
NA |
NA |
|
Vault |
|
x |
x |
x |
|
|
Automation Ops |
|
x |
x |
x |
|
|
License |
|
NA |
NA |
NA |
x |
|
Schedule Robot |
|
|
|
|
|
|
Interact Workflow - Queues |
|
|
|
NA |
|
|
Interact Workflow - URN Management |
|
|
|
NA |
|
|
Interact Workflow - Reports |
|
|
|
NA |
|
|
Interact Workflow - Project Configuration |
|
|
|
NA |
|
|
Workflow |
|
NA |
NA |
NA |
|
|
App Integrations |
|
|
|
|
|
Credential Admin
This role will have access to manage application credentials utilized by robots. These users are entrusted with the critical responsibility of overseeing and managing application credentials used by robots in the system. Below are the permissions entitled with,
Permissions:
1.Access the dashboard for project and robot monitoring in real time.
2. Manage application credentials utilized by robots.
3. Create, modify, and delete credentials within the role of Credential Admin.
The below table guides you with the permissions and actions assigned to the Credential Admin with each module.
| Pages | View | Add | Edit | Delete | Action |
|---|---|---|---|---|---|
|
Dashboard |
|
NA |
NA |
NA |
NA |
|
Roles & Users - Manage Users |
x |
NA |
NA |
NA |
NA |
|
Roles & Users - Manage Roles |
x |
NA |
NA |
NA |
NA |
|
Vault |
|
|
|
|
|
|
Automation Ops |
x |
NA |
NA |
NA |
NA |
|
License |
x |
NA |
NA |
NA |
NA |
|
Schedule Robot |
x |
NA |
NA |
NA |
NA |
|
Interact Workflow - Queues |
x |
NA |
NA |
NA |
NA |
|
Interact Workflow - URN Management |
x |
NA |
NA |
NA |
NA |
|
Interact Workflow - Reports |
x |
NA |
NA |
NA |
NA |
|
Interact Workflow - Project Configuration |
x |
NA |
NA |
NA |
NA |
|
Workflow |
x |
NA |
NA |
NA |
NA |
|
App Integrations |
|
|
|
|
|
1.3.2 Workflows
Workflows are automation solutions created, configured, and published through Robility Designer. They represent the backbone of Robility’s automation ecosystem, defining the logic, sequence, and execution flow of automated processes. Once published, workflows are deployed to this section, which serves as a centralized command center for managing, organizing, and overseeing all operational automations within the enterprise.
This section enables users to maintain complete visibility and control over every deployed automation, ensuring that business processes run seamlessly, efficiently, and with minimal manual intervention.
Key Capabilities
1. View and Organize Workflows: Browse and filter workflows by projects.
2. View Workflow History: Access a complete historical record of workflow published status.
3. Manage Versions: Every workflow version is recorded, allowing users to:
a. Audit prior versions
b. Compare logic changes
c. Roll back if an update causes execution issue
d. Publish enhancements safely
Version control ensures continuity and controlled evolution of automations.
4. Security Scan Status: View automated security scan results to ensure workflows follow secure coding standards and do not introduce vulnerabilities. This helps maintain enterprise-grade compliance and trust.
5. Workflow Analyzer Report: Access analyzer reports generated during workflow build and publish cycles. These reports highlight best-practice deviations, performance issues, and optimization recommendations—helping designers improve workflow quality and reliability.
Click here to learn more about how to publish workflows.
Explanation of Tags on the Workflow Screen
1. Serial Number: Displays the count of workflows published, helping users identify and organize the sequence of solutions efficiently.
2. Solution Name Lists the name of each published solution, enabling users to easily recognize and differentiate between workflows.
3. Latest Version: Indicates the most recently published version associated with each solution, ensuring users can access the latest updates and modifications.
4. File Size (MB): Shows the size of the most recently published file, providing an overview of storage requirements for each solution.
5. Updated By: Tracks and displays the name of the person who last updated the resource. This tag reflects changes made by the resource itself or by an individual, ensuring accountability.
6. Updated On: Records the date and time when the resource was last updated. Similar to “Updated By,” this tag captures both manual updates and changes initiated by the resource.
7. Publish Status: Displays the current status of the published solution, offering visibility into whether the workflow is active, inactive, or under review.
8. History: Provides detailed tracking of workflow-related actions, enabling users to monitor and manage workflows effectively. The following options are included:
a. Inactive: Allows users to mark a specific version of the solution as inactive, preventing further use while retaining version history.
b. Download: Enables users to download the workflow.
9. Scanned Status: Provides the status of the security scan of the solution.
How to Inactive and download the workflows?
1. Login to the “RobilityManager” portal.
2. Select the “Tenant” against which the “Project” has been configured and navigate to it.
3. Select the “Workflows” from the Menu.
4. Choose the respective “workflows” and click on the “view” option.
a. Here choose the “Inactive” or “Download” option against the version number.
1.3.3 Credential Vault
The Robility Credential Vault is a secure feature designed to store and manage sensitive information such as credentials, API keys, and confidential data within the Robility platform. It ensures secure access to secrets during automation workflows, minimizing exposure risks.
By default, the Credential storage is set to “Robility Manager Instance”. This option can be configured in the tenant selection area. Click here to learn more about it. This step is crucial for the tenant admin because all credentials will be stored in the area based on the storage configuration.
Click here to view where all the credentials configured in Robility Manager are stored.
How the Credential Vault is Secured
1. Tenant Isolation: Credentials for each tenant are stored in isolated databases that are physically separate and hosted in Azure SQL Managed Instances (Azure SQL MI). These databases are protected with Transparent Data Encryption (TDE) to secure data at rest, ensuring tenant-specific security.
2. Encryption Mechanism: AES-256 Encryption: The Robility Credential Vault employs AES (Advanced Encryption Standard) with a 256-bit key to encrypt sensitive data. This industry-leading encryption ensures robust security for stored secrets. Encryption keys are securely managed and stored within the Robility infrastructure.
3. Secure Communication: All communication between Robility components, such as bots, the Credential Vault, and the Robility Manager, is secured using TLS 1.2 (Transport Layer Security), safeguarding data in transit.
4. Role-Based Access Control (RBAC): Robility enforces strict role-based access controls, ensuring that only authorized users and processes can access or modify stored credentials.
5. Audit Logs: Credential Vault activities, such as storing, retrieving, or modifying credentials, are logged to support audit and compliance requirements.
Third Party Vault Integration
Robility integrates seamlessly with external credential management systems, allowing organizations to leverage existing solutions for secure credential storage and retrieval.
Supported Third-Party Vaults:
Azure Key Vault: Allows secure storage and management of credentials using Azure’s encryption and policy controls.
Aws: Provides secure storage, automatic rotation, and fine-grained access control for secrets, ensuring safe integration with AWS services and applications.
Google: Enables secure storage and access management of API keys, passwords, and other sensitive data, integrated with Google Cloud’s IAM and audit logging.
Click here to configure third party vault integrations.
Advantages
1. Enhanced Security: Implements advanced encryption and access controls to protect sensitive data.
2. Centralized Management: Streamlines credential management by centralizing sensitive information storage.
3. Zero Trust Enforcement: Access is strictly granted only to authenticated users or bots with appropriate permissions, aligning with Zero Trust security principles.
4. Flexible Infrastructure Options: Works with both Robility Manager’s instance vault and external third-party vaults, allowing organizations to choose based on their infrastructure preferences.
5. Auditability and Compliance: Tracks and logs credential access to meet compliance requirements such as GDPR, ISO 27001, and HIPAA.
Click here to learn more about the best practices while configuring credentials.
1.3.4 Automation Ops
The “Automation Ops” menu is designed to streamline workflow automation within a project. It provides users with the ability to view, manage, and assign workflows to machines, ensuring seamless execution of automated processes.
Located at the Project level, this menu grants the Project Admin or Process Admin the authority to configure automation deployment. This section helps maintain operational control while optimizing task execution within the project.
Pre-requisites
Below are the points to note before deploying the machines to the robots.
1. The resource must be added to the Tenant to map it to the respective project. If you haven’t added the license yet, click here.
2. Adequate licenses must be available to deploy them.
3. You cannot map the deployed machine to another solution.
4. The machine must be idle and not in use in order to map it to another solution.
Once you have added the machine in the “Resources” inside the tenant and published the automation solution within the respective project, you are all set to deploy them. To learn about adding resources to your tenant, click here.
Steps to Add Resources to a Project
1. Navigate to the respective project within your tenant.
2. In the “Automation Ops” section, click the “Add” button.
3. Ensure that workflows are published to the project before deploying resources.
4. Select the license type as “Unattended Robot.”
5. Choose the available resource name for the tenant, then select the workflow you wish to deploy.
6. You can select the version number to be deployed. This will display details such as the description, published by, published date, and any release notes provided during publishing.
7. Once the workflow version is selected, the Resolution Settings will be automatically populated based on your published solution’s JSON. Click here to learn more about it.
8. Finally, click the “Save” button.
What does each of the tag in the Automation Ops screen mean?
1. Serial number– Shows the count of the number of machines added.
2. MachineName – The name of the machine to which the robot is assigned is seen here.
3. LicenseType – Displays the type of license (Unattended Robot or Attended Robot) associated with the resource.
4. Solution – Shows the name of the solution assigned to the machine. This corresponds to the solution published and deployed from the Designer.
5. Version – Displays the version number of the solution assigned to the robot.
6. Domain User – The domain and the username for the robot is seen here.
7. Status– The robot has different status based on its execution in runner. Click here to view the status in detail.
8. Updatedby – Displays the name of the user or resource that last updated the resource. This field is also updated when the resource itself performs an action.
9. UpdatedOn – Shows the date and time of the most recent update to the resource. This timestamp is also refreshed when the resource performs an action.
10. Action – There are four different actions that we can use from the runner which are run, stop, edit and remove.
a. Run – This initiates the bot in the runner.
b. Stop – To stop the workflow during execution. This requires a stop activity to be used in the workflow.
c. Edit – To edit the workflow details assigned to the machine.
d. Remove – To remove the machine from the project.
Removing the machine
When a machine is in a Locked or Running state, you cannot remove it from the Automation Ops page.
If the machine is linked to a scheduler, attempting to remove it from the Automation Ops will display a notification:
“The machine is being used by the scheduler. Do you want to remove it?”
a. If you click Yes, the machine along with the associated scheduler will be removed.
b. This happens only when a single machine is assigned to the scheduler.
c. If multiple machines are assigned to the same scheduler, the scheduler will remain active and only the selected machine will be removed.
1.3.5 Scheduler
The Scheduler menu streamlines processes between robots and humans without manual intervention. It enables scheduling of automation workflows at regular intervals, facilitating efficient management and real-time monitoring of robot execution in RobilityManager. This automation of scheduling tasks reduces human error and ensures timely execution of critical processes. By setting up scheduled triggers, you can automate repetitive tasks, manage resources efficiently, and monitor workflow progress seamlessly.
Schedulers are essential in automation for several reasons:
1. Efficiency: Schedulers automate repetitive tasks, ensuring they are executed at predefined intervals without manual intervention. This improves overall process efficiency.
2. Resource Optimization: By scheduling tasks, you can allocate resources more effectively, ensuring that critical processes are executed when needed without overburdening systems during peak times.
3. Timely Execution: Scheduled tasks ensure that important processes are executed at the right time, reducing delays and improving overall workflow timelines.
4. Error Reduction: Automation through schedulers reduces human errors that can occur during manual execution, leading to more accurate and reliable results.
5. Real-Time Monitoring: Many schedulers provide real-time monitoring capabilities, allowing you to track task progress, identify issues promptly, and take corrective actions as needed.
6. Productivity: By automating routine tasks, schedulers free up time for employees to focus on more strategic and value-added activities, boosting overall productivity.
Within Robility Manager, the scheduler is a vital tool used to organize bot deployment using five distinct scheduling methods.
1. Daily Schedulers
2. Daily Multiple Schedulers
3. Weekly Schedulers
4. Weekly Multiple Schedulers
5. Monthly Schedulers
Scheduler Essentials
Let’s delve deeper into each type of scheduler to grasp how they operate within the automation framework.
Before proceeding with scheduling robots, it’s crucial to adhere to and maintain the following steps:
1. Publishing Solutions: Begin by publishing the solutions to the project in RobilityManager. This step ensures that the latest versions of your automation workflows are available for scheduling. You can find detailed instructions on how to publish solutions here.
2. Resource Allocation: Next, add the necessary resources with their respective licenses. This step ensures that the correct resources are available for executing the scheduled tasks. Refer to the documentation here for guidance on adding resources.
3. Resource Configuration: Finally, configure the resources inside the project to define their roles and permissions. This configuration step ensures that resources are utilized efficiently and securely during automation execution. Refer to the guide here for detailed instructions on resource configuration.
How to navigate to the scheduler section?
Once you have followed and configured the above three steps, you can navigate to the Scheduler section to schedule and deploy your robots on a timely basis.
1. Login to Robility manager.
2. Click on Projects from the left side menu bar and navigate to the respective project.
3. Now, click on scheduler from the left side menu bar.
4. Now we can see the different types of schedulers available on this screen.
1.3.6 App Integrations
About
Robility’s App Integrations empower users to connect with third-party applications, seamlessly incorporating their services into automation workflows. Using API processes with secure authentication, Robility offers centralized control and customization for managing integrated systems. With a wide range of pre-built connectors for enterprise applications, Robility ensures quick and efficient automation, while also allowing for custom integration options to fit to unique business needs.
How does it help you?
1. Ensures secure and compliant data exchange between systems through robust authentication and encryption protocols, maintaining a higher level of compliance and governance through a standardized approach.
2. Simplifies the integration of a wide range of third-party applications to extend the functionality of your automation workflows.
3. Provides a unified environment for managing integrations, making it easier to maintain, troubleshoot, and update connections.
4. Access the ready-to-use library of connectors to streamline your automation processes.
5. Ensures a consistent automation design experience across all Robility products.
6. Built on a cloud-native platform, enabling businesses to scale integrations and automation rapidly without worrying about infrastructure limitations.
Why Use App Integrations Over API Activities?
1. App Integrations streamline the process by offering pre-configured connectors, reducing the complexity of setting up API calls and handling authentication or data parsing manually.
2. App Integrations are often more scalable and easier to maintain. Changes in API endpoints or authentication can be managed centrally, preventing the need for modifications across numerous workflows.
3. You can easily reuse the same integration setup across multiple workflows, avoiding the need to re-implement API connection logic each time.
Click here to learn about the connectors.
1.4 HarmonyAI
About
Harmony AI, the AI component of Robility, powers a comprehensive range of AI-driven automation capabilities designed to enhance workflow efficiency and intelligence. It offers prebuilt and custom AI models for tasks such as document processing, text analysis, and image recognition. With features like Document Intelligence, Harmony AI combines OCR and machine learning to accurately extract data from unstructured documents, while its Natural Language Processing (NLP) capabilities enable sentiment analysis, entity extraction, and text classification. Additionally, Harmony AI’s UI Vision allows for seamless recognition of UI elements in diverse environments, and its Generative AI integrations provide advanced text generation, summarization, and language translation features.
Harmony AI also integrates effortlessly with popular AI platforms such as Google AI, AWS, and Microsoft Azure, enabling organizations to leverage advanced machine learning capabilities within their automation workflows. AI-powered chatbots, voice and speech analysis, and seamless integration with third-party AI services, Harmony AI drives intelligent automation across industries such as healthcare, finance, and customer service, making Robility a leading solution for AI-powered automation.
Note
The feature is currently in preview mode. Click here to learn more about preview release.
HarmonyAI’s Capabilities
UI Vision: Revolutionizing UI Interaction
Harmony AI’s UI Vision is a cutting-edge, vision-driven capability that effortlessly transforms UI screens into structured, actionable elements. This breakthrough empowers Robility robots to navigate and interact with UI layers more intelligently and efficiently. By enabling seamless engagement with complex UI components, Harmony AI’s UI Vision can identify tables, icons, button, labels and text boxes. Click here to learn more.
Generative AI Activities: Transforming Automation with Intelligence
Harmony Generative AI Activities empower businesses to leverage artificial intelligence within their automation workflows. By offering key capabilities such as email generation, PII detection, content summarization, and text translation, these features enhance robotic efficiency, enable human-like informed decision-making, and unlock new automation opportunities. Click here to learn more.
Document Intelligence: AI-Driven Document Processing
Harmony Document Intelligence utilizes AI and machine learning to extract, interpret, and process data from structured and unstructured documents. It enhances accuracy and efficiency by automating data entry and validation tasks. With customizable features, it streamlines business workflows and reduces manual effort. Its seamless integration with the Robility Interact platform enables comprehensive automation. Empower your organization with intelligent document processing for greater operational efficiency.
AI Search: Revolutionizing Information Retrieval
Harmony AI Search enables robots and humans to efficiently locate information within documents, transactions, and audio files ingested through automation or manual input. It provides powerful features such as natural language search, field-based filtering, and context-driven retrieval for accurate results. Leveraging AI-driven insights enhances accessibility and speeds up information retrieval. Seamlessly integrated into automation workflows, it boosts productivity and informed decision-making.
1.4.1 Autonomous Agent AI
Understanding Autonomous Agent AI and Robility’s Harmony AI Support
Autonomous Agent AI refers to an advanced artificial intelligence system capable of functioning independently without the need for constant human supervision. These intelligent agents are designed to perceive their surroundings, analyze situations, and make informed decisions to achieve specific objectives. By operating autonomously, they can streamline processes and improve efficiency across various industries.
Key Characteristics of Autonomous Agent AI
1. Perception: Autonomous agents have the capability to gather and interpret data from their environment through various sources such as sensors, APIs, and other input mechanisms. This allows them to understand their surroundings and respond accordingly.
2. Decision-Making: Equipped with sophisticated AI models, rules, and heuristics, these agents can analyze information and make decisions that align with predefined goals. They can evaluate different options and take the most suitable course of action.
3. Autonomy: A defining feature of Autonomous Agent AI is its ability to function without direct human oversight. Once programmed with specific objectives, these agents can adapt and respond to changing conditions on their own.
4. Goal-Oriented Behavior: Autonomous agents work with a clear purpose, striving to accomplish specific tasks efficiently and effectively. Whether the goals are pre-defined or dynamically adjusted, these agents stay focused on achieving the desired outcomes.
5. Interaction: These AI systems are capable of communicating with humans, other AI agents, or external systems. This interaction enables seamless coordination, collaboration, and execution of tasks in complex environments.
1.4.2 Harmony AI Privacy Layer
Harmony AI Privacy Layer is an advanced solution designed to empower enterprises with comprehensive control over the utilization of AI models by users, automation bots, and various components within the Robility ecosystem. This privacy-focused layer provides a robust framework that ensures compliance, security, and governance while enabling organizations to tailor AI interactions to their specific business needs.
The Harmony AI Privacy Layer offers a wide range of configurable settings that allow administrators to manage AI model integrations at multiple levels, including tenant-wide and project-specific configurations. This flexibility enables organizations to dictate which AI models can be utilized across different projects, ensuring alignment with their security policies and operational requirements.
Key capabilities of the Harmony AI Privacy Layer
1. Granular AI Model Integration Control: Administrators can define which AI models are permitted within the organization, ensuring adherence to internal policies and regulatory requirements. The layer supports integration with a variety of AI models, including custom and third-party solutions. Click here to learn more.
2. Personally Identifiable Information (PII) Filtering: The privacy layer incorporates advanced mechanisms to detect and mask PII, such as names, addresses, and financial details, ensuring compliance with data protection regulations like GDPR, HIPAA, and CCPA. Customizable filtering rules allow organizations to define what constitutes sensitive information based on their compliance needs.
3. Abusive Content Prevention: To maintain a safe and professional environment, the Harmony AI Privacy Layer includes content moderation features that identify and prevent the generation of abusive, offensive, or inappropriate content. This functionality helps organizations enforce ethical AI usage policies and maintain brand integrity.
4. Role-Based Access Control (RBAC): Enterprises can enforce strict access controls by assigning AI usage permissions based on user roles and responsibilities. This ensures that only authorized users, robots, and components can access AI functionalities as per defined policies.
5. Audit and Monitoring Capabilities: The layer includes comprehensive logging and monitoring tools that track AI interactions, providing insights into how AI models are being utilized across projects. Detailed audit logs support compliance audits and help identify any potential misuse or anomalies.
With these features, the Harmony AI Privacy Layer ensures that enterprises can confidently deploy AI solutions within the Robility platform, balancing innovation with robust security and compliance measures.
1.4.3 Integrations
Robility® offers a comprehensive suite of AI services and built-in open-source models that can be seamlessly integrated into automation workflows. These services empower users to enhance the intelligence and efficiency of their automations by enabling them to process unstructured data, understand human input, and make informed decisions within workflows.
The AI services are tailored to handle routine yet data-intensive tasks such as extracting key fields from documents, analyzing customer sentiments from text inputs, identifying and validating signatures, and recognizing both printed and handwritten text formats. These capabilities significantly reduce manual effort, improve data accuracy, and accelerate processing times across various business operations.
Robility’s AI services are created using trusted open-source tools, which are then improved with custom-built models to make them work better for specific tasks. These services are designed to understand complicated data, filter inappropriate content, pull out useful information from text, and create human-like responses. All of this happens automatically as part of the automation process. Whether you use Robility’s built-in AI tools or connect with other AI services, these features help make your automation smarter and more adaptable to different situations.
Available AI Services Powered by Robility:
1. Generative AI – Create dynamic text content or responses using AI-based natural language generation. To learn more about the activities, click here.
2. OCR & ICR – Extract printed (OCR) and handwritten (ICR) text from documents, forms, and images.
3. Sentiment Analysis – Understand the emotional tone of customer feedback, reviews, or support queries.
4. Entity Extraction – Identify and extract structured information such as names, dates, and locations from unstructured text.
5. Text Moderation – Detect and filter out inappropriate or harmful language from content inputs.
These AI capabilities bring intelligence to your automation journey, helping businesses respond faster, work smarter, and scale efficiently.
Third Party integrations
HarmonyAI also provide AI integration with third parties such as Azure and Google to further extend our capabilities and enhance document automation.
Azure Integration
Azure AI in Robility offers a wide range of models and services designed to cater to different AI and ML needs. These models and services are accessible through Azure’s cloud platform and can be used for tasks such as computer vision, natural language processing, anomaly detection, and more.
You can now easily plug Azure AI models into your automation workflow to enhance solutions.
AI services in Azure:
1. Document Understanding
2. Azure OpenAI
3. OCR
Google Integration
Google’s advanced AI and machine learning models leverages to improve document processing and automation. By incorporating Google’s Gemini and Vertex AI capabilities, users can achieve more accurate data extraction, better natural language understanding, and seamless integration with other Google services.
AI services in Google:
1. Document Understanding
2. Vertex AI
Click here to know how to activate the HarmonyAI within your tenant.
1.4.4 Settings
This section enables tenant administrators to configure and activate HarmonyAI for their projects, offering step-by-step instructions for setup. It also provides a comprehensive overview of the AI agent, its features, and the use cases.
1.5 Interact Workflow
About Interact
Interact is Robility workflow platform empowering human in the loop automation model. We manage interactions between robots and humans seamlessly.
Use cases
1. Human-in-the-Loop: In scenarios where automation processes require human intervention at specific stages for decision-making, the interaction could occur between robot-human-robot, robot-robot-human, human-robot, or robot-human ecosystems.
2. Integration of Disparate Applications: When integrating multiple disconnected applications into a unified system, Interact can be used to bridge the gap.
Example: Interacting with CRM, ERP, and ticketing systems simultaneously, allowing humans and robots to exchange data across these platforms in real time.
3. Hybrid Automation: In scenarios where the robot completes its execution and requires human intervention to provide relevant data, such as follow-up scheduling or ticket creation.
4. Report Generation Automation: Automation processes that require report generation to review, monitor, and analyze the process and inputs received from the robot.
5. Handling exceptions: For processes where automation encounters exceptions, Robility Interact enables users to handle exceptions and resume automation after reviewing the cases.
a. Example: A robot detects an issue in a data entry process, flags it for human review, moves it to either the system or business exception queue, and resumes the next step once the human verifies.
Limitations
DataTable and Attachment field types are not supported when uploading Queue transactions through Bulk Upload.
Key Features of Robility Interact
Robility Interact simplifies the automation process by offering a wide range of powerful features. Below are some highlights:
Fields:
Fields refer to individual pieces of data passed by robots and humans within the automation workflow. These fields represent the core information used in Interact to display, process, or retrieve data values. They can vary in type and purpose, depending on the specific requirements of the automation. In Interact, there are 16 types of fields that can be utilized for passing or retrieving data. This is the first step where the field description, purpose, and value types are defined and managed by both humans and robots.
For detailed information on field types, click here.
Queues:
Queues define the sequence in which the configured fields are processed. Robility Interact provides six distinct queue types, each serving a specific purpose within the automation flow:
- Processing – Manages indexing, fetching, and processing of data.
- HarmonyAI – Facilitates the integration of HarmonyAI into your automation workflows.
- Business Exception – Handles data when it encounters business-related exceptions.
- System Exception – Processes data that encounters system-level exceptions.
- Rejected – Manages data that is rejected due to specific errors or exceptions.
- Completed – Used when all processes related to the data are successfully finished.
The queue system allows users to control the flow of data from one queue to another seamlessly, ensuring efficient processing. For detailed information on queues, click here.
Business Rules:
Robility Interact includes a comprehensive yet easy-to-use rule engine that controls the movement of fields and queues based on If/Else conditions. This helps to streamline decision-making in the automation process, ensuring that data is processed correctly and efficiently based on predefined conditions.
For detailed information on configuring business rules, click here.
Email Configuration:
Interact also allows for the setup of automated email notifications, keeping users informed of queue movements and changes throughout the process. This feature ensures smooth communication and transparency during automation workflows. Click here to learn more.
Master Data:
The Master Data Configuration feature enables the storage and management of standardized inputs for recurring processing over a defined period. This ensures consistency and efficiency when dealing with common data sets used across multiple automation tasks. Click here to learn more.
1.5.1 Project Configuration
Project Configuration
Robility Interact offers a robust framework to manage automation workflows effectively by integrating robots and human operators. To get started, it’s crucial to configure key components such as fields, queues, and business rules. These configurations ensure a streamlined and structured process, providing clarity and consistency throughout the automation lifecycle.
Why is it essential?
1. Establishes a seamless interaction between automated processes and human intervention.
2. Reduces errors by setting clear parameters and rules for task execution.
3. Enhances efficiency by organizing workflows into well-defined structures.
4. Ensures consistent data handling and process standardization across tasks.
Key components
1. Field Configuration: Fields are the building blocks of your project setup, capturing data required for workflows. Proper field configuration ensures accurate data collection, storage, and usage in automation processes. Click here to learn more about field configuration.
- Define input fields such as text, numbers, or dropdowns based on the project requirements.
- Map fields to specific tasks to ensure robots and users interact with data correctly.
- Customize field properties to align with business needs, such as mandatory fields, default values, or validation rules.
2. Queue Configuration: Queues help in organizing tasks and managing workloads efficiently. They act as repositories for tasks awaiting processing, ensuring prioritization and orderliness. Click here to learn more about queue configuration.
- Define queues based on task categories or process stages.
- Assign robots to specific queues for automated task execution.
- Monitor and manage queue statuses to track task progress in real-time.
3. Business Rules: Business rules define the logic and decision-making criteria for your workflows. By establishing these rules, you can ensure that tasks follow a structured path with minimal manual intervention. Click here to learn more about business rules.
- Configure rules to handle task routing, prioritization, or exception handling.
- Integrate conditions and triggers to automate decision-making processes.
- Use rules to guide both robots and human operators in their respective roles.
4. Email Notifications: Email notifications play a vital role in keeping stakeholders informed about workflow activities and task statuses. Configuring notifications ensures timely communication and accountability. Click here to learn more about email notification.
- Set up automated alerts for task assignments, completions, or delays.
- Customize email templates to include relevant details such as task IDs, deadlines, or instructions.
- Enable notifications for exceptions or errors to ensure quick resolution.
5. Master Data: Master data serves as the foundation for maintaining consistency and accuracy across workflows. It provides a centralized repository for essential data used in automation tasks. Click here to learn more about Master data.
- Define and store key datasets, such as user roles, product information, or system parameters.
- Ensure data integrity by standardizing formats and avoiding duplication.
- Use master data to streamline task inputs and outputs, reducing manual dependencies.
1.5.2 Field Configuration
Fields are the foundational components of your project setup, serving as the primary means of capturing the data necessary for workflows. Proper configuration of these fields ensures the accuracy and reliability of data collection, storage, and usage, forming a critical part of seamless automation processes. Click here to learn more about field configuration.
1.5.3 Queue Configuration
Queue Configuration
The queue configuration helps the user to set up and manage queues. Queues are used to store and manage items fields, often in a First-In-First-Out (FIFO) order, for processing by robots. It can be customized to meet the needs of the user, such as setting different priorities, limits, and expiration times for different types of work items.
Proper queue configuration and management are essential for orchestrating complex processes efficiently and ensuring that your robots work seamlessly.
How to configure queues for your project?
The users will be able to configure the queues after fields has been set up. Follow the below documentation to walk through the Queue configuration page.
Queue Types
There are 6 queue types in which the fields are configured to set rules. Each queue type has its own set of parameters and rules that can be configured. This makes it easier to manage workload and keep the robots running smoothly. Additionally, queues can be used to manage exceptions and errors, ensuring that any issues that arise are handled quickly and efficiently.
Use Case
The following illustration helps you to understand how to configure queues against the project.
In this scenario, the input will consist of an Excel file containing a list of OS details. Using the information provided, including the OS type, RAM, HDD, and Applications, the server is to be created. Once the server creation process, specific to the relevant OS, is completed, it must be recorded back into the Excel file. The fields and queues can be established according to our specific use case. Here we are continuing the process from field configuration step.
Now let’s configure the queues:
The following steps helps you to set up the queues in your project. In our specific use case, 6 queues need to be created and configured.
Queue 1 – Processing:
The processing queue enables the transactions to move into process for execution of the automation. The fields that need to be processed can be configured. Let’s see how this works. After setting up the fields, they need to be managed with rules during the automation process. This processing queue will move the transactions into the execution process to initiate the automation. Follow the below steps to create a queue name for processing queue.
1. Select the project in which you want to configure the Interact. Here chooses the project as “Server creation”.
2. Navigate to the “Smart Interact” at the left-hand side of the page.
3. You will be directed to the project configuration page.
4. Select the queue configuration step.
5. Choose the queue type as “Processing” from the drop-down list.
6. Enter the queue name as “FetchData”.
7. Select the “Click here” option on the queue access to provide the access to the users available in the project. (Refer queue access to know more).
8. Select the “Click here” option on the field Access to configure the fields to process. (Refer field access to know more).
9. Select the regex script and add script against the field name. (Refer custom scripts to get detailed information).
10. Select the Custom script and provide the javascript for the fields to process.
Queue 2 – Harmony AI:
Harmony AI refers to the process of extracting meaningful information from structured & unstructured documents, such as text files, PDFs, images, and scanned documents.
This framework will facilitate the processing of incoming files, from file digitization to extracted information validation, all in an open, extensible, and versatile environment. It helps combine different approaches to extracting information from multiple document types. The main aim is to make the process of extracting data as easy as possible: creating one single workflow that will extract data from a variety of documents. The acceptable cards are Aadhar, PAN card, Voter card and driving license. Follow the below steps to create a queue name for business exception. Here we are continuing from Fetch data queue.
1. Select the project in which you want to configure the Interact. Here chooses the project as “Server creation”.
2. Navigate to the “Interact Workflow” at the left-hand side of the page.
3. You will be directed to the project configuration page.
4. Select the queue configuration field.
5. Choose the queue type as “HarmonyAI” from the drop-down list.
6. Enter the queue name as “Aadhar Card”.
7. Click here to know about the queue access for the fields.
How to upload the cards for processing through Harmony AI?
1. Select the “click here” on the Harmony AI.
2. A pop-up will appear on the window.
3. Upload the sample Aadhar card to be processed by the bot.
4. Click on the upload option and select the file from the local system.
5. Once the file has been uploaded, the type will be automatically chosen as “Aadhar card”.
6. Click on the Get taxonomy button to extract the details from the provided Aadhar card.
Queue 3 – Business exception:
The business exception refers to a situation where the workflow process is disrupted due to unexpected or abnormal conditions that occur while the bot is executing the automation. These exceptions can be caused by various factors such as data errors, system issues, user interactions or any other unexpected events that the bot may encounter while execution. To notify these exceptions to the user, the cases can be automated to move to business exception queue so that the user may take actions to prevent this in future. Follow the below steps to create a queue name for business exception.
Queue 4 – System Exception:
The system exception refers to an unexpected error or issue that arises from the underlying technical systems or software applications with which the bot interacts. Unlike business exceptions, that re related to deviations from normal business rules or processes, system exceptions grow from problem like software crashes, connectivity errors, server downtime or any other technical glitches that disrupt the automation workflow. To notify these exceptions to the user, the cases can be automated to move to system exception queue so that the user may take actions to prevent this in future. Follow the blow steps to create a queue name for system exception.
Queue 5 – Rejected:
The transactions which do not have sufficient information or incorrect data to proceed with the automation process can be categorized under rejected queue. These transactions need to be manually verified to check the accuracy of the data provided. If the data is accurate, then these transactions can be re-processed. Otherwise, the transaction can be cancelled. Follow the blow steps to create a queue name for Rejected.
Queue 6 – Completed:
Once all automation process has been completed successfully and performed the required tasks, the transactions can be moved to completed queue. This queue enables you to view the completed transactions on the Manager portal. Follow the blow steps to create a queue name for business exception.
1.5.4 Business Rules
Business rules allow the user to define rules and conditions for the transaction process. These rules are crucial during project configuration as they help the user to make decisions based on the real time data.
In simpler terms, this step acts as a checkpoint for every transaction, ensuring that each transaction is validated, and further actions are processed seamlessly during bot execution.
Benefits
1. The business rules allow the user to reduce the workflow process by handling complex cases with multiple conditions at the project configuration level.
2. It minimizes the manual intervention during runtime and processes the cases within minutes.
3. This makes transaction movement easier and swifter through “If/Else” functionality compared to the traditional process of transaction movement.
4. It improves flexibility and enhances efficiency in data management by customizing field values and copying one field value to another queue.
How do business rules work?
Traditionally, the business rules model wouldn’t allow users to process transactions with multiple conditions. To overcome this hurdle, the “If/Else” functionality implements a comprehensive and structured model, enabling users to pre-determine and define their own criteria in all possible ways. This functionality allows the user to create multiple conditional parameters that can execute actions based on the specified criteria.
The below diagram represents the diagrammatic flow of the model of the business rules.
- If: This part specifies the condition that must be met for the action in the “Then” part to be executed.
- Then: This part specifies the action to be taken if the condition in the “If” part is true.
- Else: This part specifies the action to be taken if the condition in the “If” part is false.
Please note that the below picture demonstrates a sample example of a process flow model.
Visual Representation of Business rule window:
How to implement and configure the rules?
Let’s understand the key concepts and configuration steps in the business rule window.
Step 1: To access the “Rule Configuration” window, select the “Create Rule” button.
If Part:
This section allows the user to choose the fields, specify the condition and provide the conditional value that is to be actioned and processed. Let’s see how to add rule condition in the “IF” part.
Step 2: Select the “Source Queue” name from where the fields have to be configured. In the “If” part, there will be three options to configure.
1. Field: This drop-down displays the “fields” that are available for the current chosen queue. Select the required fields which needs to be actioned.
2. Operator: There are 12 operators with which the user can define the values. Choose the operation from the drop-down.
a. Equals: It validates to check whether the input “FieldName” value received is equal to the specified condition value.
b. Not Equals: It validates to check whether the input “FieldName” value received is not equal to the specified condition value.
c. Greater than: It validates to check whether the input “FieldName” value received is greater than the specified condition value.
d. Less than: It validates to check whether the input “FieldName” value received is lesser than the specified condition value.
e. Greater than or equals: It validates to check whether the input “FieldName” value received is greater than or equal to the specified condition value.
f. Lesser than or equals: It validates to check whether the input “FieldName” value received is lesser than or equal to the specified condition value.
g. Contains: It validates to check whether the input “FieldName” value received contains the specified condition value.
h. Does Not Contains: It validates to check whether the input “FieldName” value received does not contain the specified condition value.
i. Starts With: It validates to check whether the input “FieldName” value received starts with the specified condition value.
j. Ends With: It validates to check whether the input “FieldName” value received ends with the specified condition value.
k. Empty: It validates to check whether the “FieldName” value is empty. When this operator is chosen, there will be no “Value” field to provide, the values can be directly moved to “Then” part condition.
l. Not Empty: It validates to check whether the “FieldName” value is not empty. When this operator is chosen, there will be no “Value” field to provide, the values can be directly moved to “Then” part condition.
3. Value: It enables the user to provide the conditional values to action the process with the values against the selected field name.
Then Part:
This part will be actioned when the transactions meet the conditions specified in the “If” part. It provides the user with two options: they can move the transactions directly without setting or copying any field values, or they can move the transaction by setting up and copying the values.
1. Destination Queue: Select the “Destination Queue” name where the fields has to be moved if the transactions met the specified criteria/ condition in the “If” part.
2. Action: This additional step lets the user to set or copy the values for the transactions against any field value. There are two options,
a. Set: It lets the user to set any default values once the transactions are processed and moved to the specified queue. By choosing this option, the user can set the values to one or more fields in the destination queue.
b. Copy: It lets the user to copy the values from any source field and paste them into the destination field. By choosing this option, the user can set the values to one or more fields in the destination queue.
Else Part:
This section will be actioned when the transactions does not meet the condition and criteria mentioned in the “If” part. It provides the user with two options: they can move the transactions directly without setting or copying any field values, or they can move the transaction by setting up and copying the values.
1. Destination Queue: Select the “Destination Queue” name where the fields have to be moved if the transactions do not meet the specified criteria/ condition in the “If” part.
2. Action: This additional step lets the user to set or copy the values for the transactions against any field value. There are two options,
a. Set: It lets the user to set any default values after the transactions are processed and moved to the specified queue. By choosing this option, the user can set the values to one or more fields in the destination queue.
b. Copy: It lets the user to copy the values from any source field and paste them into the destination field. By choosing this option, the user can set the values to one or more fields in the destination queue.
Multiple Conditions
There are options to add multiple conditions within the “IF”, “Then” and “Else” parameters as well as there is option to add multiple “Else-If-Then” parameters.
A. Adding “Multiple Conditions” in If part:
Adding multiple conditions in the “If part” allows the user to combine them using “AND” or “OR” logic. This flexibility enables the creation of complex rules that can accurately reflect real time scenarios and decision-making processes.
All the fields accessible in the specified source queue can be validated multiple times with the below logics.
AND Condition: When the user is adding more fields with this logic, all specified conditions must be true for the action in the “Then” part to be executed. This is useful for scenarios where multiple criteria need to be met simultaneously.
OR Condition: At least one of the specified conditions must be true for the action in the “Then” part to be executed. This is useful for scenarios where any one of multiple criteria being met is sufficient.
B. Adding “Multiple fields” in Then and Else part:
Adding multiple fields in the “Then” and “Else” part allows the user to set/copy the values to the destination field. All the fields accessible can be added multiple times to set or copy the values.
1.5.5 Queue Reference Field
The Reference Field is a key feature in the Interact module designed to uniquely identify transactions within a queue. Its primary purpose is to detect and manage duplicate entries automatically. By comparing the reference values across transactions, the system ensures that the same transaction is not processed multiple times, reducing errors, improving efficiency, and maintaining data integrity during automation.
This feature is particularly useful for workflows handling high-volume transactions, where manual tracking of duplicates is not feasible. It also provides a structured mechanism for users and bots to manage duplicates by moving them to a designated queue for review.
Steps to configure the field:
Queue configuration
Upon each field creation, the reference will be created and available under queue configuration for field mapping. Click here to learn about field creation. Below are the steps to configure the reference field,
Steps:
1. Open the queue and navigate to the Field Mapping section against the specific queue.
2. In the Reference column, select one of the fields that will serve as the unique identifier for duplicate validation. (e.g., Transaction ID, Order Number, or Invoice Number).
3. Update the queue configuration to include the selected reference field.
4. Save the configuration to ensure that the reference field is applied to the queue.
Business Rule Configuration
Once the queue has been updated with the reference field, a business rule must be created to handle duplicates.
Steps:
1. Navigate to the Business Rules section after configuring the queue.
2. Add a new rule for the queue.
3. Select the reference field from the list of available fields; it will appear as “Field Name (Reference)”.
4. Set the condition for the rule to “Duplicate”.
5. The application will automatically create a default “Duplicate” queue, where all detected duplicate transactions will be moved.
6. Save both the business rule and the project to apply the configuration.
7. Users can review these transactions in the Duplicate queue and process them according to their workflow policies.
Key Considerations
1. Placing the Reference field rule at the top guarantees that duplicates are identified first, preventing incorrect processing of duplicate transactions.
2. Only one reference field can be selected per queue in the Queue Configuration section, and only one duplicate condition can be applied to that reference field within the Business Rules section for the queue.
a. However, you can have multiple queues, each with its own reference field and duplicate condition.
3. Multiple reference fields and multiple duplicate conditions cannot be added.
Adding Reference Field for Existing Projects
For all existing projects, the Reference field is already available in the Queues section. To implement duplicate handling in current workflows, business rules must be configured properly.
Steps to Configure for Existing Projects:
1. Select the reference field against the queues in Queue configuration section.
2. Open the business rules section for the relevant queue.
3. Ensure that the Reference field rule is placed at the top of the “If” branch.
4. After adding the Reference field rule, proceed to configure any additional rules for the queue as required.
1.5.6 Queue Priority
The Priority field in the Interact module defines the urgency level of a transaction and determines how it should be processed within a queue. It ensures that important transactions are handled first, improving response time and operational efficiency.
This field is available as a default field configured in Interact, viewable only in the Queue Review section, and can be updated only through Business Rules.
Key Benefits
1. Reduce delays and customer escalations.
2. Integrates seamlessly with existing queue modes for flexible prioritization.
3. Supports dynamic, rule-based processing without manual intervention.
Configuring Priority Using Business Rules
Business Rules automatically update priority levels based on the defined field conditions (such as equals, contains, etc.) ensuring that critical transactions are processed first without manual intervention.
Steps to Configure:
1. Navigate to Business Rules and select the queue where your transactions are indexed.
2. Create a new rule or edit an existing one.
3. Define the condition that determines when the rule should apply.
a. Example: If the “Payer Name” contains “Apollo,” apply the rule.
5. In the action section:
a. Select Set Field → choose Priority → assign High(1) (or desired level).
6. Save and apply the rule.
Once activated, it automatically marks transactions that met the specified conditions as high priority and processes them first according to the queue mode.
How does priority work?
Each transaction can have a priority level — High, Medium, and Low.
1. High priority transactions are processed before Medium and then Low.
2. If multiple transactions share the same priority, the order is determined by either of the following queue mode:
a. FIFO: Older transactions with priority set are processed first.
b. LIFO: Most recently added transactions with priority set are processed first.
c. Random: Transactions are processed in no specific order.
Default behavior: If a transaction has no priority set and no queue mode specified, it is processed in a FIFO manner according to the queue rules.
Example
Let’s say in a project, the index queue receives 10 transactions, out of which 2 are High, 5 are Medium, and 3 are Low.
The system will first process the two High priority transactions. Once completed, it will process Medium, and finally Low, following the order defined by the queue mode (FIFO, LIFO, or Random).
1.5.7 Email Notification
Email Notification
Interact also allows for the setup of automated email notifications, keeping users informed of queue movements and changes throughout the process. This feature ensures smooth communication and transparency during automation workflows.
Why do we need this step?
1. Emails can act as a form of record-keeping. They provide documented evidence of the completed transaction, which might be needed for auditing, compliance, or future reference purposes.
2. Notifications allow for real-time monitoring. In case of errors or issues, they can trigger an alert to relevant personnel for immediate action.
3. It improves communication by informing relevant parties about the progress, completion, or any issues related to the transaction, maintaining transparency within the organization or between systems.
4. Integrating email notifications as part of the workflow can further automate the process, ensuring that stakeholders receive timely updates without manual intervention.
How to configure email notification in your project?
Let’s continue from the use case, here I am going to set the email address to notify whenever the transactions has been completed successfully or if there are any errors thrown during the runtime.
Follow the below steps,
1. Login to the Manager and navigate to the “Projects” where you have configured the Interact.
2. Click on the “Interact Workflow” and choose the “EmailNotification” step.
a. This is not a mandatory step while configuring the project. You can also skip this step to move forward.
b. In this case, I am going to add the “Email Address” with two different mail subjects.
3. There will be two options available “Bulk” index and “Manual” index notification. You can configure both of these, and you can also configure either of them.
4. Let’s first create the “Bulk Index” to send the notification configuration.
a. This notification will be triggered whenever the transactions are indexed as bulk to the project to the specified mail address along with the CC mail addresses provided.
b. Here I am specifying CC mail address as my mail address to send a notification to myself every time the transactions are uploaded.
5. Next, moving to the “Manual index Notification” option.
a. Here, I am choosing the “Queue” name as “Completed”, so that once the transactions are moved to completed queue, an email will be triggered for each transaction.
b. Next, moving to the “TO” field, you need to mention the mail address to whom the notification needs to be triggered.
c. Next, “CC” field, here you need to mention the “CC” mail addresses. In this case, I left out this option.
d. Now, moving to the “Subject” to provide the subject for the mail to be notified.Here I am specifying the subject as “Transactions completed”.
e. Finally, the “Body” helps you to provide the content that needs to be sent along with the mail. You can configure the mail body as per project preference.
i. Here I am specifying the Body as “The transaction has been completed successfully.”
6. Now, Add and save the project.
1.5.8 Master Data
MasterData
The MasterData Configuration enables the storage of a standardized set of inputs for processing over a specified period. It also allows modification by adding or removing data within MasterData.
The flexibility offered by the MasterData Configuration empowers users to swiftly adapt to alterations in input requirements, facilitating smoother and more adaptable data processing.
How to configure MasterData in your project?
Let’s continue from the use case, here I am going add the Master data in an excel sheet.
1. Login to the Manager and navigate to the “Projects” where you have configured the Interact.
2. Click on the “Interact Workflow” and choose the “MasterData” step.
a. Here I am providing the “MasterData” name as “InputFile”.
b. Now, click on the “Browse file” option and choose the respective file from the system folder.
c. In this case, I am uploading the sample excel sheet.
3. Now, click on “ADD” button and save the project.
Now, you have configured your project successfully and refer the activities to know how to add transactions to your project.
1.5.9 Other Components
1.6 Security
Robility maintains secure and reliable communication between its core components – Manager, Designer, and Runner-by implementing advanced security mechanisms. This guide provides an overview of how API communications are safeguarded to protect your automation workflows.
1.6.1 Authentication
The Robility Manager provides users with the option to choose their preferred authentication method based on their organization’s requirements. There are two types of authentications available which ensures both convenience and security in the login process.
Authentication Types
Username and Password Authentication:
The tenant will be configured with default authentication as Username and password. The users have to enter their registered mail ID and Password created while activating the account when accessing the platform. Click here to know about the user invite process.
Single Sign on with Microsoft:
The SSO can be integrated with Microsoft when the Tenant/ Organization Admin has configured with the Azure AD account. The authentication with Microsoft can be processed only when the admin has completed the signup process. To sign up with Microsoft Azure, click here.
How to authenticate and sign in?
Once the Organization and the tenant has been created. The users can be invited to the platform. The invitation to the platform for signing up can be authenticated through Microsoft. Follow the below steps to configure the Microsoft Azure account.
1. Login to the platform.
2. Click on the settings icon against the organization name.
3. Choose Identity provider option.
4. The default option will be selected as Username and Password.
5. Click on the Microsoft option and save button.
6. The page will be refreshed and logged out.
7. Now, you will be able to sign with Microsoft Azure AD account.
8. Further, you can invite the users to the platform.
Password Recovery
If a user forgets their password to access the platform, they can easily reset it by following the steps below:
1. On the login screen, click the “Forgot Password” link to begin the password recovery process.
2. In the provided field, enter the email ID that is registered with the platform, and then click the Proceed button.
3. The system will send a password reset email to the entered email address with further instructions.
4. Open the email and click the Reset Password button to initiate the password reset process.
5. After clicking the reset button, a second email will be sent containing a temporary password that you can use to log in.
6. Open the second email and click the Click Here to Login link. This will redirect you to the login page where you can enter your credentials.
7. On the login page, enter your registered email ID and the temporary password provided in the email, and log in.
8. Once logged in with the temporary password, you will be redirected to a page where you can set a new password.
9. On the reset page, enter your new password, confirm it, and save the changes. Your new password will now allow you to access the platform.
Troubleshooting steps
When authenticating with Microsoft, if the provided business mail id( Robility Manager) is not registered with Azure App registration services, they will have to create a new one. An error message will be thrown displaying as “Azure AD authentication failed.” To configure with Azure AD App Registration, click here.
1.6.2 Authorization
This section provides a detailed overview of the default roles and permissions assigned to each user role within a tenant.
In Robility Manager, tenant-level roles and permissions define the scope of platform management and configuration for a specific tenant. These roles determine what actions users can perform, ensuring a structured and secure automation environment.
Each developer can be assigned only one role, ensuring clear responsibilities and preventing conflicts in access control. By default, all users invited to the platform are assigned the “User” role, which grants them basic access to the tenant’s features. Administrators can later update user roles to provide additional privileges based on their responsibilities.
To learn how to modify user roles and permissions, click here.
Default Permissions
1. TenantAdmin: This role has full administrative privileges across the platform, allowing users to configure settings, manage users, and access all platform features. Tenant Admins are responsible for overseeing the platform’s operations and ensuring that everything is set up according to the organization’s needs.
Note that the tenant administrator can fully utilize the platform but will not have the access to activate the designer license. To Activate the designer license, their roles needs to be modified as “RPA Developer”.
Permissions:
The below table guides you with the permissions and actions assigned to the Tenant.
| Pages | View | Add | Edit | Delete | Action |
|---|---|---|---|---|---|
|
Products |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Harmony AI |
Yes |
Yes |
Yes |
Yes |
Yes |
|
MarketPlace |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Projects |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Invite Page |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Resources |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Templates |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Settings & its components |
Yes |
Yes |
Yes |
Yes |
Yes |
|
Help |
Yes |
Yes |
Yes |
Yes |
Yes |
2. RPA Developer: RPA Developers is intended for users who are responsible for designing and deploying automation workflows with Designer and Runner.
Permissions:
The below table guides you with the permissions and actions assigned to the RPA Developer.
| Pages | View | Add | Edit | Delete | Action |
|---|---|---|---|---|---|
|
Products |
Yes |
NA |
NA |
NA |
Yes |
|
Harmony AI |
Yes |
NA |
NA |
NA |
No |
|
MarketPlace |
Yes |
NA |
NA |
NA |
Yes |
|
Projects |
Yes |
No |
No |
NA |
No |
|
Invite Page |
No |
No |
No |
No |
No |
|
Resources |
Yes |
Yes |
Yes |
Yes |
NA |
|
Templates |
Yes |
NA |
NA |
NA |
No |
|
Settings & its components |
No |
No |
No |
No |
NA |
|
Help |
Yes |
NA |
NA |
NA |
NA |
3. User: The User role will be standard users who interact with the platform without needing access to the administrative or any Robility products. These users can perform tasks assigned to them but have limited access in the platform.
Permissions:
The below table guides you with the permissions and actions assigned to the User.
| Pages | View | Add | Edit | Delete | Action |
|---|---|---|---|---|---|
|
Products |
Yes |
NA |
NA |
NA |
NA |
|
Harmony AI |
No |
NA |
NA |
NA |
NA |
|
MarketPlace |
Yes |
NA |
NA |
NA |
No |
|
Projects |
Yes |
NA |
NA |
NA |
No |
|
Invite Page |
No |
NA |
NA |
NA |
NA |
|
Resources |
No |
NA |
NA |
NA |
NA |
|
Templates |
No |
NA |
NA |
NA |
NA |
|
Settings & its components |
No |
NA |
NA |
NA |
NA |
|
Help |
Yes |
NA |
NA |
NA |
NA |
Click here to know about the Project level roles and permissions in the RobilityManager.
1.6.3 Setting up Azure AD
Robility Manager allows users to authenticate using Microsoft Azure App registration. The Organization Administrator who creates the tenant will be responsible for configuring it. If the organization’s tenant admin has already completed Azure App Registration, they can connect it to their tenant directly with existing user account.
If you have decided to use Azure AD for your organization, please ensure that you have followed the steps below.
Pre-requisites
To configure with Azure AD, the following are the pre-requisites,
1. The Organization Administrator needs to acquire Enterprise license.
2. Needs Administrative access in both Robility Manager Cloud and Azure AD account. If you do not have administrator access, coordinate with Azure admin to complete the process.
To create an application, kindly follow the below steps. Here we are configuring the account and have to setup against each menu.
Steps to configure
A. App registration:
1. To create an app registration in your account with Organization business mail ID, click here.
2. Select App registration under Azure services.
3. Click on the New registration.
4. Enter the name for the application. This can be changed later.
5. Under Support account types, select only “Accounts in the Organizational directory only” to configure the access for the Application/API.
6. Under Redirect URI, select the platform as “WEB” and set the Redirect URI as WebsiteURL+SSO/SSOAuthCheck.
7. Then click on the Registration button.
Now that the app has been registered, we are going to configure the Azure for integration. Follow the below steps:
B. Application Overview:
Once the application has been registered, the user will be able to view the application name under “All Applications” field.
1. Click on the application name and you will be redirected to the Application overview page.
2. Under Essentials, you can find the Application (Client ID) and Directory (TenantID), this can be viewed anytime. But when integrating with Robility Manager under Azure AD authentication, the Client ID, Tenant ID will not be required.
C. Authentication page:
1. Navigate to the Authentication page on the left-hand side of the page.
2. Under the Redirect URIs, enter the “website url + /SSO/SSOAuthCheck”.
3. Under Implicit grant and hybrid flows, select the token authentication as “ID Tokens”.
4. Now, click on save.
To learn more about Implicit grant and hybrid flows, follow the documentation –https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-implicit -grant-flow
D. Token Configuration page:
1. Navigate to the token configuration page from the left-hand side menu.
2. Select Add Optional Claim.
3. Under Token type, select ID.
4. Select the check boxes for family_name ,given_name, and upn to add them as optional claims.
To learn more about optional claims configuration, follow the documentation – https://learn.microsoft.com/en-us/azure/active-directory/develop/optional-claims .
E. API Permissions page:
1. Navigate to the API Permissions from the left-hand side menu.
2. Click on “Add permissions” button.
3. A pop will be opened to request API permissions. Select “Microsoft Graph API”.
4. Then choose “Delegated permissions” under it.
5. Under OpenID permissions – choose email, OpenID, profile.
6. Under Group member permissions – choose GroupMember.Read.All.
7. Under User permissions – choose User.Read, User.ReadBasic.All.
8. Select the Grant Admin consent checkbox.
For more information about the access and permissions, see the Azure AD permissions documentation.
F. Certificates and Secrets:
Under the certifications and secrets page, you need to create a new client secret for your account. Follow the below steps to create a client secret.
1. To learn how to Create a client secret, follow the documentation steps – https://learn.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-
app#add-a-client-secret
2. Take note of the secret code and save it to use later. But this is not required for the integration with Robility Manager under Azure AD authentication.
Now, the configuration set up has been completed for the app registered. Once all the above steps have been completed, the admin can integrate with Microsoft.
1.6.4 API Security Guide
Robility’s robust security mechanisms provide a foundation for safe and efficient automation workflows. These measures ensure that communication between Manager, Designer, and Runner remains secure and reliable.
1. Authentication and Authorization
a. OAuth 2.0 Authentication: Robility APIs leverage OAuth 2.0 for secure token-based authentication.
b. User Authentication: Access requires valid credentials or API keys, with support for Multi-Factor Authentication (MFA) for enhanced security.
c. Role-Based Access Control (RBAC): Permissions are assigned based on user roles, ensuring that only authorized individuals can perform specific actions.
2. TLS Encryption
a. Encrypted Communication: All API communications between Manager, Designer, and Runner are encrypted using HTTPS with TLS.
b. Certificate Validation: Certificates are validated by Manager to ensure secure connections and prevent unauthorized access.
3. Session Management
a. Token-Based Authentication: Sessions are secured with time-limited tokens. Refresh tokens allow for seamless re-authentication.
b. Automatic Session Timeout: Sessions automatically expire after a set period of inactivity to reduce risks.
4. Data Security
a. Payload Encryption: Sensitive data within API requests and responses is encrypted to prevent unauthorized access.
b. Secure Data Storage: Credentials and other sensitive information are stored in encrypted formats.
5. Input Validation
a. Sanitized Inputs: All API inputs are validated and sanitized to prevent injection attacks like SQL injection or cross-site scripting (XSS).
b. API Rate Limiting: Throttling mechanisms are in place to prevent overuse and mitigate denial-of-service (DoS) attacks.
6. Secure Manger Hosting
a. Tenant Data Isolation: In multi-tenant deployments, each tenant’s data is logically isolated to maintain privacy and security.
Best Practices for API Security
1. Use strong, unique passwords and enable MFA for all accounts.
2. Regularly update and rotate API keys and access tokens.
3. Monitor audit logs for unusual activity and configure alerts for anomalies.
4. Limit API access to specific IP ranges or VPNs.
5. Regularly review and update permissions to ensure minimal access for each role.
1.6.5 SDK Security
Robility SDKs are built with enterprise-grade security measures to ensure safe development, deployment, and integration with the Robility platform. This guide explains the mechanisms and practices implemented to secure Robility SDKs.
Standard SDKs are available as separate packages upon request to enable masking integration with Robility Manager. These SDKs are exclusively offered for the on-premises deployment model.
1. Secure Communication
a. TLS Encryption: All communication between SDKs and the Robility platform is encrypted using TLS (Transport Layer Security) to prevent data interception or tampering.
b. HTTPS Protocol: SDKs require secure HTTPS endpoints to ensure safe data transmission.
2. Authentication and Authorization
a. OAuth 2.0: Robility SDKs use OAuth 2.0 for secure access to APIs, ensuring only authorized applications can connect to the platform.
b. API Keys: Access to SDKs requires scoped API keys, restricting access to only necessary functionalities.
c. Role-Based Access Control (RBAC): SDKs respect RBAC policies, ensuring users or services only have permissions relevant to their roles.
3. Token Security
a. Access Tokens: SDKs use short-lived access tokens for secure API interactions, minimizing the risk of token misuse.
b. Refresh Tokens: Secure mechanisms allow refresh tokens to obtain new access tokens without reusing sensitive credentials.
c. Session Management: Sessions expire automatically after a set period of inactivity, reducing exposure to session hijacking.
4. Data Security
a. Payload Encryption: Sensitive information in API requests, such as credentials or configurations, is encrypted to prevent unauthorized access.
b. Data Masking: SDKs ensure sensitive information like passwords is not exposed in logs or debugging outputs.
5. Secure Dependencies
a. Validated Dependencies: SDKs rely on secure, verified libraries and dependencies to reduce the risk of vulnerabilities.
b. Frequent Updates: Robility regularly patches SDKs and dependencies to address security concerns.
6. SDK Version Control
a. All SDK are regularly updated to patch vulnerabilities and improve security.
b. Notify developers to deprecate older versions and enforce the use of updated ones.
Best Practices for Using Robility SDKs Securely
1. Use scoped API keys to grant the least privilege necessary for a task.
2. Rotate access tokens and API keys periodically to reduce the risk of compromise.
3. Validate endpoint URLs and certificates to protect against man-in-the-middle (MITM) attacks.
4. Monitor API logs to identify unauthorized access or potential misuse.
1.7 Manager Updates
Find the latest release of RobilityManager here.
1.7.1 v.26.8.0.7
This release introduces enhancements, and bug fixes across multiple areas of the platform.
Prerequisites: Cache must be cleared once after deployment to ensure Robility Manager functions as expected.
Enhancements
1. License Expiry Notification
Enhanced the License Expiry Notification modal to provide direct navigation to the License Request and License Renewal pages, enabling quicker access to license management actions.
a. Migration to Project Layer
Migrated the Admin Console implementation from the Tenant layer to the Project layer. Integrated Admin Console functionality within the Project layer in the Automation Ops page, improving project-level operational management capabilities.
b. UI Enhancements
Redesigned the Admin Console interface by replacing the partial-view slider with a modal popup, delivering a more streamlined and user-friendly experience.
c. PDF Export for Command
Added PDF export functionality for the Top Process and Running Process modal popups within Admin Console command views, allowing users to easily download and share process details.
3. Scheduler – Time-Based Execution
Added support for a new Execution Type field in the Time-Based Scheduler, allowing users to choose between Parallel and Sequential processing. Parallel execution now includes configurable Execution Count and Retry Count, enabling automatic retries of failed queue items within the scheduled window, while Sequential execution processes items one after another in order.
Bug Fix
Interact
1. Fixed an issue where uploaded attachments were not visible on the Interact Review page for specific projects despite being successfully saved. Enhanced the file loading logic to ensure attachments are retrieved and displayed correctly across projects
2. Fixed an issue where items were not moved to the Completed queue when a business rule was configured with the “Empty” Updated the rule evaluation logic to correctly identify fields with no value and execute the configured queue transition.
Known Issue
1. Time-Based Scheduler: Retry functionality is currently not working for workflows configured with the Advanced Time-Based Scheduler.
Existing Limitations
1. When the storage type is set to Local Storage in the Storage tab, workflows larger than 60 MB cannot be downloaded using RunnerApi.
2. The Priority field is currently visible only in the Queues tab and is not yet available in other Interact menus, such as URN Management or Reports.
3. The user limit in Machine Templates is currently restricted to 200 users per machine template. This limit will be increased in a future release.
4. The asset text limit has been increased to 20,000 characters on the Manager side; however, the Activity side does not yet support this limit.
5. Microsoft O365:Access tokens are valid for one hour. After expiration, OAuthconnections can automatically obtain a new access token using the refresh token, while Client Credentials connections must be reconnected manually.
Release Date: 29.08.2026
1.7.2 v.26.7.0.9
This release introduces new features, enhancements, and bug fixes across multiple areas of the platform.
Prerequisites: Cache must be cleared once after deployment to ensure Robility Manager functions as expected.
New Feature
1. Admin Console
Introduces a centralized administrative console that enables real-time monitoring and remote management of machines running the Unattended Runner. Administrators can execute commands, monitor machine health, and manage runner logs through a live connection between the Manager and Runner.
New Integration
1. Microsoft SharePoint Integration
Microsoft SharePoint integration is now available on the Robility platform, enabling users to manage SharePoint sites, files, folders, and documents seamlessly within their automation workflows using the Microsoft Graph API.
Note: SharePoint activities are not included in the current release. These features are currently available only in Integration. SharePoint activities will be included in an upcoming release.
Enhancements
1. MasterData Grid – Updated By Column
Added an Updated By column in the MasterData Grid under Interact Project Configuration to display the user who last modified each record, improving audit tracking.
2. Robot Status
The Robot Status page now includes a Move to Idle option for locked robots. Clicking this updates the robot’s status to Idle, making it available for task execution again.
3. Transaction Report Download in Email Notifications
Improved the Download Report functionality so users can download transaction reports in Excel format directly to their local system.
4. UI Enhancements
a. Automation Ops – Flow: Flow status is now represented with color-coded indicators for improved visibility — Idle (Blue), Running (Green), and To Check (Amber).
b. Grid Messages: Added a “No Data Found” message to empty grids across Robility Manager, providing clearer feedback when no records are available.
5. Robility Flow – Automated API Key Management
Robility automatically regenerates API keys for Flows used in scheduled executions.
If a Flow API key is generated for a solution in the Workflow section and the solution is associated with a Scheduler, the key is automatically renewed before expiration. This ensures uninterrupted scheduler execution and eliminates the need for manual key renewal.
Bug Fixes
1. Interact Manager
a. Transaction Details
Fixed an issue where transaction details failed to load due to incorrect queue-project mappings, causing the “No Fields configured against the Queue” Added validation to ensure queues are mapped only to their respective projects, preventing configuration issues and ensuring correct data retrieval.
b. Transaction Processing
Fixed an issue where transactions were routed to incorrect queues. Updated validation now allows only project-specific queues to be assigned during business rule execution, preventing invalid mappings.
c. Data Table Field Updates
Fixed an issue where Data Table field values were not displayed when reopening existing queue transactions. Improved Data Table handling ensures values are retrieved and displayed correctly across transaction views.
d. Business Rule Processing
Fixed an issue where transactions with Data Table fields were not routed correctly. Enhanced Data Table support now ensures accurate rule evaluation and reliable queue routing based on configured business rules.
Limitations
1. When the storage type is set to Local Storage in the Storage tab, workflows larger than 60 MB cannot be downloaded using RunnerApi.
2. The Priority field is currently visible only in the Queues tab and is not yet available in other Interact menus, such as URN Management or Reports.
3. The user limit in Machine Templates is currently restricted to 200 users per machine template. This limit will be increased in a future release.
4. The asset text limit has been increased to 20,000 characters on the Manager side; however, the Activity side does not yet support this limit.
5. Microsoft O365: Access tokens are valid for one hour. After expiration, OAuth connections can automatically obtain a new access token using the refresh token, while Client Credentials connections must be reconnected manually.
Release Date: 25.07.2026
1.7.3 v.26.5.0.4
In this release, we have introduced enhancements and bug fixes across multiple areas of the platform.
Prerequisites
Cache must be cleared once after deployment to ensure Robility Manager functions as expected.
Enhancements
1. LLM Configuration: The LLM Configuration page has been enhanced with Active and Inactive states for each provider. Providers can be deactivated and reactivated as needed. Provider details can be edited only when the provider is in the active state; editing is disabled while the provider is inactive.
2. UI Enhancements: Tenant-level features such as Invite, Projects, Resources, and Templates, along with project-level features including Roles & Users, Workflow, Vault, Automation Ops, and License in Robility Manager, now feature a streamlined card-based UI. This improves clarity, speeds up setup, and ensures consistent configuration across workflows.
3. Robility Flow History for Time-Based Scheduler: The Time-based scheduler for Robility Flows has been enhanced to provide visibility into execution history. In Automation Ops, under Flow, users can access the time-based scheduler to view past executions along with their status. This enables better monitoring, troubleshooting, and debugging of scheduled workflows through access to historical execution data.
Bug Fixes
1. Machine Templates: Resolved an issue on the Resource page, where adding users to Machine Templates resulted in duplicate entries and inaccurate license count calculations.
2. Time-Based Scheduler: Fixed an issue where scheduled executions were not triggered for the Weekly Multiple Schedule option due to missing Daylight-Saving Time (DST) handling in the time zone logic. Updated the scheduler’s time zone logic to correctly support DST.
3. Robility Lens Workflow Execution: Resolved an issue where workflow execution failures in Robility Lens showed only a generic “Activity Not Found” message when required features were unavailable in Hub or not mapped to the target environment. The warning popup now displays the exact missing feature name and version, making dependency issues easier to identify and troubleshoot.
Limitations
1. When the storage type is set to Local Storage in the Storage tab, workflows larger than 60 MB cannot be downloaded using RunnerApi.
2. The Priority field is currently visible only in the Queues tab. It is not available in other Interact menus such as URN Management or Reports.
3. User limit in Machine Templates – You can add up to 200 users per machine template. This limit will be increased in the future release.
Released Date: 30.05.2026
1.7.4 v26.4.0.5
In this release, we have introduced new integration, enhancements and bug fixes across multiple areas of the platform.
Prerequisites
1. Cache must be cleared once after deployment to ensure Robility Manager functions as expected.
What’s New
1. Microsoft 365 Integration
Microsoft 365 integration is now available in the Robility platform, enabling users to seamlessly send emails, download attachments, and access user profiles via Microsoft Graph API within their automation workflows.
Enhancements
1. Vault Page
The maximum allowed character limit for text input in Asset Type has been increased to 20,000 characters.
2. UI Enhancements
The LLM Configuration Management and Tenant Environment Setup pages in Robility Manager now offer a streamlined and consistent experience. They centralize model settings and tenant environment selection for simpler management. This enables faster setup, improved clarity, and uniform configuration across Robility workflows.
3. Login Page Security
Improved handling of user credentials on the login page to ensure they are no longer directly exposed during rendering or runtime.
Bug Fixes
1. Machine Template
Fixed an issue preventing multiple users from being added to the Machine Template on the Resource page, and a maximum of 200 users can now be added.
2. User Profile Picture
Fixed an issue where user profile images were not displayed correctly for some users in the Manager.
3. Scheduler
Resolved an issue in the Daily and multiple Schedules where a flow scheduled to trigger for a count of 1, was instead triggered multiple times rather than the intended number.
Limitations
1. When the storage type is set to Local Storage in the Storage tab, workflows larger than 60 MB cannot be downloaded using RunnerApi.
2. The Priority field is currently visible only in the Queues tab. It is not available in other Interact menus such as URN Management or Reports.
3. User limit in machine templates – You can add up to 200 users per machine template. This limit will be raised in the future release.
Released Date: 02.05.2026
1.7.5 v.26.3.0.4
In this release, we have introduced enhancements and bug fixes across multiple areas of the platform.
Enhancements
1. LLM Configuration
The LLM Configuration management has been enhanced to support 10 providers with provider-specific basic configuration and authentication settings. It also introduces unified advanced settings such as model parameters, network settings, and enterprise compliance options. These enhancements provide improved flexibility, security, and consistent control over model behavior and data handling. Click here to learn more
2. Robility Flow Execution Using Queue-Based Trigger
A queue-based trigger has been introduced for Robility flows, enabling execution when new transactions are added to the queue. This allows flows to be triggered automatically based on incoming queue items, eliminating the need for manual or time-based triggers. It improves responsiveness, scalability, and ensures timely processing of transactions as they arrive in the system.
Bug Fixes
1. Resource Page
Users were unable to add machines on the Resource page. The page remained in a continuous loading state displaying only the Sutherland loading icon without any success or error message. This issue has been fixed.
2. Scheduled Robots
The Advanced Scheduler was not functioning correctly, as it failed to trigger robot execution, and the scheduled time displayed on the tile appeared in an incorrect color. This issue has now been fixed.
3. Interact
In the Interact table, hovering over multiple data items simultaneously caused multiple hover effects to appear at the same time.
This issue has been fixed. The hover effect is now displayed only for the last hovered item.
4. URN Management
a. All Transactions were selected and a few transactions were subsequently unselected, the unselected transactions were also being unlocked. This issue has now been fixed.
b. Previous queue information was being populated incorrectly, resulting in inconsistent data. This issue has now been fixed.5.
5. Robot Utilization
The Total Hours Executed value was previously incorrect when filtering by a date range. This has been fixed, and it now reflects only the accurate execution hours within the selected period.
6. MarketPlace
The downloaded version did not match the version displayed on the marketplace page. This issue has been fixed.
7. Time-Based Scheduler
The Cron expression note was incorrectly displayed in the center of the popup. This issue has been fixed. b. The “No File Chosen” text was not fully visible in the popup. This issue has been fixed.
Limitations
1. When the storage type is set to Local Storage in the Storage tab, workflows larger than 60 MB cannot be downloaded using RunnerApi.
2. The Priority field is currently visible only in the Queues tab. It is not available in other Interact menus such as URN Management or Reports.
Released Date: 28.03.2026
1.7.6 v.26.2.0.4
Enhancement
1. JIRA App Integration
A new JIRA connection has been introduced under the App Integration section. This integration enables seamless synchronization between Robility and JIRA, allowing automated ticket creation, status updates, and real-time data exchange. It improves cross-team collaboration, enhances visibility into issue tracking, and streamlines overall workflow management for better operational efficiency.
2. Package Upgradation
Updated the core activity packages within Robility Manager to the latest supported versions for improved security, performance, and vendor support continuity.
Prerequisites
1. Cache must be cleared once after deployment to ensure Robility Manager functions as expected.
Bug Fixes
1. Automation Ops
a. Dropdown Content Overlapping
On the Automation Ops page, while adding a robot, dropdown items extended beyond the visible boundary, making options difficult to view or select. This has now been fixed, and all items are displayed properly within the visible area.
b. Robot Utilization
The Total Hours Executed value was previously incorrect when filtering by a date range. This has been fixed, and it now reflects only the accurate execution hours within the selected period.
2. Scheduler Robot
a. Monthly Scheduler
When clicking the Time Zone dropdown in the Monthly Scheduler, the list of available options did not appear. The dropdown now displays correctly, allowing users to select their desired time zone.
b. Tile Color Not Changed
On the Schedule robots pages, fixed an issue where schedule status tiles (Allocated, Scheduled, and Failed) were incorrectly displayed in green. This has been fixed. Tiles now reflect their respective status colors.
3. Machine Template
The “Provisioned” status was displayed for only one user when creating a machine template with multiple users. The status now reflects all connected users correctly.
4. Reset Password
The Cancel button in the Reset Password popup was unresponsive. The button is now fully functional, allowing users to close the popup without issues.
5. Vault
a. Previous Dates Not Disabled
While creating an application in Vault against a project, users were able to select past dates. Date validation has been corrected, and past dates can no longer be selected during application creation.
b. Pins & Key Visibility
Previously, PIN and key values were visible to all users. Access has now been restricted to Credential Admins for viewing and modification.
6. User Access Issue
Users in the Robility Manager were able to access both RPA and Tenant roles. This has been corrected; users now have either the RPA or Tenant role based on their assigned permissions.
7. Invite Page
a. Unable to Remove Additional Member
On the Invite User page, when multiple members were added, clicking the remove icon did not delete the selected row. This issue has now been fixed.
b. Requested License Issue
License requests from expired tenants were displayed at the project level. This issue has now been fixed.
8. Page Counts
When selecting the page size as “All,” the table displayed incorrect row information across all tables in the Robility Manager. This has now been fixed.
Released Date: 07/03/2026
1.7.7 v.26.1.0.7
In this release, we have introduced new features, enhancements, and bug fixes in the following areas:
What’s New
1. TAT Report
The TAT Report has been introduced in Robility Interact Reports to track transactions across multiple queues. The report captures key time metrics, including Received Time, Start Time, and End Time at each queue level.
2. User Tracks – Audit Reports
Audit Reports are now available under the User Tracks section to capture all user actions, supports audits and overall system management.
Reports: Login / Logout, Invalid Attempts, VM Add, Privileged User Actions
3. Machine Utilization Page
The Machine Utilization page provides a detailed view of machine activity where robots are executed within a project. It provides monitoring and analysis tools for tracking robot execution across machines.
Enhancements
1. Robility Flow Schedule Execution
The Schedule Robot option now supports Robility Flow automation. Users can configure, schedule, and execute flows automatically using the time-based scheduler without manual intervention.
2. Integration of TOTP-Based MFA Login with QR Expiry and CAPTCHA
The login page now supports TOTP-based multi-factor authentication (MFA) with QR code setup and CAPTCHA validation to enhance account security.
3. Data Retention and Policy
Introduced the Data Retention to manage the storage and lifecycle of Interact workflow data. Project data is retained for a defined period, safely archived, and removed automatically when no longer needed, ensuring compliance and optimized storage.
4. LLM Configuration Management
LLM configuration management is a key capability for organizations to securely set up and manage Large Language Models (LLMs) across different environments.
It supports LLM providers such as Azure OpenAI and Google Vertex AI, and includes the management of embeddings and runtime configurations, including Azure OpenAI embeddings.
5. Vault Page
Access to the Vault page is restricted based on user roles. The Credential Admin role has access to the Add button, enabling users to add, edit, and update Tokens, PINs & Keys, Assets, JWT tokens, and Applications. All sensitive data within the Robility platform is securely managed using the Key Vault configured in the settings. Secrets are stored and retrieved based on the vault type configured for each tenant or project.
Released Date: 31/01/2026
1.7.8 v.25.10.0.2
This release introduces significant enhancements across the platform to improve usability, efficiency, and overall user experience.
Enhancements
1. Tenant Management Enhancements
a. Tenant Renewal: Tenant Admins can now renew expired tenants directly from the tenant selection page, simplifying the renewal process.
b. Tenant Switch: Switching tenants are now seamless and faster. With a single click, users can move between tenants without logging out.
c. Tenant Expiry Display: Expiry information is now visible in user profiles, making it easier to monitor account validity.
2. Invite User Page Updates
a. A new tile displays user role counts for a quick overview.
b. License Renewal: Simplified renewal process supporting both individual and bulk renewals for RPA developers at invite page, reducing administrative effort.
c. License Expiration Date: The Users list now includes a separate column showing the license expiration date for RPA Developer roles.
3. Analysis Count Updates
Simplified layouts make it easier to track and review large datasets such as user lists, projects, and resources. Changes are applied to the following pages:
a. Resource
b. Templates
4. Marketplace Updates
The Marketplace page now features a simplified and interactive user interface for easier navigation.
5. Vault Page Enhancements
a. Expiry dates for tokens, keys, and assets are automatically aligned with tenant expiry and cannot be manually edited, ensuring security and compliance.
b. The Application names and usernames for applications, assets, and other credentials cannot be updated once created.
6. Improved User Interface
a. Tabular grids across the platform have been upgraded for smoother navigation and faster performance.
7. Interact Module Updates
a. Queue Prioritization: Critical tasks are now processed faster through priority settings.
b. Duplicate Prevention: Duplicate entries are automatically prevented, reducing errors and improving workflow accuracy.
1.7.9 v.25.8.0.3
This update includes important fixes and improvements to enhance security.
Enhancements
URN Review Page – File Support
Users can now view PDF files within the URN review page, eliminating the need to download and open them externally.
Revamped UI for Improved Experience:
Sign-In Page
1. A cleaner, modern design makes login faster and more straightforward, reducing friction for both new and returning users.
2. Simplified layouts make it easier to track and review large datasets such as user list, projects, resources, helping users find the insights quickly. You can view these changes applied in the below pages,
a. Invite page
b. Projects page
c. Deploy robots
d. Roles and users.
Note
Post-deployment: Clear the cache and reopen the browser before launching the website for the first time.
Bug Fixes
1. Previously, features were unavailable during automation execution due to sync delay after job execution. This issue has now been resolved.
2. Resolved an issue where the logic to handle usernames containing underscores in email addresses was missed. This has now been validated and addressed.
1.7.10 v.25.7.0.9
This update introduces critical bug fixes and powerful feature enhancements designed to improve stability, security, and usability.
Bug Fixes
1. Business Rules Deletion Issue
Previously, business rules were automatically deleted due to missing validation logic. This has now been fixed, ensuring rules remain intact as expected.
2. Transaction Creation Failure
In certain cases, transactions were not created because the project key was not properly saved in the database. This issue is resolved with additional validation to ensure correct storage during creation.
3. Deploy Robot Page Loading Issue
When resolution settings were left empty, the Deploy Robot page would get stuck in a loading state during edits. We’ve implemented logic to handle null resolution scenarios, ensuring reliable page loading.
Feature Enhancements
1. Cron Expression Scheduler
Schedule your bots with precision using cron-based scheduling. Configure rules for tasks to run at specific times, intervals, or days with complete flexibility. [Click here to learn more]
2. Secure Asset Management
Manage API keys, tokens, passwords, and configuration values in a centralized vault—eliminating hardcoded credentials and ensuring secure, controlled access for authorized bots and users. [Click here to learn more]
3. FIFO/LIFO Queue Processing
Define transaction execution order with FIFO (First-In-First-Out) or LIFO (Last-In-First-Out) modes, aligning task prioritization with business needs.
4. AWS & Google Cloud Integration
Seamlessly integrate Robility Manager with AWS and Google Cloud for secure data storage and retrieval, supporting enterprise-grade scalability. [Click here to learn more]
5. Revamped UI for Improved Experience
Key pages have been redesigned for a cleaner, more intuitive interface:
• Login Page
• Tenant Selection
• Landing Page
• Settings
• Key Vault
• Storage
Known Issue
The Runner status on the “Resources” page may not update to “Provisioned” at times, even when the machine is successfully connected and provisioned in the “Deploy Robots” page. This will be addressed in the upcoming version. In the meantime, restarting the VM once should resolve the issue when it occurs.
1.7.11 v.25.5.0.0
This update delivers essential fixes and improvements on the Robility Manager.
Bug Fixes
1. Resource Page:
a. Case Sensitivity in Resource Names –
Previously, when resources were connected using lowercase letters, the license key could not be connected due to case sensitivity issues. This has now been resolved by allowing the resource name to be recognized in both uppercase and lowercase formats.
b. Runner Status Update
In earlier versions, the Robility Runner status did not update correctly when a machine transitioned from a “Not Connected” state to a “Running” state. This caused inconsistencies on the Resources and Deploy Robots This issue has now been fixed to ensure accurate status updates. Click here to learn more.
2. Interact Workflow:
a. Duplication of URN: Previously, an exception was occasionally thrown due to URN duplication when adding transactions to the queue. This issue has now been addressed and properly handled.
b. Unable to Download File: Previously, users were unable to download files from the “Completed” queue. This issue has now been resolved, and files can be downloaded from the “Completed” queue.
Enhancement
App Integrations: Robility Doc Intelligence has been renamed to Robility Copilot. Click here to learn more.
1.7.12 v.25.4.0.2
This update introduces key enhancements to optimize resource management and enhance automation capabilities.
Enhancements
1. Revamped Resource Management
The Resources page has been redesigned to improve efficiency at the tenant level. Users can now assign a single machine to multiple projects, enabling centralized resource management and optimizing utilization.
Click here to learn more about resources.
2. Harmony AI – Gen AI Integration
This release integrates Gen AI into Harmony AI, enhancing automation with advanced intelligence. The model streamlines complex workflows by handling dynamic and cognitive tasks, reducing the need for human intervention.
Click here to learn more about HarmonyAI.
3. Deploy Robots – License Validation
The Deploy Robots page has been enhanced with validations tied to the license key status. It now displays the last seen active timestamps for each machine, providing improved control and visibility during deployment.
Click here to learn more about deploying robots.
4. License Page – Harmony AI Activation Status
The License page now enables the activation status of Harmony AI licenses, which provides the validity and usage across projects. Click here to learn more about license management.
5. Scheduler Calendar – Unified View
The Scheduler Calendar now features a unified view of all scheduled items, includes end date validation aligned with the tenant’s expiration, and uses color-coded indicators to highlight scheduler or bot-related issues, enhancing visibility and scheduling control.
Click here to learn more about the scheduler.
1.7.13 v.25.2.0.0
In this major release, the RobilityManager will support cross-platform compatibility, providing several advantages, especially in terms of performance, flexibility, and scalability.
What’s New
1. Cross-Platform Functionality – Robility AI runs seamlessly on Linux, macOS, and Windows, offering your organization the flexibility to deploy on your preferred systems.
2. Optimized Performance – The Robility AI Manager has been fine-tuned to reduce latency, ensuring smoother and faster automation workflows.
3. Cloud-Ready Integrations – Improved compatibility with top cloud platforms simplifies deployment and scaling, making it easier than ever to leverage cloud solutions.
Bug Fixes
1. Schedulers: Previously, when a single machine was connected to multiple projects, the scheduler triggered regardless of the mapped project. Now, removing a machine from a project also removes its associated scheduler, preventing unintended triggers.
2. System exception retry validation: Previously, retrying cases from the System Exception queue in Designer was unsuccessful due to an exception. Now, users will receive a notification preventing them from retrieving cases from the system exception queue from the runtime. Instead, cases must be manually back pushed in Robility Manager.
3. Designer activation issue:
Previously, there was an issue with character length when activating the designer from Robility Manager. This issue has now been resolved, allowing seamless activation.
Release Date: 12-Feb-2025
1.7.14 v.24.11.0.32
This version 24.11.0.32 addresses critical issues in Robility Manager and enhancements to improve your experience and streamline processes within our platform.
Enhancements
Export to excel option: We have introduced the Export to Excel functionality on the Invite Users and Roles and Users pages to enhance usability and data management. This feature enables you to easily download the user list displayed on these pages in an Excel format.
Email Notification: We have introduced an enhanced email notification system to keep tenant admins informed about user invitations. When a tenant admin invites a user to the platform, they will now receive an email notification as soon as the invited user accepts the invitation.
Interact Review screen – The review screen in Interact has been upgraded to refresh automatically every minute. This improvement ensures the session remains active, preventing expiration and maintaining a seamless user experience.
Bug Fixes
1. Interact Workflow:
Resolved an issue where the Import option was unavailable during the initial configuration of Interact. This option is now accessible as expected.
2. Scheduled Reports: Fixed an issue where the configured email address would disappear after saving a scheduled report. The email address now remains intact.
Known Issues
1. Queue Configuration: Attempting to “Save/Update” all queues simultaneously during project configuration may result in an unresponsive warning message. This issue occurs only when the total number of queues exceeds eight.
2. Invite User Page: If a user’s role is updated at the project level, the Invite User page does not display the list sorted by the updated date
3. Bulk Case Upload with Multiple Queue Movements: Bulk case uploads are not supported when multiple queue movements are configured for a single transaction in business rules.
a. Example: If a transaction progresses through stages such as Index → Fetch → Process → Complete with specific conditions, bulk uploads will fail to process.
4. App Integration API Key: For existing projects, the API key required for App Integration may be missing. This can result in an error message such as “Invalid grant: Interact API key is empty” when accessing the App Integration page.
Workaround: Navigate to the project, click on “Edit” against the project and save it again to regenerate the API key.
Released date: 02-Dec-2024
1.7.15 v.24.10.0.56
v.24.10.0.56
This version 24.10.0.56 addresses critical issues in Robility Manager and enhancements to improve your experience and streamline processes within our platform.
Enhancements
1. App Integrations: We have implemented a “Refresh Token” method for connections, enabling tokens to renew automatically upon expiration without requiring any manual intervention.
2. Pagination: To improve navigation through the pages with ease, we have implemented pagination on the following pages:
a. Templates
b. Template History
c. Projects
d. Resources
HarmonyAI – Document Understanding: We’ve introduced a “JSON Viewer” for fields in HarmonyAI’s Document Understanding, allowing output to display in a well-formatted JSON view for easier readability.
Bug Fixes
1. License Page – The License count for Occupied, Available and expired was incorrect earlier. Now, this has been fixed and the counts are displayed accurately.
2. App Integrations –
a. Previously the “Search box” in App integrations page had some default characters whenever the page was loaded, now this has been removed.
b. Previously, deleted connections were not removed from the grid. This issue has now been fixed.
3. Project Expiration – Previously, the production team faced an issue while trying to retrieve the credentials from the credential vault, an exception was thrown as the project expired. Now, we have removed the project expiration logic.
4. Harmony AI – Previously, the business rules created against “Document Understanding” in HarmonyAI was working since a field was missed. Now, we have fixed this and the transactions are moving successfully.
5. Project Configuration –
a. SearchBox – Previously, if the “Enable Search” box was checked for a textbox field type and when we change field type, the box remained checked for other field types. This issue has now been fixed.
b. The “Maximum size” field was not getting cleared and disabled to make any changes. Now it has been fixed.
c. When updating the Master data in Interact, it was not saved properly. Now it has been fixed.
6. Deploy Robots –
a. Previously, the “Runner” status would not be updated and stays in the “Run Initiated” state even if the license has been disconnected in the machine. Now, If the “Run Initiated” status is active for more than 3 minutes after selecting the “Run” option, it will now automatically switch to “Not Connected” status.
b. Earlier there was a slowness while editing the robots in deploy robots page, now it has been addressed.
c. Previously, attempting to add a new robot in “Deploy Robots” after removing resources would not allow the addition, even when resources were available. This issue has now been fixed.
Known Issues
1. When you are trying to “Save/Update” all the queues at same time during the project configuration, the page may show an unresponsive warning message. It occurs only when the overall number of queues exceed more than 8.
2. The “Invite User” page does not display the list in the correct order when roles are updated at the project level.
3. If multiple queue movements are configured for a single transaction in the business rules, uploading bulk cases will not be supported.
Example: If a transaction moves through stages like Index → Fetch → Process → Complete with specified conditions, cases uploaded in bulk will not be supported.
4. For existing projects, the API key for App Integration may be missing. As a result, accessing the App Integration page may display an error like ‘Invalid grant: Interact API key is empty.’ To fix this, please click “Edit” for the project and save it again.
Released date: 4-11-2024
1.7.16 v.24.10.0.24
v.24.10.0.24
This version 24.10.0.24 addresses critical issues in Robility Manager and enhancements to improve your experience and streamline processes within our platform.
Enhancements
Performance optimization:
To optimize performance and provide a more customized view without latency issues, we have implemented the below functionalities on the “Interact” pages instead of the “Eye” filter option.
1. Custom Field Search: The custom field search functionality has been implemented across all the pages in Interact, allowing to configure “Search” for any two fields during project setup. This option supports only textbox field types.
2. Pagination: Additionally, we have implemented pagination in the following pages:
a. URN Management
b. Reports
c. Queues
3. Search functionality: The search bar has now been implemented in the “Reports” page as well which helps the user to search and export the required data.
Auto Renewal for Designer and Runner:
Previously, licenses were reassigned using a FIFO model, which led to allocation of existing licenses that are closer to expiration even though new licenses have been acquired.
To address this, we have enhanced the license allocation logic for Designer and Runner. The system now prioritizes licenses with the longest remaining duration during renewal.
Bug Fixes
1. Roles and Users: The screen used to freeze whenever a user attempted to map or select any user in the “Select users” option without specifying a role. This issue has been fixed, and the screen now functions properly.
2. HarmonyAI Icon: Below are the issues that have been addressed on “HarmonyAI”.
a. The HarmonyAI icons were enhanced.
b. Previously, the values provided in the “Advance Settings” of the “AI Agent” were not properly passed to the Harmony AI service. This issue has now been resolved, and the values are available as a separate field called “Queue_name_Params.”
3. URN Management – History: In the previous version, the History page only displayed checkboxes instead of hyperlink option. Now, the checkboxes have been replaced with hyperlinks, allowing users to access the corresponding URN data directly.
4. Live Report: Below are the issues that have been addressed on the Live Report page:
a. Headers in the Live Report were misaligned, and columns did not resize properly if the name contained more characters. All headers are now uniformly aligned.
b. A double loader used to appear whenever an input was provided in the search box and when navigating to the next page using pagination options. This issue has been fixed, and the double loader no longer appears.
c. When no transactions were available, the history of Live report would display ‘Showing entries.’ This has now been fixed.
5. Search Box: Previously, if the user entered specific input in the search box on the “Reports” page, the results were irrelevant, returning all values. The search functionality has now been fixed to retrieve and provide accurate results.
6. Resource Management: The “Updated By” column was not correctly updating when users edited machine names. This issue has been addressed, and the column is now properly updated.
7. Queue Name Duplication: Users were able to create the same queue name in two different sections (e.g., Processing and Exception), leading to duplicate names. Validation has now been implemented to prevent duplication, ensuring only unique names are allowed.
8. Queue Access Update: When users tried to provide or update field/queue access, they were unable to do so due to a warning message saying, “Queue already exists.” This issue has been fixed, and the queue can now be updated without an error.
9. Key Vault – Azure Secret Expiry: If the client secret key provided in the “Azure Key Vault” was expired, no proper warning message was displayed. Now, this has been resolved with a proper warning message.
10. Credential Vault – Below are the issues that have been addressed on the credential vault page:
a. In previous versions, the expiration date for new credentials exceeded the tenant’s expiration date. Now, validation ensures that the credential expiration date does not surpass the tenant’s expiration.
b. The ‘Lock/Unlock’ status was incorrectly displayed for newly created credentials. This issue has now been resolved.
11. Bulk Upload – Popup Issue: During the bulk upload process, if the user canceled or closed the process, the popup to upload again would not appear. This issue has been fixed, and the popup now functions correctly after canceling or closing.
12. Deploy Robots – Below are the issues that have been addressed on the Deploy robots page:
a. Using the same machine name for different license types, such as Unattended and High Density, caused the page to keep loading indefinitely. This issue has been resolved, and the page now loads correctly.
b. The filter functionality was not working, now it has been fixed.
13. Scheduler: In LSC environment, users were unable to schedule robot via scheduler due to the time gap in the scheduled time. Now, the issue has been fixed and the scheduler now functions properly.
14. The search functionality has been fixed to prevent triggering on every key press and now includes both a search and clear icon for improved usability.
15. All queues and reports have been aligned to display a uniform column structure for consistency.
16. All the unassigned fields were displayed in the queue while adding the cases manually, now it has been fixed.
17. Business Rules – The priority order used to change with every update, causing the bot to improperly move transactions. This issue has now been resolved.
Known Issues
1. When you are trying to “Save/Update” all the queues at same time during the project configuration, the page may show an unresponsive warning message. It occurs only when the overall number of queues exceed more than 8.
2. The “Invite User” page does not display the list in the correct order when roles are updated at the project level.
3. If multiple queue movements are configured for a single transaction in the business rules, bulk upload cases will not be supported.
a. Example: If a transaction moves through stages like Index → Fetch → Process → Complete in a single process, cases uploaded in bulk will not be supported.
Released date: 14-10-2024
1.7.17 v.24.8.0.26
v.24.8.0.26
This hotfix release addresses key issues in Robility Manager, including enhancements to the search functionality on the Interact workflow page and improvements in managing user access.
Bug Fixes
1. Search Functionality on the Interact Workflow page – Previously, users faced difficulties reviewing transactions on the Interact page due to the lack of a search option, making it challenging to locate and review specific URNs. We have now implemented a search box, enabling users to easily search with specific data.
2. Roles and Users at the Project Level – The following issues have been addressed on this page:
a. User Search in Drop-Down Menu: Users were unable to search and select specific users when mapping roles. Now, users can search for names and provide access more efficiently.
b. “Select All” Option: The “Select All” option did not work when the list contained more than 20 users. This issue has been resolved, and the “Select All” option will be disabled if the user list exceeds 20.
c. Filtered User List: The user list will now only display users who do not already have access to the selected role.
Known issue
1. Business rule – The “Copy” functionality will only work when the source and destination fields are of the same field type.
2. Currently we have not implemented multiple queue movement when indexing the transactions via BulkIndex option.
3. If the user’s role is updated at the project level, the Invite User page does not display the list in order of the updated date.
Released date: 16-09-2024
1.7.18 v.24.8.0.25
v.24.8.0.25
This version 24.8.0.25 addresses critical issues in Robility Manager and enhancements to improve your experience and expand your capabilities on our platform.
What’s New
App Integrations(beta): With Robility’s App Integrations, you can effortlessly connect with various software applications. Share data and functionalities to create a smooth, interconnected workflow. It helps you to streamline the setup and management of third-party connections with standardized authentication. This is exclusively available for integrating with Zendesk, simplifying and securing your automation processes—all in one convenient place.
HarmonyAI: We’re thrilled to unveil a major transformation in HarmonyAI’s Playground, set to elevate your prompt responses to new heights. But that’s not all—our AI services have reached the next stage with the integration of Google Vertex AI and enhanced text moderation capabilities.
Enhancements
1. Improved Performance – To boost performance in Reviews, URN Management, and Reports, we’ve introduced pagination. This will enhance loading times and streamline navigation through large datasets.
Bug Fixes
Sign up – Users were previously able to sign up using links that had expired for more than 48 hours. We’ve fixed this issue, so now, expired links will no longer grant access, ensuring a secure and timely signup process.
Template – Alerts for activating and deactivating templates now appear immediately, without needing to refresh the page. This ensures you get prompt notifications about your template status.
Settings –
1. License Page –
a. We’ve resolved the issue where you couldn’t send a Tenant license request due to an error asking for a license count. You can now submit requests without any problems.
b. Previously, old license details would appear on the “Buy License” page. This has been fixed, so you’ll see only current information when you’re ready to purchase.
2. Features – All previously mapped and available versions of Designer & Runner were not showing up. This issue has been fixed, so you can now see and access all versions as expected.
Credential Manager-
a. Lock/Unlock status – Earlier there was a glitch on updating the details and status of the credentials, now every time you utilize the credential through Designer, the Lock/Unlock status in the Manager’s Action Category will mirror your actions perfectly.
b. Expiration date – Previously, you could provide past the 90-day limit when updating or adding new credentials. Not anymore—now, everything is in line, keeping your credentials secure and compliant.
c. History – Previously, the history option will list out all the details for more than 24hours. Now, user details will vanish right on schedule, 24 hours later, just as they should.
Business rules –
a. We’ve tackled an issue where you couldn’t update and save a new condition in an existing business rule. Previously, trying to save would throw an error, especially when there was only one rule in the project. Now, updates save effortlessly—no more errors!
b. The “Else” condition was mandatory before, causing transactions to fail if the rule wasn’t met. We’ve made it optional, allowing for a smoother transaction process.
c. Previously, when using text fields with conditions like “Less than,” “Greater than” or “Greater than or equal to,” in the business rule, the transactions were not updated and throwed an error. Now, we have fixed that glitch, so now you can index queues.
Roles and Users –
a. We’ve resolved the issues where clicking outside the “Select Users” field would clear your selections, leading to unnecessary warning messages. Now, your selections stay intact, even if you navigate away and return.
b. The “Select All” feature now works reliably, displaying the correct count of selected users. No more mismatches between the displayed count and actual selections.
Interact –
a. Special Characters – Now Fully Supported: Earlier when the “UNICODE” characters were provided in the field values, it was not accepted. Now, All special characters are seamlessly handled in Interact, ensuring a smooth experience with varied inputs.
b. Picture Field – ‘Fit to Screen’ Fixed: We’ve resolved the issue with the “Fit to Screen” option for images in the “Picture” field. It now works as expected, giving you a perfect fit every time.
c. Drop down field – Previously, there was no status indication for dropdown values uploaded to Excel. We’ve added clear status notifications, so you know exactly when your upload is completed.
d. Queue Inactivation – When a queue was inactivated, you could still copy “Json” and “Attachment details.” This has been fixed to ensure proper access controls.
e. Queue Details Display – The copy icons for Json and attachment fields were mistakenly enabled for Completed and Business Exception Queues. This has been corrected to match appropriate permissions.
f. Project Configuration Page –We’ve fixed the loading issue on the Interact Project Configuration page, so you can access your configurations without delays.
g. Invalid Rule Conditions –Adding invalid rule conditions used to cause confusing alerts. Now, you’ll see a clear “Rule not satisfied” message for better clarity.
h. Field Access –You can now select only one option between Show & Edit in the Interact Field Access settings, ensuring clearer permissions.
i. User & API Access Checkboxes –We’ve corrected the header checkbox issue, ensuring that selections for User and API Access are accurately reflected.
j. Field Name Matching Issue –If you named a field the same as its type (like “Group”), the page would get stuck loading. This has been fixed for smooth transaction additions.
k. Bulk Index Loading –After a successful file upload, Bulk Index used to keep loading indefinitely. This issue is resolved, ensuring that you can proceed without unnecessary delays.
l. Master Data –If you deleted master data and tried to add new data, it used to overwrite the existing records. This has been fixed to avoid unintentional overwrites.
m. Queue Details –When you click on a queue and use the copy icons for Json, Attachment Fields, or Table Names, you’ll now clearly see which details were copied, fixing previous visibility issues.
n. Project Configuration Save – “Saved successfully” message now appears correctly after saving changes in the Project Configuration page, and clicking during the loading phase no longer disrupts the process.
o. Review Page Headers – Unchecking headers in a queue and then refreshing causes all headers to appear selected, but none are visible in the grid; switching queues and returning restores the headers. Now it has been resolved.
p. Queue Access Options – Previously, when providing API access for the queue was not reflecting and resulted in exception. Now you can update and save changes to queue access options correctly, even when API access is provided
Deploy Robots –
a. Edit Option –The “Edit” option was previously available even when the machine was in an “IDLE” state. We’ve updated this so that the “Edit” option is now disabled in the “IDLE” state and will only be enabled if the machine moves to a “not connected” or “faulted” state.
b. Resolution Settings –Users could previously save and submit resolution settings for “W/H” set to the maximum allowed values. This issue has been resolved to prevent saving and submitting with such settings, ensuring optimal resolution management
Known issue
1. Business rule – The “Copy” functionality will only work when the source and destination fields are of the same field type.
2. Currently we have not implemented multiple queue movement when indexing the transactions via BulkIndex option.
Released date: 26-08-2024
1.7.19 v.24.7.0.13
v.24.7.0.13
This version 24.7.0.13 addresses critical issues in Robility Manager and enhancements to improve your experience and expand your capabilities on our platform.
What’s New
HarmonyAI(beta): Dive into the world of AI-powered automations with HarmonyAI, Robility’s standalone platform. Imagine creating agentic automations that learn from your data, make decisions, and execute bot tasks across your automation solutions—all without needing to be a machine learning expert.
Experience the ultimate flexibility and power with seamless integrations of major cloud platforms like Azure and Google.
MarketPlace (beta): The Robility Marketplace will serve as a comprehensive platform, providing a broad selection of connectors and reusable RPA templates developed by seasoned experts and practitioners. It acts as a hub for top-tier RPA solutions, featuring integration packs, automation components, and readymade automation workflows. These resources are designed to expedite and expand automation initiatives across organizations.
Co-pilot(beta): Revolutionize your transactions with the new Co-pilot integration in RobilityManager. This cutting-edge AI assistant is designed to enhance your productivity and ensure the highest standards of accuracy and clarity in every transaction review.
Imagine an AI assistant helping you summarize, review, and spell-check your transactions—amazing, right? Discover how Co-pilot minimizes your routine tasks and maximizes efficiency.
AzureKeyVault: Unlock the next level of security with Robility Manager’s cutting-edge feature for safeguarding your most sensitive information. Imagine effortlessly storing secrets, passwords, and files for each tenant, leveraging the unmatched security of Azure Key Vault and Blob Storage.
Discover the power of robust security measures that adapt to your needs, without compromising on accessibility or performance. Learn more and take the first step towards impeccable data security with Robility Manager.
Business Rules: Boost decision-making and streamline your workflows with Robility’s powerful, low-code rule engine. This engine offers seamless integration capabilities, allowing you to manage complex logic and deploy rules with ease.
Enhancements
1. History Option: Utilize the “History” option within the following menus to enhance security and monitor user’s usage This option is exclusively available for:
a. Credential Vault
b. Workflows
2. Queue Enhancement: The “Queues” that are displayed in the “Interact workflow” has been vamped to show the queues based on the configured group type.
Bug Fixes
1. An exception was thrown when publishing the workflow from designer due to mismatch of the versions. Now it has been addressed.
2. Sign Up page – Resolved the issue where it displayed “Object Object error” exception message when attempting to sign up for the Robility Manager.
3. Resource – Unable to remove the machine even when the machine was disconnected and deleted from the deploy robots page, now it has been fixed.
4. Workflow Page –
a. In the workflow page, we have resolved alignment issues where the header was not properly aligned, and the workflow list grid size was changing whenever the ‘View’ button was clicked.
b. Addressed the ability to download workflows when it was in “Inactive” state.
c. The “Check update” button remained enabled after checking workflow updates, now it has been resolved.
5. Business Rules –
a. Business Rule Queue Issues: Previously, when an existing rule for the queue was deleted, attempting to add a new rule with the same queue would result in an exception being thrown. This issue has now been resolved.
b. Else Destination and Condition Value Field: Addressed the Else Destination issue where if two rules contained the same destination queue in ‘Else,’ only one rule would be updated, and the other would not retain the same destination queue.
c. Loader issue – Faced the loading issue when switching between rules, now it has been addressed.
d. Deleted Fields – The deleted fields were available when creating new rules. This issue has now been addressed.
e. Fields in dropdown – Even before choosing the source queue, the fields were displayed in the drop-down in the “If Part”, now it has been addressed.
6. Interact Workflow –
a. Bulk Index Transactions: Previously, the business rule was not working when transactions were uploaded through bulk index. This issue has now been fixed.
b. Email Notification: The “From Process Queue” name in triggered emails was incorrect. This has now been corrected.
c. Add Transaction: Previously, adding transactions for a project was not possible. This issue has been addressed by making changes to the database.
d. MasterData: The MasterData file was not deleted previously, now this issue has been addressed.
Known issue
1. Business rule – The “Copy” functionality will only work when the source and destination fields are of the same field type.
2. Currently we have not implemented multiple queue movement when indexing the transactions via BulkIndex option.
Released date: 15-07-2024
1.7.20 v.24.5.1.1
v.24.5.1.1
This release includes bug fixes to improve your experience and expand your capabilities on our platform.
Enhancements
1. Project – Roles & Users: The drop-down in “Select Roles” within the project level was not visible to users. This issue has now been fixed.
2. User Management – When a user is invited as “Tenant Admin,” the default role “User” was not being selected for the respective user upon first sign-in. This issue has now been fixed.
3. Invite Page – Previously, both “RPA Developer” and “Tenant Admin” roles were being provided to the user by default. This issue has now been fixed.
4. Resolution Settings – The resolution was not changing according to the workflow, and manually inputted values were not being reflected upon saving. This issue has now been fixed.
Limitation
OCR & Entity Extract Review Page: Enhancements are currently in progress.
Known Issues
1. When user system’s display scale is set as 125%, the scroll bar option is not available in the Interact menu.
2. Robility Manager is getting logged out too soon when the user is inactive on the page.
3. While saving/updating inside the interact configuration page, it shows unresponsive warning message.
Released date: 28-05-2024
Hotfix Release
This hotfix release addresses critical issues in Robility Manager, including the timeout issue on the Interact page and the failure of email triggers for transaction movement in the LIVE environment.
Please note that this “Hotfix release” has been implemented into the existing version 24.5.1.1 of RobilityManager.
1. Timeout Issue on Interact Page: Users experienced timeouts when reviewing the transactions in the Interact page. Now we have fixed the issue by impementing optimizations and handling the process in the backends.
2. Email Trigger Failure: Emails were not being triggered upon creating or updating the transactions to any other queues in the LIVE environment. Now it has been rectified and the emails will be triggered automatically.
Released date: 04-07-2024
