> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/release-notes/boston-edition/boston-4.4.0.md).

# Boston 4.4.0

📅 Release Date: March 14, 2025 - 📅 Next Release Date: - May 12, 2025

## **🚀 Highlights of this Release** 

{% hint style="warning" %}

* **Graphical Interface Control:** Role Management initially enables **menu visibility management** in the **left navigation pane**.
* **Customizable Menu Visibility:** Administrators can define which menus and menu items are **visible** based on assigned roles.
* **Future Enhancements:** **Role-based content access control** will be introduced in upcoming releases to enhance permission granularity.
* **Role-Based Usage Examples:**\
  ✔ **If View access is granted** to the **Dashboard menu**, all dashboards will be visible.\
  ❌ **If View access is disabled**, the Dashboard menu will be completely hidden.\
  ✔ **If Read access is enabled** for the **Automs menu**, all Automs will be visible.
  {% endhint %}

{% hint style="danger" %}
⚠ **Note:** Currently, Role Management applies only to the left navigation pane. **More advanced role-based access control features** will be introduced in future updates.
{% endhint %}

***

{% hint style="info" %}
**🔔 Info**

* **Improved Clarity for RESTful Errors**: Enhanced error logging to ensure detailed output for RESTful responses. This improvement simplifies debugging by making error messages more informative and actionable.
* **Flexible Log Retention Options:** Users can now choose a log retention period of **7, 15, or 30 days**, with **7 days set as the default**. However, archived logs will always be stored for **30 days** before being automatically deleted.
* **Email Notifications for Archives:** Users can specify an **email address** to receive notifications when logs are archived. If left blank, the notification will be sent to the **email registered in the license**. If the **Mail Server** is not configured, notifications will be available only in the **Dashboard’s notification panel**.
* **Downloadable Archive Links:** Email notifications include a **download link**, which requires logging into **Autom Mate** to start the download. Users can also manually download archived logs from the **Archives section** in the **Dashboard**.
* **On-Premises Archive Path Management:** **On-premises users** have an additional setting under **Log Retention Settings** to define the folder where archived logs are stored. If changed, **new archives** will be saved in the updated folder, but **old archives will remain in the previous folder**. It is **not recommended** to manually move archive files.
  {% endhint %}

***

{% hint style="warning" %}
**⚠️ Warnings**

* **Database Max Connection Error Crashing DB Microservice**: Previously, exceeding MySQL's maximum connection limit could cause the database microservice to crash. This issue has been resolved, but **it is recommended to monitor database connection usage** and ensure connection pooling is optimized to prevent resource exhaustion in high-load scenarios.
* **Disabled Autom Schedule Error**: The issue where schedules for disabled Autom instances were not halted has been fixed. However, ensure schedules are reviewed for accuracy when enabling or disabling Autom instances to maintain workflow integrity.
* **Export to CSV Default Value Error:** Fixed an issue where the **Export to CSV** action in the data table library would fail if a variable had a default value assigned.
* **Xurrent GraphQL Character Issue:** Resolved an issue where certain text characters prevented operations from being executed in the **Xurrent GraphQL** action.
* **Data Manager Second Step Issue:** Fixed an issue where the second step in **Data Manager** workflows, such as **Jira Create Issue** or **ServiceNow Update Records**, was not being processed.
* **Log Retention**: Default retention is set to **7 days**.
* **Log Retention**: If no email is provided in the **notification field**, log archive notifications will be sent to the **email address defined in the license**. If your instance’s **Mail Server settings are not configured**, notifications **will not be sent via email** and can only be viewed in the **Dashboard’s notification panel**.
* **Log Retention**: Ensure that your **Mail Server settings** are properly configured to receive email notifications for archived logs. If you want notifications to be sent to a specific email, enter it in the **notification field** to override the default behavior.
  {% endhint %}

***

### **🅱️ Bug Fixes**

#### 📌 [**Refresh Token Issue on Azure DevOps**](#refresh-token-problem-on-azure-devops)

Resolved an issue where expired tokens returned an unexpected status code, causing refresh token functionality to fail.

#### 📌 **Missing Integration Logo**

Resolved an issue where the integration logo was not displaying as expected.

#### 📌 [**Disable Autom Run Issue**](#disable-autom-run-issue-1)

Resolved an issue where disabled Autom instances could still be executed via the "Run Autom" option in the drop-down menu when scheduled triggers were configured.

#### 📌 [**Database Max Connection Error Crashing DB Microservice**](#database-max-connection-error-crashing-db-microservice-1)

Resolved an issue where exceeding MySQL's maximum connection limit caused the database microservice to crash during high connection usage.

