Boston 4.3.0

🚀 Highlights of this Release

The Autom Mate 4.3.0 release brings significant bug fixes and enhancements, improving overall system stability, automation reliability, and user experience. Key fixes include resolving action selection issues, ensuring accurate schedule execution, fixing credential-saving bugs, and enhancing data handling in CSV and Excel actions. Additionally, UI responsiveness has been optimized, logging and monitoring have been improved for better automation visibility, and new validation mechanisms have been introduced to prevent errors and enhance performance.

🅱️ Bug Fixes

📌 Action Selection in Configuration Form

Resolved blank screen issues when selecting actions, enabling smooth configuration processes.

📌 Schedule Display and Execution

Corrected time display and execution issues for daily, weekly, and monthly schedules, ensuring accurate automation.

📌 User Password Field Bug

Fixed a bug where credentials were saved as empty strings during Autom creation, ensuring accurate login details.

📌 No Autom Found Error After Deletion

Residual "Not Found" errors after Autom deletions have been resolved, ensuring clean system operation.

📌 Data Manager Fullscreen Overlay

Resolved an issue blocking library menu access in fullscreen mode, improving navigation.

📌 Desktop Actions Menu Display

All actions are now correctly visible in the Desktop Actions menu, ensuring comprehensive user access.

📌 Import Autom Credentials Fix

Credentials for RWS actions now transfer accurately across environments, ensuring seamless imports.

📌 Error Handling and Retry Logging

Improved retry logging to display clear retry counts and start-end markers for error-handling processes.

📌 Mate Drive Folder Path in CSV Export

Ensured folder paths are recognized correctly during CSV exports, reducing errors.

📌 CSV Library UTF-8 Support

UTF-8 encoding now handles special characters accurately, ensuring proper CSV export and import functionality.

📌 Empty Array Handling in String Assignments

Cleaned up empty array representations to prevent unintended newline characters in backend processes.

📌 "Sheet Contains Header" Option in CSV Read

Corrected header inclusion issues, ensuring proper data imports when the option is selected.

📌 Import Autom Basic Authentication Fix

Fixed credential mismatches during Autom imports, ensuring reliable authentication.

📌 Debug Operation Status Display

Debug mode operations now display as "IN-PROGRESS," providing accurate real-time feedback.

📌 Monitoring Interface Data Accuracy

Resolved issues with overlapping data in In Progress, Pending, and Scheduled monitoring sections.

📌 Error Handling Copy-Paste Restriction Notification

Added a restriction notification for unsupported actions in error-handling Automs to improve reliability.

📌 Schedule Validation and Date Handling

Fixed invalid date issues, added prompts for schedule updates, and ensured proper date validation.

📌 On-Premises Agent OAuth Error

Resolved OAuth authentication issues in hybrid and on-premises environments with updated Mate Agent support.

📌 Resolved EOF Errors in CSV and Excel Libraries

Enhanced file handling for CSV and Excel actions, minimizing unexpected Automs disruptions.

📌 Resolved Restful Header Output Issue

Fixed missing header output data when body output was absent, ensuring reliable Restful action functionality.

📌 Data Manager Selection Bug

A performance issue that occurred when selecting fields repeatedly within the Data Manager has been resolved.

📌 Alert Rule Bug Fix - Mate Agent & Autom Center Connection Lost

The bug affecting the alert mechanism for when the connection between Mate Agent and Autom Center is lost has been resolved. Now, Autom Mate will send notifications to the user when the connection is lost.

📌 String Variable Mask Option Not Available in Export-Import Actions

The issue where the masked string variable values were not being included during export and required manual input upon import has been fixed. This behavior is now documented under the variables section.

📌 ##sys_date_now## Not Updating Issue Fixed

The issue where the ##sys_date_now## variable was not updating after the first assignment in Autom has been fixed. Now, ##sys_date_now## will update correctly with each subsequent operation.

---

🛠️ Enhancement

Time Zone Synchronization

When using the database library to connect to an Oracle database, users must be aware of any time zone differences between the Mate Agent and the Oracle Client instance. If a discrepancy exists, users should specify the Oracle Client's time zone in the Connect Action to ensure proper synchronization between the Mate Agent and the Oracle Client instance.

📌 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.

Streamlined action name editing with better hotkey support. Optimized dashboard widget performance for faster load times.

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.

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.

---

✨ New Features

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.

📌 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.

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.

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.

---

Detailed Version

🅱️ 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.

Warning

Users with complex scheduling configurations should review schedules to confirm that display times and execution match the intended schedule.

1. 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.

2. 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

After deleting an Autom, verify that all associated elements have been removed to prevent unintended display errors.

1. 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.

1. Desktop Actions Menu Display

   • In the Desktop Actions menu, scope actions were the only ones visible, limiting user access to other actions. All actions now display correctly in the menu, ensuring comprehensive access for users.

