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.