#### 📌 [**Improved Clarity for RESTful Errors**](#improved-clarity-for-restful-errors-1)

Resolved an issue where RESTful errors were unclear due to missing error details in the output field when responses from the service were not properly logged.

#### 📌 [**Dynamic List Issue in MS Teams**](#dynamic-list-issue-in-ms-teams-1)

Resolved an issue where the dynamic list functionality in MS Teams did not update correctly, causing inconsistencies in displayed data.

#### 📌[ **Action Label Length Issue**](#action-label-display-issue)

Resolved an issue where long action labels were not truncated properly in the UI, causing display inconsistencies after import.

#### 📌 [**Error Configuration "Go To" Action Issue**](#error-configuration-go-to-action-issue-1)

Resolved an issue where the "Go To" action in error-configured scenarios failed to execute properly within Autom, causing disruptions in workflows.

#### 📌 [**Disabled Autom Schedule Error**](#disabled-autom-schedule-error-1)

Resolved an issue where schedules for disabled Autom instances were not stopped, causing erroneous behavior and misleading error logs.

#### 📌 [**Default Value Update for Webhook and API Trigger Parameters**](#default-value-update-for-webhook-and-api-trigger-parameters-1)

In **Boston 4.4.0**, if an **Autom** has never been triggered via API before, the `##triggerParam##`, `##triggerHeader##`, and `##triggerQuery##` values will now default to `{}` instead of `null`.

#### 📌 [**Fix for Expired Client Credential Password Refresh**](#fix-for-expired-client-credential-password-refresh-1)

In **Boston 4.4.0**, an issue has been resolved where an **Autom** using an expired client credential password failed to refresh the password via the refresh token mechanism.

#### 📌 [Resolved Business Impact Estimator Data Handling Issues](#resolved-business-impact-estimator-data-handling-issues-1)

Business Impact Estimator data was not updating properly when edited. Optimized data handling to ensure smooth calculations and updates.

#### 📌 [Fixed Data Persistence in Business Impact Estimator](#fixed-data-persistence-in-business-impact-estimator-calculator)

Some saved calculations were not retained after page reloads. Improved persistence mechanisms to ensure data remains intact.

#### 📌 [Validation & Sorting Fixes](#validation-and-sorting-fixes-1)

Some required fields were missing in Business Impact Estimator. Implemented validation rules to ensure completeness before saving. Business Impact Estimator reports did not always sort correctly. Adjusted sorting logic to prioritize total value sorting correctly.

#### 📌 [Resolved Invalid Filename Error During Delete File Operations at Mate Drive](#resolved-invalid-filename-error-during-delete-file-operations-at-mate-drive-1)

Fixed an issue where project creation would fail due to invalid characters in file or folder names.

***

### **🛠️ Enhancement**

#### 📌 [**Updated `created_at` Logic for Pending Operations**](#updated-created_at-logic)

Modified the logic for setting the `created_at` field of pending operations to reflect the actual start time of the operation instead of the time it was moved to the pending state.

#### 📌 [**Filter Button and Input Field Enhancements**](#filter-button-and-input-field-enhancements-1)

We have introduced a refined **filter button design** along with improved placements for **Multiselect** and **Contains** input fields. These changes enhance the usability and clarity of the filtering process, providing a more intuitive experience.

#### 📌 [**Filter Indicator for Applied Filters**](#filter-indicator-for-applied-filters-1)

In **Boston 4.4.0**, when a user applies a filter, an **indicator chip** will now appear below the tabs, displaying the applied filter. This chip includes an **edit button, a delete button, and the number of filtered columns**, enhancing visibility and user control overactive filters.

#### 📌[ **Enhancements to Dashboard Widgets: Description, Time Range, and Symbols**](#enhancements-to-dashboard-widgets-description-time-range-and-symbols-1)

In **Boston 4.4.0**, **dashboard widgets** have been improved with the addition of **descriptions, time range indicators, and symbols**. These enhancements provide users with better context and a clearer understanding of widget data.

#### 📌 [**Custom Token Refresh Status Code for OAuth 2.0 Connections**](#custom-token-refresh-status-code-for-oauth-2.0-connections-1)

In **Boston 4.4.0**, a **Token Refresh Status Code option** has been added to the **OAuth App Library** for **OAuth 2.0 connections**. This enhancement allows users to define custom status codes that indicate an expired token, ensuring proper token refresh handling for different applications.

#### 📌 [Better Data Accuracy & Validation](#better-data-accuracy-and-validation)

