{% endhint %}
π **Action Name Hotkeys**
Enhanced editing capabilities for action names with precise hotkey support, ensuring smoother user interaction.
π**Dashboard Widget Data Fetching**
Improved dashboard responsiveness with optimized widget data fetching for faster load times and enhanced performance.
π **Increased Upload Limit for Mate Drive**
Upload limit increased to 50 MB, enabling larger file uploads with clear warnings for size restrictions.
π **Improved UI Responsiveness for High-Resolution Monitors**
Optimized layout and spacing for better usability on high-resolution screens, ensuring a visually cohesive experience.
π **Monitoring Log Detail Search Button Improvements**
Enhanced search experience with loading animations and disabled button states during log searches to reduce redundancies.
π **Improved Backend Stability and Logging Continuity in Autom Operations**
Backend recovery now ensures uninterrupted autom operations and accurate log updates, addressing previous stability issues.
π **Import Autom Enhancement**
Added confirmation dialog to prevent accidental overwrites when importing Autom.
π **Trigger Param Payload Enhancement**
The `triggerHeader` variable is now visible in the UI, functioning like `triggerParam` to streamline Automs configurations.
π **Excel Read File Action Data Limit Update**
Enforced a 250 MB size limit for Excel readFile action to enhance performance and reliability.
π **Mate Drive Save to Mate Drive Action Data Limit Update**
The SaveToMateDrive action now supports files up to 250 MB, improving system efficiency and preventing errors.
π **Word Read Document Action 250 MB Data Limit Implementation**
Introduced a 250 MB limit for the Word Read Document action to ensure stable and reliable processing.
π **CSV Read Action: 250 MB Data Limit Implementation**
Updated the CSV Read action to process files up to 250 MB, enhancing stability for large dataset handling.
π **FTP Download Files & Download Folder Actions: 250 MB Data Limit Implementation**
Enforced a 250 MB limit for FTP Download actions to optimize performance and maintain Automs stability.
π **Data Limit Applied to Text Read Action**
Applied a 250 MB size restriction to the Text Read action, improving performance and avoiding memory issues.
π **Display Message Pop-Up Improvements**
Added character limits and download functionality to prevent browser crashes and improve usability in message handling.
π **Tooltip for Autom Name in Log Summary Dialog**
Enhanced log summary dialog with a tooltip for Autom names, offering contextual information and improved clarity.
π **Disabled Output Tab for Empty Log Outputs**
The Output Tab is now disabled for empty logs, streamlining navigation and improving the user experience.
π **Clear Button for Search Input Values**
Introduced a clear button for search fields, providing a quick and efficient way to reset inputs.
π **Autom List Page FE Enhancements**
1. **New Select All/Deselect All Button**: Easily select or deselect all Automs in the list for faster bulk actions.
2. **Improved Language for Single Autom Deletion**: Clarified messaging for deleting a single Autom.
3. **Enhanced Multi-Delete Language**: Updated language for deleting multiple selected Automs to improve clarity and user experience.
π **Log Limiting Input and Output**
The issue related to log data exceeding the 10,000-character limit has been addressed, particularly for **Base64** encoded data. Additionally, key value limits have been introduced for objects in logs.
π **Display Message Enhancement**
A series of improvements have been made to the **Display Message** pop-up to prevent browser crashes and enhance user interaction. This includes a 1000-character limit, a download option for the full message, and a title length restriction.
π **Base64 Encode Action 250MB Data Limit**
A new data limit has been applied to the **Base64 Encode** action to restrict the maximum data size to **250MB**. This change ensures that larger data files do not exceed memory or performance limits.
π **Repeat n times - Maximum Limit of 999**
A character validation and restriction have been implemented to ensure that the "Repeat n times" field only accepts values up to 999. This prevents the entry of values beyond this limit and improves data integrity for loop actions.
π **Mate Drive Folder and File Name Limitations**
Mate Drive now enforces a 20-character limit for folder names during creation, ensuring compatibility and improved usability across various interfaces. Additionally, tooltips have been added for folder and file names exceeding 20 characters, with long names truncated using ellipses ("...") for better display. Hovering over truncated names reveals the full name via a tooltip, providing users with clarity and ease of access. Alongside these updates, several optimizations have been implemented to enhance overall performance and user experience.
{% hint style="success" %}
Streamlined action name editing with better hotkey support. Optimized dashboard widget performance for faster load times.
{% endhint %}
{% hint style="danger" %}
### Xurrent / 4me Update
With the recent rebranding from **4me** to **Xurrent**, users are now required to be on version 4.3.0 or higher to download any Xurrent versions from the platform. This change is purely due to rebranding and does not introduce any new features or functional changes to the Xurrent platform.
* **Restriction for Older Versions**: Users on versions earlier than 4.3.0 are restricted from downloading Xurrent versions to align with the rebranding guidelines. This restriction helps prevent compatibility issues with previous 4me versions and maintains system consistency.
* **Library Validation Error**: If a user on a pre-4.3.0 version attempts to download a Xurrent version, they will receive a **Library Validation Error**. This message indicates that an update is required to access the rebranded version.
***
> **Warning**: Users on versions below 4.3.0 should update to the latest version to ensure they can download Xurrent versions without encountering errors. This update does not add any new features but is necessary to avoid compatibility issues stemming from the rebranding.
> **Hint**: Check your current version in the settings. If it is below 4.3.0, updating will prevent download restrictions and ensure continued access to Xurrent versions post-rebranding.
> {% endhint %}
{% hint style="info" %}
### **Enhanced** Autom**-Based Log Level Management in Autom Mate**
Autom Mate introduces Autom-specific log level management, giving users more control over logging configurations and enhancing performance:
* **Info Level Logging Option**: In the Automs editing screen, a new checkbox labeled *"Info Level Logging Enabled"* allows users to enable Info-level logging for a specified duration (e.g., 7 or 14 days).
* **User Notification**: When a time period is selected, a prompt will display, informing users of the retention period and its impact on log storage.
* **Display of Debug Configurations in** Automs **Details**: The Automs detail screen now shows previously saved debug configurations, allowing users to view existing log settings easily.
* **Automated Log Level Reduction**: A timer in the backend will automatically decrease the log level of Automs that exceed the selected retention period.
* **Gateway Log Filtering**: For Automs with a reduced log level, the gateway will not store input and output logs, reducing data storage for low-priority Automs .
> **User Guidance**: Regularly review your logging settings, especially when using the timed Info logging feature, to ensure important logs are retained as needed while optimizing performance.
> {% endhint %}
***
### **β¨ New Features**
{% hint style="warning" %}
When an API request is triggered, if the request remains in-progress or if a retry occurs, the system will not send a response back to the origin of the request. Instead, the process will simply restart, and the request will continue without an immediate response.
{% endhint %}
π **Log Search Detail Page**
Introduced an advanced Log Search Detail Page with improved filtering, navigation, and highlighting tools to simplify log analysis.
* Added features for navigating logs based on filter criteria with index highlighting.
* Enhanced Error Handling Autom with an E-sign for better error visibility.
π **Log Detail Service Update**
Enhanced the Log Detail Service by merging start and end logs for each action into a single comprehensive view.
π **Input & Output Log Merging**
Combined input and output logs for more concise tracking of action lifecycles in log reports.
π **Automs Started & Ended Status in Monitoring Logs**
Added clear Automs Started and Automs Ended indicators to Monitoring Log Details, along with improved error-handling notifications.
π **HaloITSM Application Integration**
Integrated HaloITSM into Autom Mate, expanding connectivity with external applications.
π **Grouped Log Display**
Introduced expandable grouped logs under parent elements for cleaner and more organized log viewing.
π **Log Search Service**
Developed a new Log Search Service for faster and more efficient querying of log data.
π **Search Function on Detail Page**
Implemented the first phase of detailed search functionality, allowing refined searches within specific logs.
π **Removal of "Download Advanced Log" Button**
Eliminated the "Download Advanced Log" button as advanced log details are now directly accessible in the Log Monitoring section.
π **Logging of Error Handling Autom**
Enabled detailed logging for error-handling automations, improving traceability and control over automated Automs.
π **Limiting Input and Output Variables**
* Input and output variables now have size constraints:
* **String:** 10,000 characters max.
* **Number:** 1,000 characters max (with a 10-digit hard limit).
* **Array:** 1,000 elements max.
* **Data Table:** 1,000 rows max.
* **Object:** 1,000 keys max, with individual key checks.
* Informational messages will guide users when limits are exceeded.
* Improved array outputs now display the total count of arrays in input fields.
π **Enhanced Data Table Log Previews and Variable Limits**
* Data table previews now support up to **1,000 rows by 1,000 columns** with clear truncation indicators for larger datasets.
* Strict size limits introduced: **Strings (10,000 characters), Numbers (10 digits), Arrays (1,000 elements), Data Tables (1,000 rows), and Objects (1,000 keys).**
π **Trigger Param Log Improvement**
Fixed incorrect display of `{}` for empty trigger parameter logs. Enhanced log structure with distinct tabs for Trigger Body and Trigger Header.
π **Self-Healing Development for Failed & In Progress Operations**
This feature introduces an automatic retry mechanism for operations that fail or become stuck in the "**in-progress**" phase. A retry icon will appear, allowing users to retry the operation with a click.
π **Select All / Deselect All Button Added**
A new button has been added to the **Automs** page, allowing users to easily select or deselect all items in one click, improving usability and efficiency.
{% hint style="success" %}
Added advanced **Log Search Detail Page** with filtering and navigation. Merged start and end logs for clarity, and introduced grouped logs, expanded **HaloITSM integration**, and search functionality in the detail page.
{% endhint %}
{% hint style="danger" %}
### Streamlined Access to Advanced Logs with New In-UI Monitoring Tools
With this release, the Advanced Log File Download option **has been removed**, shifting advanced log access **entirely to the Log Monitoring interface within the product UI**. This integration provides a streamlined, real-time experience for users, as all log details are available directly within the UIβno need to download and open separate files. Users can now interact with logs using the enhanced Log Monitoring features.
New Features for Log Monitoring:
* **Comprehensive In-UI Log Details:** Full visibility into advanced log data is now possible within Log Monitoring, offering a centralized view of all log information related to automated processes.
* **Real-Time Log Access:** Logs are updated in real-time, giving users immediate insights into process execution, errors, and system performance.
* **Advanced Filtering and Search:** Log Monitoring now includes advanced filters, search capabilities, and sorting options. This allows users to efficiently locate specific entries, troubleshoot errors, and analyze performance without sifting through raw files.
* **Enhanced Control and Insights:** The UI offers tools to track, analyze, and troubleshoot with ease, ensuring that users have greater control over their automated processes. These changes not only enhance visibility and monitoring efficiency but also reduce dependency on external log file management, making log interaction more accessible and streamlined.
{% endhint %}
***
## **Detailed Version**
{% tabs %}
{% tab title=" π
±οΈ Bug Solution" %}
1. **Action Selection in Configuration Form**
* Selecting actions in the configuration form occasionally resulted in a blank screen, which prevented further configuration. The issue has been corrected, ensuring that the interface loads actions properly and the configuration process can proceed smoothly.
2. **Schedule Display and Execution Errors**
* Time display errors and execution inconsistencies occurred in daily, weekly, and monthly schedules, leading to confusion and missed automation events. These issues have been corrected, ensuring accurate scheduling across all frequencies.
{% hint style="danger" %}
#### **Warning**
Users with complex scheduling configurations should review schedules to confirm that display times and execution match the intended schedule.
{% endhint %}
3. **User Password Field Bug**
* During Autom creation, username and password fields were saved as empty strings, leading to incomplete credentials. This issue has been fixed, and credentials now save accurately, ensuring login details are complete and secure.
4. **No Autom Found Error After Deletion**
* After deleting Autom entries, the system occasionally displayed a residual "Not Found" error. The system now accurately handles the removal of deleted Autom entries without leaving erroneous indicators.
{% hint style="info" %}
#### **Hint**
After deleting an Autom, verify that all associated elements have been removed to prevent unintended display errors.
{% endhint %}
5. **Data Manager Fullscreen Overlay**
* The Data Managerβs fullscreen mode blocked access to the library menu, limiting navigation options. This issue has been resolved, allowing users to access the library menu even while in fullscreen.
{% endhint %}
{% hint style="danger" %}
#### **Warning**
1. Bulk deletions cannot be undone. Please double-check your selections before confirming.
2. Deletions (single or multiple) are permanent and cannot be reversed.
{% endhint %}
{% hint style="info" %}
#### **Hint**
1. Ensure you review the Autom before confirming deletion to avoid accidental loss.
2. Use the new "Select All/Deselect All" button for faster bulk management on pages with numerous Automs.
{% endhint %}
3. **Log Limiting Input and Outputs**
1. **Base64 Encoded Data**: If a piece of data exceeded the 10,000-character limit and was in **Base64** format, displaying just part of it was not useful. This issue has been addressed, and a helpful message will now appear in the logs, informing users of the data's size limitation when it's in **Base64** format.
2. **Object Key Length Limit**: Previously, there was no limit on the length of keys within objects logged. Now, a limit of **10,000 characters** has been introduced for **string** values of keys. This means that if a key in an object exceeds this limit, it will be truncated or omitted to prevent excessive data from being logged.
3. **Impact**:
* **Log data** is now more manageable and informative. Base64 data that exceeds the limit will be properly flagged with an informative message, and excessively long object keys will be handled by truncating or rejecting them as needed.
* Helps avoid performance or storage issues caused by excessively large log entries.
4. **User Action**:
* Users will see clear messages in the logs when data exceeds the limits, especially for Base64 encoded data or long object keys, preventing confusion or unexpected behavior.
{% hint style="info" %}
**Hint**
This fix improves log readability and prevents large objects from overwhelming the logging system.
{% endhint %}
{% hint style="danger" %}
**Warning**
Ensure that object keys and Base64 data are appropriately sized to avoid truncation or informational messages in logs.
{% endhint %}
21. **Display Message Enhancement**
1. A **1000-character limit** has been applied to the display message pop-up to prevent browser crashes that occurred when the message exceeded this limit.
2. A message at the top now informs users: *βFor viewing the whole data, please download the file.β* along with a **download button** to download the full message as a `.txt` file. This allows users to access and review longer messages without performance issues.
3. **Title Length Restriction**: The title field in the **Display Message** pop-up now has a **24-character limit** to ensure consistency and avoid UI layout issues.
4. **Impact**:
* Prevents browser crashes caused by excessively long messages.
* Improves user experience by offering a download option for longer messages.
* Ensures consistent UI by limiting title length to 24 characters.
5. **User Action**:
* Users will see a clear message if the content exceeds 1000 characters, directing them to download the full content.
* Users are encouraged to follow the new title length restriction to avoid UI issues.
{% hint style="info" %}
**Hint**
If the message exceeds 1000 characters, the pop-up will display a prompt to download the full content as a `.txt` file.
{% endhint %}
Log Details Screens and Usage
Error Handling Autom features now include an E-sign
HaloITSM Library
| Log Data Table Previews | Preview Capabilities:
| Scroll Enhancements:
|
| Variable Size Limits | New limitations to ensure performance:
|