1. Import Autom Credentials Issue

   • Custom credentials in RWS actions were not importing correctly between different environments, leading to credential mismatches. Credentials now transfer accurately, enhancing compatibility for Automs shared across environments.

2. Error Handling and Retry Logging

   • Retry logging incorrectly displayed retry counts and did not clearly mark the start and end of error-handling processes. The system now logs retries starting from 1 and includes both the start and end of each retry, improving log tracking.

3. Mate Drive Folder Path in CSV Export

   • When exporting CSVs to Mate Drive, the specified folder path was sometimes unrecognized, resulting in failed exports. The system now correctly identifies and locates folders in Mate Drive, enabling reliable CSV export.

Hint

Before exporting to Mate Drive, verify that the specified path exists to prevent potential export errors.

1. CSV Library UTF-8 Support

   1. UTF-8 special characters previously caused issues during CSV export and import, especially with non-English characters. Now, the CSV library fully supports UTF-8 encoding, allowing for accurate handling of all special characters during export and import.

Warning

For users handling non-English characters, double-check exported CSV files to ensure that characters display correctly across various platforms.

1. Empty Array Handling in String Assignments

   1. Previously, assigning an empty array to a string variable resulted in a [] format, causing unexpected newline characters to appear in backend processes. This fix ensures that empty arrays remain cleanly represented as [] in string assignments, without unintended formatting. This update improves consistency for developers, especially when handling array-to-string conversions in backend applications, and ensures smoother processing for downstream tasks such as logging and display.

2. "Sheet Contains Header" Option in CSV Read

   • Previously, when reading a CSV with the "Sheet Contains Header" option enabled, the first row (header) was mistakenly included in the data table. This update ensures that when this option is selected, the header row is properly excluded, resulting in cleaner data imports. This fix improves data accuracy and consistency for users handling CSV files with headers.

3. Import Autom Basic Authentication Issue

   • Previously, custom credentials selected in RWS actions would appear empty when an Autom was exported and imported to a new environment, despite showing as populated. This led to runtime errors due to incomplete authentication. Now, upon import, credentials are accurately verified; any unmatched credentials are cleared to avoid errors. This update ensures reliable authentication in newly imported Autom across environments.

4. Debug Operation Status Display

   • Previously, operations initiated in debug mode incorrectly showed a “PENDING” status, creating confusion over the actual state of the process. This fix updates the status to “IN-PROGRESS” immediately upon debug initiation, providing accurate real-time feedback and ensuring that users have a clear understanding of the operation's status while debugging.

5. Incorrect Data Display in Monitoring Status Sections

   • Previously, when navigating to the In Progress, Pending, or Scheduled sections within the monitoring interface before the History page data fully loaded, the system would incorrectly display history data in these sections. This issue caused confusion by showing completed automations where only active or scheduled automations should be listed. The bug has now been resolved, ensuring that each monitoring section displays only its relevant data, allowing users to view accurate statuses without overlap.

Warning

If similar data display issues persist, please refresh the monitoring interface or contact support for further assistance.

1. Error Handling Copy-Paste Restriction Notification

   1. To improve the reliability and functionality of error handling Automs, a new restriction notification has been implemented. Previously, users could copy and paste actions with Error Handling enabled within the Error Handling Autom, which could lead to unexpected behavior, such as failure to execute error handling, missing logs, and incorrect message order. With this update, a pop-up message will now appear if a user attempts to paste an error-handling-enabled action within the Error Handling Autom itself, notifying them with the following message:

“Since Error Handling is active on the action, it cannot be pasted inside of the Error Handling Autom.”

Warning

This notification helps prevent potential issues by restricting unsupported actions within error handling automations, ensuring smoother and more predictable Automs.

Users are advised to create new error-handling actions directly within the Error Handling Autom instead of copying and pasting existing ones to maintain log integrity and correct message sequencing.

1. Schedule Bugs

   1. This update addresses several issues related to scheduling and date validation within the Autom scheduling feature:

      • Daily Schedule Time Display: Fixed a bug where daily schedules did not display the correct time on the monitoring page. Users can now see accurate schedule times, improving monitoring reliability.

        1. Weekly and Monthly Schedule Execution: Previously, weekly and monthly schedules would fail to run correctly, causing disruptions. This issue has been resolved, allowing these schedules to operate as expected.

           1. Date Validation and Scheduling Options for "Only Once" Schedules:

              • Invalid Date Prevention: Users can no longer select impossible dates (e.g., February 31st, November 31st), which previously caused scheduling errors or unexpected behavior.

              • Date Corrections: If a user selects an invalid date, such as February 31st, the system will prompt an error message or adjust the date automatically (e.g., setting February 31st to March 1st).

              • Enhanced Scheduling Options: Options such as “last day of the month” or “second weekend of each month” have been considered for future scheduling flexibility.

              • Automatic Schedule Restart: When editing a date for an active schedule, the system now automatically starts the new schedule date, preventing manual errors.

              • Stopping Invalid Date Entries During Active Schedules

                1. If a schedule is active and an invalid date is entered, the schedule will no longer silently fail. Instead:

                   • The system will stop the schedule if it detects an invalid date entry.

                     A prompt will ask users to confirm the date change, adding an extra layer of caution and preventing accidental disruptions.