Stronger validation rules to prevent incomplete or incorrect entries. Automated record updates for real-time accuracy. Reports now sort correctly based on total value. Prevents data inconsistencies and ensures precise financial reporting.

#### 📌 [Default Dashboard Enhancements](#default-dashboard-enhancements)

"Estimated Saving Report" is now pre-configured in the default dashboard. A database migration script ensures consistency across environments. Ensures easier setup and improved visibility of Business Impact Estimator reports

***

### **✨ New Features**

#### 📌 [**Added `started_at` Field for Operation History**](#added-started_at-field-for-operation-history-1)

Introduced a new field, `started_at`, in the operation history to display the actual start time of the operation.

#### 📌 [New Business Impact Estimator Reports for Enhanced Financial Insights](#new-business-impact-estimator-reports-for-enhanced-financial-insights-1)

1. New Reports Added:
   * Estimated Cost Reduction
   * Estimated Revenue Generation
   * Estimated Risk Avoidance
   * Estimated Saving
   * Estimated Time Saved
2. New Grouping & Filtering Capabilities
3. Multiple Chart Views Supported: Column, Bar, List View, and Pie Chart
4. Default Dashboard Update: "Estimated Saving Report" added to the default dashboard.

#### 📌 [Enhanced Business Impact Estimator Data Management & Calculations](#enhanced-business-impact-estimator-data-management-and-calculations-1)

1. Optimized Business Impact Estimator Tracking:
   * More accurate cost reduction, time savings, and revenue generation metrics.
   * Improved data validation and record handling.
2. New Business Impact Estimator Calculation Metrics:
   * Total Cost Reduction
   * Total Estimated Time Saved
   * Total Revenue Generation
   * Total Risk Avoidance
   * Total Estimated Saving
   * Revenue Generation Driver
   * Lost Revenue Avoided
   * Fines Avoided

#### 📌 [Redesigned Business Impact Estimator Calculator UI & Functionalities](#redesigned-business-impact-estimator-calculator-ui-and-functionalities-1)

1. Improved UI for Seamless Navigation
2. New Functionalities:
   * Save, edit, and update Business Impact Estimator data dynamically.
   * Validation checks ensure completeness before saving.
   * Direct navigation to Business Impact Estimator documentation.
   * Real-time data retrieval for accuracy.

#### 📌 [**Log Retention**](#log-retention-1)

The **Boston 4.4.0** release introduces a **new Log Retention system**, enhancing log management by allowing **automatic archiving, retrieval, and scheduled deletions**. This feature provides **better control over log storage**, **improves system performance**, and ensures **efficient data retention policies**.

Key highlights:

* **Log Archiving and Retention Configuration**: Define how long logs are stored and where they are archived.
* **New Log Retention Page**: Manage retention settings through an intuitive UI.
* **Automated Archiving and Deletion**: Logs are **archived and deleted** based on configurable retention periods.
* **Audit Trail for Log Actions**: All archiving and deletion actions are **tracked for accountability**.
* **Download Archived Logs**: Users can **retrieve archived logs** on demand.
* **Log Retention Management:** Users can now manage their **log retention schedule** and specify a **file path** for storing logs.
* **Email Notifications for Archived Logs:** Users can enter an **email address** to receive notifications about archived logs. If no email is provided, notifications will be sent to the **license-defined email** or displayed in the **notification panel** if the mail server is not configured.

#### 📌 [**Monitoring Filter**](#monitoring-filter-1)

The **Boston 4.4.0** release introduces the **Monitoring Filter**, an advanced filtering feature that allows users to **apply, modify, and manage filters more efficiently** within the Monitoring page. This feature provides:

* **Advanced Filtering Capabilities**: Users can now apply **multi-select, date range, and text-based filtering** to refine their monitoring results.
* **New Monitoring Filter Modal**: A **centralized filtering interface** with predefined filter fields.
* **Filter Persistence and Management**: Users can **save, edit, and delete filters**, making monitoring more customizable.
* **Improved UI/UX**: A streamlined design that integrates filtering directly into the **Monitoring page** for **better usability**.
* **Enhanced Search Functionality**: A **global search** applies the "contains" filter across all columns.

These improvements enhance **visibility, usability, and efficiency in monitoring operations**.

#### 📌 [**Role-Based Access Control (RBAC) System**](#role-based-access-control-rbac-system-1)

The **Boston 4.4.0** release introduces **RBAC as a new feature**, providing **secure, structured, and efficient access management** across the platform. With **dynamic UI updates, centralized permission control, and optimized query performance**, this system ensures **seamless and secure role-based access** for all users. This marks a significant step forward in **enhancing system security and operational flexibility**.

***

## **Detailed Version**

{% tabs %}
{% tab title=" 🅱️ Bug Solution" %}

#### **Refresh Token Problem on Azure DevOps**

When the Azure DevOps token expires, the system returns a **`203`** status code instead of the expected **`401`**. Due to this mismatch, the application fails to trigger the refresh token process, leading to authentication issues. The application logic relied on a **`401`** response to initiate the token refresh process. The unexpected **`203`** status code bypassed this logic. Updated the token validation logic to handle **`203`** status codes and initiate the refresh token process as needed. Conducted testing to ensure compatibility with both **`203`** and **`401`** status codes in various scenarios.

***

#### **Integration Logo Missing**

The integration logo failed to appear in the user interface, impacting visual consistency and user experience. The logo asset was either missing or misconfigured in the codebase, leading to a failure in rendering the logo. The logo asset was restored to the designated storage location. Code references were corrected to ensure the logo is properly displayed.

***

#### **Disable Autom Run Issue**

Users could bypass the disabled state of an Autom instance and manually run it using the "Run Autom" option in the drop-down menu when a schedule trigger was configured. The application did not check the disabled status of the Autom instance during manual execution from the menu. Logic was added to validate the disabled status before displaying or enabling the "Run Autom" option. Now, the "Run Autom" button will be disabled or hidden for any Autom marked as disabled.

***

#### **Database Max Connection Error Crashing DB Microservice**

When the `max_connections` limit in MySQL was set to a very low value (e.g., `1`), exceeding this limit caused the database microservice to terminate instead of handling the error gracefully. In one test scenario, running an Autom that created 17 simultaneous connections resulted in the microservice crashing. The database microservice did not handle MySQL connection limit errors (`Too many connections`) properly, leading to unhandled exceptions and eventual termination of the service. Enhanced error handling for database connection failures caused by exceeding the `max_connections` limit. Implemented safeguards to prevent the database microservice from crashing, ensuring proper recovery and retry mechanisms when connection limits are exceeded. Added logging and alerts to monitor connection usage and notify administrators of potential connection bottlenecks.

***

#### **Improved Clarity for RESTful Errors**

Errors in RESTful calls were classified based solely on the `statusCode` being greater than 400, without additional details about the root cause. When the response from the service was not logged into the `output` field, users were left without sufficient error information for debugging. The service response was not properly recorded in the `output` field when the field was left empty, causing a lack of visibility into error details. Enhanced error logging to ensure that all RESTful responses are recorded in the `output` field, even if the field is initially empty. Updated the system to provide clearer error messages by including detailed information from the service response in the error output. Added fallback logic to handle cases where the service response is incomplete or malformed, ensuring meaningful error messages are displayed.

***

#### **Dynamic List Issue in MS Teams**

The dynamic list in MS Teams failed to refresh or display updated data, leading to outdated or incorrect information being shown to users. The backend logic responsible for fetching and updating the dynamic list did not trigger correctly, resulting in static or stale data being displayed. Updated the dynamic list fetching logic to ensure proper triggering and retrieval of the latest data. Improved synchronization between the MS Teams interface and the backend data source to guarantee real-time updates. Conducted testing to validate dynamic list updates across various scenarios and use cases.

***

#### **Action Label Display Issue**

Action labels with long names disrupted the UI when an Autom was reimported with an excessively long name. The truncation logic was not triggered for imported action labels, leading to unrestrained text display in the UI. Adjusted the label rendering logic to truncate labels exceeding the character limit and append “...” for clarity. Improved the overall UI behavior to ensure consistent truncation of long text across various components. Introduced a character limit threshold for action labels, ensuring all labels fit neatly within the allocated UI space. Added real-time label validation during imports to prevent display issues.

***

#### **Error Configuration "Go To" Action Issue**

In Autom workflows, when an error configuration was enabled, the associated "Go To" action failed to execute. The issue did not occur when the error configuration was disabled, indicating a conflict between the error handling mechanism and the "Go To" logic. Logs displayed the error: *"The destination action in the goto action was not found."* The system could not locate the destination action referenced in the "Go To" step when error configuration was active, possibly due to a misalignment in the workflow execution sequence. Updated the workflow execution logic to ensure the destination action in the "Go To" step is properly resolved, even when error configurations are enabled. Enhanced error handling mechanisms to maintain compatibility with "Go To" actions during error-configured scenarios. Improved logging to provide clearer insights into such scenarios and aid in debugging.

***

#### **Disabled Autom Schedule Error**