Warning

If you attempt to edit an active schedule and select an invalid date, the system will now stop the schedule and ask for confirmation before proceeding with the new date. This helps prevent unexpected schedule disruptions.

1. On-Premises Agent OAuth Error

   1. A bug affecting OAuth authentication in hybrid and on-premises environments has been resolved. Previously, OAuth requests were routed to the Assistant, causing errors when the Mate Agent and Autom Center were on separate networks. This issue occurred due to the absence of proper IP definitions and the inability of the Mate Agent to handle the wildcard .pem file used in Autom Center. The fix involves supporting the addition of the Autom Center's wildcard .pem file to the Mate Agent configuration. This ensures seamless OAuth authentication, even when the Mate Agent and Autom Center operate on different networks. Users must now include the wildcard .pem file in the Mate Agent setup to enable OAuth functionality and avoid authentication failures.

2. Resolved EOF Errors in CSV and Excel Libraries

   • A bug causing EOF (End of File) errors in CSV and Excel library actions has been fixed. This issue affected users working with certain file formats or improperly terminated files, leading to abrupt failures in Automs. With this fix:

     • CSV Actions: Now handle edge cases more robustly, including improperly terminated rows or unexpected file endings.

     • Excel Actions: Improved compatibility with diverse Excel file structures, ensuring error-free processing even with incomplete data or unusual file terminations.

     This fix enhances reliability for users working with CSV and Excel files in their Automs, minimizing unexpected disruptions due to file-related errors.

3. Resolved Restful Header Output Issue

   • A bug in the Restful action caused the header output to fail when nobody output was provided. This has been resolved, ensuring that:

     • Headers now display output data correctly, even when the body output is absent.

     • Output Consistency has been restored across all Restful actions, ensuring proper functionality regardless of the body configuration.

     This fix ensures that Automs using Restful actions remain functional and reliable, even in scenarios where only header outputs are utilized. Users can now fully leverage header data without dependency on the body output.

1. Data Manager Selection Bug

   1. A performance issue was identified when users attempted to select fields repeatedly within the Data Manager. Each subsequent selection caused noticeable slowdowns. This issue has now been fixed, ensuring smoother and faster interactions when selecting and adding fields. Improved performance when selecting fields multiple times in the Data Manager, reducing the lag and enhancing the overall user experience. Users can now interact with the Data Manager without experiencing performance degradation during repeated field selection.

Hint

The fix should improve field selection performance, especially when performing multiple selections in quick succession.

1. Alert Rule for Mate Agent & Autom Center Connection Lost

   1. A bug was identified in the alert rule mechanism for detecting when the connection between Mate Agent and Autom Center was lost. As a result, users were not receiving notifications in such cases. This issue has been resolved, and now, whenever the connection is lost, Autom Mate will send an alert notification to the user. Reliable notifications for connection loss between Mate Agent and Autom Center, ensuring users are informed of critical connectivity issues. Users will now receive notifications automatically whenever the connection between Mate Agent and Autom Center is lost.

2. String Variable Mask Option Not Available in Export-Import Actions

   • When exporting an Autom, if a variable was marked as masked, its value was not included in the export file. As a result, when importing, users had to manually enter the masked value again. This behavior has been addressed, and the system will now handle the masked variables appropriately during export and import actions. Consistency in the export-import process for masked variables. Users no longer need to manually re-enter masked values when importing data. This behavior is now documented under the variables section for better user understanding. Users can now export and import Autom configurations with masked variables without losing their values, as the system will manage them automatically.

3. ##sys_date_now## Does Not Get Updated

   • When using the ##sys_date_now## variable in an Autom to send a webhook, the value of ##sys_date_now## was assigned correctly the first time but did not update in subsequent operations. Specifically, after 60 seconds, when sending another webhook, the ##sys_date_now## value remained the same and was not refreshed. This bug has been resolved, and ##sys_date_now## now updates correctly with each trigger in Autom. Ensures that ##sys_date_now## always reflects the current timestamp when used in automations, preventing outdated or stale values from being used in webhook requests or other processes. Users can now expect the ##sys_date_now## variable to update consistently throughout the Autom process, ensuring accurate timestamps are used in all steps.

🛠️ Enhancement

✨ New Features