When an Autom instance was scheduled while disabled (or before being disabled), the schedule was not halted. Upon reaching the scheduled execution time, the Autom instance would attempt to run, resulting in an error, and the next schedule date was not set (as expected). However, the error message created confusion, as it did not accurately represent the issue. The system allowed scheduled executions for disabled Autom instances without proper validation, leading to incorrect behavior and misleading error logs. Updated the logic to prevent schedules from triggering for disabled Autom instances. Added validation to ensure that when an Autom is disabled, any active schedules are automatically halted. Improved error messaging to reflect the actual state of the Autom instance and provide clarity.

***

#### **Default Value Update for Webhook and API Trigger Parameters**

Previously, these parameters remained `null`, causing potential integration issues when API consumers expected structured data. With this update, the default empty object (`{}`) ensures:

* **Improved API reliability**, eliminating the need for additional `null` checks.
* **Consistent data structure**, maintaining a standardized format across API-triggered executions.
* **Better integration compatibility**, preventing unexpected errors.

This change enhances **stability and predictability** in API-triggered Autom executions, ensuring smoother and more reliable workflows.

***

#### **Fix for Expired Client Credential Password Refresh**

Previously, if an **Autom** attempted to execute with an **expired client credential password**, the system attempted to refresh the password using the **refresh token**. However, this process encountered an error, causing the Autom execution to fail instead of automatically renewing the credential.

With this fix:

* When an **Autom** runs with an expired client credential password, the system will now correctly use the **refresh token** to obtain a new password.
* The **error handling process** has been improved to ensure a **seamless refresh operation** without interruptions.
* The update enhances **Autom stability**, preventing failures due to expired credentials.

This fix ensures **smoother execution** of Autom processes that rely on client credential authentication, **eliminating disruptions** caused by expired passwords.

***

#### Resolved Business Impact Estimator Data Handling Issues

Business Impact Estimator data was not updating properly when edited. Optimized data handling to ensure smooth calculations and updates.

***

#### Fixed Data Persistence in Business Impact Estimator Calculator

Some saved calculations were not retained after page reloads. Improved persistence mechanisms to ensure data remains intact.

***

#### Validation & Sorting Fixes

Some required fields were missing in Business Impact Estimator calculations. Implemented validation rules to ensure completeness before saving. Business Impact Estimator reports did not always sort correctly. Adjusted sorting logic to prioritize total value sorting correctly.

***

#### Resolved Invalid Filename Error During Delete File Operations at Mate Drive

A bug was resolved where file or folder names containing invalid characters (e.g., `:`) caused errors during project creation or deletion. The system now sanitizes file names before processing, ensuring compatibility with the file system and preventing such errors.
{% endtab %}

{% tab title="🛠️ Enhancement" %}

#### **Updated `created_at` Logic**

The `created_at` field for pending operations now reflects the start time of the operation. Previously, it incorrectly displayed the time the operation was moved to the pending state. Adjusted the backend logic to ensure that `created_at` is updated with the actual start time of operation processing. Improves accuracy in operation tracking and provides consistent data for analysis.

#### **Filter Button and Input Field Enhancements**

1. **Filter Button Design**: The filter button has been redesigned for better visibility and accessibility, ensuring users can quickly apply filters to refine their search results.
2. **Multiselect and Contains Input Placement**:
   * The **Multiselect** field now appears in a more structured layout, improving selection efficiency.
   * The **Contains** input is positioned for easier text-based filtering, aligning with best UI practices.
3. **Filtered Sections Placement**: After applying filters, the filtered sections are now displayed in a structured manner, ensuring users can easily identify the active filters and adjust them as needed.

These enhancements improve the **user experience** by streamlining filter interactions and making the search functionality more effective.

***

#### **Filter Indicator for Applied Filters**

Previously, applied filters were not visually indicated, making it difficult for users to track which filters were active. With this enhancement, users will now see a **filter chip** that clearly represents the applied filter state.

1. **Filter Chip Display**: When a filter is applied, a chip appears below the tabs, showing the number of filtered columns.
2. **Edit and Delete Options**:
   * **Edit**: Users can modify the filter directly from the chip.
   * **Delete**: Clicking the delete icon prompts a **confirmation message** before removal. If confirmed, the filter is deleted, and the UI updates accordingly.
3. **User Experience & Accessibility**:
   * The summary section is designed to be **responsive**, ensuring proper display across different screen sizes.
   * Accessibility improvements include **tooltips or labels** for delete icons to assist users in understanding their functionality.

This update enhances **filter usability**, providing a more intuitive experience by ensuring users can easily **view, edit, and remove** applied filters.

***

#### **Enhancements to Dashboard Widgets: Description, Time Range, and Symbols**

Previously, dashboard widgets lacked **key visual indicators**, making it harder for users to interpret data at a glance. To enhance usability, the following updates have been implemented:

* **Description Addition**: Each widget now includes a **description** that provides meaningful context about its displayed data.
* **Time Range Indicator**: Widgets now display a **time range** or **percentage gain** where applicable, allowing users to track data trends over time.
* **Symbol Integration**: Relevant widgets now include **symbols** to visually represent data more effectively.

***

#### **Custom Token Refresh Status Code for OAuth 2.0 Connections**

Previously, when an OAuth token expired, the system expected a **401 status code** in response to an API request. However, some applications return a different status code when a token expires, causing the automatic refresh process to fail.

With this update:

* Users can **customize the status code** that triggers a **token refresh**, instead of relying solely on `401`.
* If an application responds with a **different status code** (e.g., `403`, `498`, etc.) upon token expiration, this option allows the system to recognize it and refresh the token automatically.
* This improvement enhances compatibility with **various OAuth-based integrations**, reducing manual interventions and ensuring seamless authentication renewal.

By implementing this feature, **OAuth 2.0 connections** in the **OAuth App Library** now offer **greater flexibility and reliability**, improving **token management** for diverse API environments.

***

#### Better Data Accuracy & Validation

Stronger validation rules to prevent incomplete or incorrect entries. Automated record updates for real-time accuracy. Reports now sort correctly based on total value. Prevents data inconsistencies and ensures precise financial reporting.

***

#### Default Dashboard Enhancements

"Estimated Saving Report" is now pre-configured in the default dashboard. A database migration script ensures consistency across environments. Ensures easier setup and improved visibility of Business Impact Estimator reports
{% endtab %}

{% tab title="✨ New Features" %}

#### **Added `started_at` Field for Operation History**

Introduced a new `started_at` field in the operation history view to display the start time of Autom executions. Populates this field with the operation's start date and time. Updated the history view logic to include the `started_at` field. Ensures that the field is populated accurately based on Autom execution timelines. Provides clear and detailed insights into operation start times. Helps users distinguish between the time an operation was queued (pending) and the time it began processing.

***

#### New Business Impact Estimator Reports for Enhanced Financial Insights

1. New Reports Added:
   * Estimated Cost Reduction
   * Estimated Revenue Generation
   * Estimated Risk Avoidance
   * Estimated Saving
   * Estimated Time Saved
2. New Grouping & Filtering Capabilities
3. Multiple Chart Views Supported: Column, Bar, List View, and Pie Chart
4. Default Dashboard Update: "Estimated Saving Report" added to the default dashboard.

These reports provide better visibility into automation-driven financial impact, making Business Impact Estimator tracking more detailed and accessible.

***

#### Enhanced Business Impact Estimator Data Management & Calculations

1. Optimized Business Impact Estimator Tracking:
   * More accurate cost reduction, time savings, and revenue generation metrics.
   * Improved data validation and record handling.
2. New Business Impact Estimator Calculation Metrics:
   * Total Cost Reduction
   * Total Estimated Time Saved
   * Total Revenue Generation
   * Total Risk Avoidance
   * Total Estimated Saving
   * Revenue Generation Driver
   * Lost Revenue Avoided
   * Fines Avoided

These enhancements ensure greater accuracy and efficiency in tracking financial benefits.

***

#### Redesigned Business Impact Estimator Calculator UI & Functionalities

1. Improved UI for Seamless Navigation
2. New Functionalities:
   * Save, edit, and update Business Impact Estimator data dynamically.
   * Validation checks ensure completeness before saving.
   * Direct navigation to Business Impact Estimator documentation.
   * Real-time data retrieval for accuracy.

Users can now easily analyze, modify, and track Business Impact Estimator calculations with a more interactive and intuitive experience.

***

#### **Log Retention**

#### **1. Log Archiving and Retention Management**

A structured log retention mechanism has been introduced, allowing users to **configure, store, and manage archived logs** based on predefined retention policies.

**New Features**

1. **Automated Log Archiving**:
   * Logs are automatically archived at scheduled intervals.
   * The system determines **which logs need to be archived based on retention settings**.
2. **Retention Policy Management**:
   * Users can define **how long logs are retained** before deletion.
   * Archive files are stored in a **configurable archive directory**.
   * Default retention is set to **7 days**.
3. **Audit Logging for Archival and Deletion**:
   * When logs are **archived or deleted**, an **audit record is created**.
   * Tracks **archive location, file details, and timestamp**.
4. **a. Setup Log Retention**

   * **Feature:** Users can now configure their **log retention period** and specify a **file path** to store logs.
   * **Functionality:** This allows better **log management** and compliance with data retention policies.

   **b. Email Notifications for Archived Logs**

   * **Feature:** Users can enter an **email address** to receive notifications when logs are archived.
   * **Functionality:**
     * If no email is specified, notifications will be sent to the **email address defined in the license**.
     * If the **Mail Server** settings are not configured, notifications will only be available in the **Dashboard’s notification panel**.

Reduces manual log maintenance efforts and **optimizes log storage usage**.

#### **2. New Log Retention Page**

A **dedicated Log Retention page** has been added to the **Settings section**, allowing users to configure and monitor log retention policies.

**New Functionalities**

1. **Configure Archive Time Range & Location**:
   * Users can **define the retention period**.
   * Modify the **archive storage location**.
2. **Visual Indicators for Archived Logs**:
   * Logs display **status (archived, available for download, deleted)**.
   * Download links are available for **retrieving archived logs**.
3. **User Actions Supported**:
   * Change retention settings.
   * Enable or disable log archiving.
   * Download logs.
   * Track log status in real time.

Provides **better control over log lifecycle management**, improving **compliance and storage efficiency**.

#### **3. Automated Log Archiving and Scheduled Deletion**

A **scheduler-based system** ensures that logs are archived at the right time and deleted once they exceed their retention period.

**New Features**

1. **Daily Scheduled Archiving**:
   * Logs are **archived automatically at 3:00 AM daily**.
   * The system checks the **retention period** to determine which logs need to be archived.
2. **Automated Deletion of Expired Logs**:
   * Once a log reaches its **expiration date**, it is **automatically deleted**.
   * The system ensures that **archived logs are removed efficiently** to free up storage.
3. **Cloud File Transfer Support**:
   * In cloud environments, archived logs are **transferred to a remote storage location before deletion**.
   * Users are **notified before permanent deletion**.

Eliminates **manual log cleanup** and ensures **consistent and reliable log retention management**.

#### **4. Log Retrieval & Download Capabilities**

Users can now **retrieve and download archived logs** using the new **Log Archive Download feature**.

**New Functionalities**

1. **Download Archived Logs**:
   * Users can download **archived logs directly from the UI**.
   * Supports **progressive download**, preventing excessive memory usage.
2. **Archive File Listing**:
   * The **list of archived logs** is displayed in an organized table.
   * Includes **file name, archive date, size, and download option**.
3. **Filtering & Sorting Options**:
   * Search archived logs by **name or date**.
   * Sort by **file size, archive date, or status**.

Allows **quick and efficient retrieval of logs**, ensuring **easy access to archived data**.

#### **5. Audit Trail & Security Improvements**

All log archival and deletion actions are **tracked in the audit log**, ensuring transparency and accountability.

**New Functionalities**

1. **Audit Log for Log Archival & Deletion**:
   * Every log archive and deletion is **recorded in the audit table**.
   * Tracks **timestamp, file name, and action type**.
2. **Ownership Validation for Scheduled Jobs**:
   * Ensures that **only the correct system processes handle log deletion**.
   * Prevents accidental deletion of **critical logs**.
3. **Concurrency & Performance Optimization**:
   * Prevents **race conditions** in scheduled log deletion.
   * Improves **performance of log retrieval and storage processes**.

Enhances **security, compliance, and traceability** in log retention management.

#### **6. Performance Optimization & Backend Improvements**

The backend has been optimized to **handle large-scale log retention operations efficiently**.

**New Enhancements**

1. **Efficient Log Storage & Compression**:
   * Logs are **compressed before archiving**, reducing storage consumption.
   * Supports **efficient indexing** for faster log retrieval.
2. **Improved API Performance**:
   * Optimized API responses for **faster access to archived logs**.
   * Pagination added for **large datasets**.
3. **Scalable Scheduling Mechanism**:
   * New scheduling logic **prevents excessive resource usage**.
   * Reduces **impact on system performance**.

Ensures **faster log retrieval, optimized storage usage, and better overall system efficiency**.

***

#### **Monitoring Filter**

#### **1. Advanced Filtering Capabilities**

A new **dynamic filtering system** has been integrated into the Monitoring page, enabling users to **refine their search criteria** and manage large data sets efficiently.

**New Features**

1. **Multi-Select Filtering**: Users can **filter multiple statuses, users, automs, and queue pools** in one search.
2. **Date-Based Filtering**:
   * **Current Week, Current Month, Current Year, and Today** options allow easy selection of **time-based filters**.
   * Users can **define custom date ranges** for precise searches.
3. **Text-Based "Contains" Search**:
   * Allows partial matching for **autom names, queue pools, and user names**.
4. **Queue Pool & User Filtering**:
   * Users can **filter results based on specific users or queue pools**.

Enables **more targeted searches**, reducing the time required to find specific operations.

#### **2. New Monitoring Filter Modal**

A **dedicated Filtering Modal** has been added to the Monitoring page, allowing users to **apply multiple filtering criteria at once**.

**New Functionalities**

1. **Pre-Filled Data for Existing Filters**:
   * When updating a filter, the **previously saved values** are automatically populated.
   * Users can **edit or modify fields without re-entering information**.
2. **Filter Categories**:
   * **Status** (e.g., Pending, Completed, Failed)
   * **Autom Name & Group**
   * **Queue Pool & User Name**
   * **Created & Ended At Timeframes**
3. **Save and Reset Filters**:
   * Users can **save frequently used filters** for quick access.
   * A **reset option** allows users to clear selected filters.

Simplifies **filtering workflows** and allows users to **quickly switch between saved filters**.

#### **3. Filter Persistence and Management**

Users can now **save, edit, and delete filters**, ensuring **efficient filter management**.

**New Functionalities**

1. **Filter Summary & Chip Display**:
   * When a filter is applied, an indicator **below the tabs** displays the **active filters**.
   * Users can **edit or delete filters directly from the summary section**.
2. **Single & Bulk Filter Deletion**:
   * Users can **delete individual filters** or **bulk delete multiple filters** at once.
   * A confirmation prompt ensures filters are **not deleted accidentally**.

Makes **filter management more flexible and efficient**, reducing repetitive configuration.

#### **4. Enhanced Search Functionality**

A **global search bar** applies a **"contains" filter across all columns**, allowing users to **quickly find relevant operations**.

**New Functionalities**

1. **Dynamically Filters All Columns**:
   * The entered search text applies **to all columns in the monitoring list**.
2. **Real-Time Query Evaluation**:
   * Search queries are **dynamically constructed** based on both the search input and selected filters.
3. **Searchable Fields**:
   * **Operation Status**
   * **Created At, Run At, Completed At**
   * **Autom Name, Group Name, Queue Pool, User Name**

Reduces **manual effort** in finding operations, ensuring **faster and more accurate results**.

#### **5. Backend Enhancements for Filtering & Search Optimization**

Backend services have been updated to **support the new filtering options and improve search performance**.

**New Features**

1. **Enhanced Query Processing**:
   * Search values and filter parameters are **dynamically evaluated together**.
2. **New Filters Query Parameter**:
   * The system supports **complex filtering rules**, including **multi-select and date ranges**.
3. **Improved API Performance**:
   * **Optimized database queries** reduce **load times for large result sets**.
4. **Scheduler-Based Query Optimization**:
   * Improved efficiency in **filtering scheduled operations and queue pools**.

Ensures **fast, scalable, and efficient filtering**, even with large data sets.

#### **6. UI/UX Enhancements & Performance Optimization**

The user interface has been redesigned for **better usability and responsiveness**.

**New Features**

1. **Consistent UI Across All Pages**:
   * The filtering experience **matches other Autom Mate settings pages**.
2. **Improved Data Visualization**:
   * Clear separation of **filter summary, applied filters, and available options**.
3. **Optimized Rendering Performance**:
   * **Faster filter loading times**, even with **complex queries**.

A **more intuitive and user-friendly filtering experience**, reducing **complexity and improving accessibility**.

***

#### [**Role-Based Access Control (RBAC) System**](/userguide/product-features/management/user-management/roles.md)

The **Boston 4.4.0** release introduces the [**Role-Based Access Control (RBAC) system**](/userguide/product-features/management/user-management/roles.md), providing **granular access management** across Autom Mate. This newly implemented feature enables organizations to **define, manage, and enforce user roles and permissions**, ensuring **secure and controlled access** to different platform functionalities.

Key Features:

* **New Sidebar UI with Dynamic Permissions**: The sidebar now **fetches role-based access data dynamically** from the backend.
* **Comprehensive Role Management System**: Users can **define, modify, and assign roles & permissions** with an intuitive UI.
* **Database & API Enhancements**: Role-permission mapping is now **centrally managed** with optimized queries.
* **Adaptive UI Rendering**: Modules and UI components dynamically adjust **based on assigned user roles**.

This **first-time release of** [**RBAC** ](/userguide/product-features/management/user-management/roles.md)brings **greater security, control, and operational efficiency** to access management.
{% endtab %}
{% endtabs %}