Boston 4.3.0

1. Action Name Hotkeys

   • Enhanced hotkey functionality during action name editing. The delete key now affects only the action name field, and Ctrl + V pastes text directly into the name field.

1. Dashboard Widget Data Fetching

   • Frontend: Data fetching for widgets is now processed separately to improve dashboard responsiveness, allowing faster load times.

   • Backend: Enhanced backend performance for dashboard widgets by optimizing data-fetching methods, which reduces load times and server impact.

1. Increased Upload Limit for MateDrive

   • Previously, MateDrive had a restrictive 1 MB upload limit. This update expands the limit to 50 MB, accommodating larger file uploads. Additionally, the warning message has been adjusted to reflect the new 50 MB maximum. Users can now upload more substantial files without encountering issues, with clear guidance provided if they exceed the limit.

1. Improved UI Responsiveness for High-Resolution Monitors

   • To enhance usability and maintain a consistent interface across various display sizes, we have implemented significant improvements in the responsiveness of the UI for users with high-resolution monitors. Previously, UI components would extend and create excessive spacing on larger screens, affecting the visual appeal and ease of navigation. With this update, component spacing and layout are optimized to maintain proportional alignment and usability, ensuring that all elements display in a visually coherent and user-friendly manner, regardless of monitor resolution.

These enhancements aim to provide a more cohesive and visually balanced experience, enhancing productivity and ease of use for users with high-resolution displays.

1. Monitoring log detail page search button improvements

   1. To enhance the user experience and prevent redundant actions, two key improvements have been made to the search functionality:

      1. Loading Animation: When the user initiates a search by clicking the search button, a loading animation will appear. This animation provides immediate visual feedback, letting the user know that the system is processing the search request. The animation will remain visible until the service returns a response, ensuring users are informed that their request is underway.

      2. Button Disable During Search: After the search button is clicked, it will be temporarily disabled until a response is received from the service. This prevents users from accidentally submitting multiple searches requests and helps reduce server load and response time.

1. Improved Backend Stability and Logging Continuity in Autom Operations

   1. This fix addresses issues related to backend stability and logging in autom operations. Previously, if the backend went down during an autom execution, operations would stop, and logs would not update accurately. Additionally, completed operations could sometimes remain stuck in the "In Progress" status due to logging issues triggered by backend downtime.

      With this update:

      • Autom operations will now automatically resume when the backend recovers from downtime, ensuring uninterrupted processing and accurate task completion.

        • Log status updates are now reliable, so completed operations no longer stay in the "In Progress" status if a backend issue occurs.

1. Import Autom Enhancement

   1. This enhancement introduces a confirmation step during the Autom import process, allowing users to make informed decisions before overwriting existing Autom configurations. When importing an Autom that may replace an existing one with identical variables, users will now see a prompt with the following message:

1. Trigger Param payload Enhancement

   1. The triggerHeader variable, previously available only in the back-end, is now visible in the Autom Mate UI for webhook and API Automs. This enhancement ensures better accessibility and transparency for users configuring automation Automs.

1. Excel Read File Action Data Limit Update

   1. The readFile action for Excel has been updated with a 250 MB data limit. Files exceeding this size will no longer be supported to ensure optimal system performance and avoid potential issues during processing. This improvement applies to all Automs utilizing the readFile action in Excel-related tasks.

2. MateDrive Save to Mate Drive Action Data Limit Update

   • The SaveToMateDrive action in MateDrive has been updated with a 250 MB data limit. Files exceeding this size will no longer be supported. This improvement ensures better system performance and avoids processing failures when handling large files.

     This update is applicable to all Automs using the SaveToMateDrive action.

3. Word ReadDocument Action: 250 MB Data Limit Implementation

   • The Word ReadDocument action in Autom Mate now enforces a 250 MB file size limit. This enhancement is implemented to ensure smoother operation, prevent resource overload, and maintain stability when processing large Word documents.

     • Files exceeding 250 MB cannot be processed using this action.

     • This change applies to all Automs utilizing the Word ReadDocument action.

4. CSV Read Action: 250 MB Data Limit Implementation

   • The CSV Read action in Autom Mate now enforces a 250 MB file size limit. This update ensures efficient operation, prevents resource overload, and enhances the stability of Automs processing large CSV files.

     • CSV files exceeding 250 MB will no longer be supported by the CSV Read action.

     • This limitation applies to all Automs utilizing this action for file processing.

5. FTP Download Files & Download Folder Actions: 250 MB Data Limit Implementation

   • The FTP Download Files and FTP Download Folder actions in Autom Mate now include a 250 MB file size limit for individual files and folders. This update is designed to optimize resource utilization and maintain the reliability of Automs downloading large datasets.

     • Files or folders exceeding 250 MB will no longer be downloaded through these actions.

     • Applies to all Automs using these actions for FTP-based data transfer.

6. Data Limit Applied to Text Read Action

   • To improve stability and optimize performance, a 250MB file size restriction has been applied to the Text Read action. Files exceeding this size will no longer be processed to avoid potential slowdowns or memory issues. Users are advised to split larger files into smaller segments or explore alternative solutions for handling oversized text files.

7. Display Message Pop-Up Improvements

   • The Display Message pop-up has been updated with the following improvements to prevent browser crashes and enhance user experience:

     1. Character Limits:

        • Message Content Limit: The message content is now capped at 1000 characters. This ensures optimal performance and prevents browser crashes caused by excessively large messages.

        • Title Limit: The title of the display message is now restricted to 24 characters, maintaining concise and clear titles.

     2. New Features:

        • Instructional Text: A message at the top of the pop-up now reads: "For viewing the whole data, please download the file."

        • Download Option: A Download button has been added to allow users to export the entire message string as a .txt file, providing a convenient way to access full data.

     These enhancements ensure a smoother user experience by addressing performance issues and offering an alternative for handling larger datasets. Users can now confidently utilize the Display Message action without risking browser crashes.

1. Tooltip for Autom Name in Log Summary Dialog

   1. The log summary dialog has been enhanced with the addition of a tooltip for the Autom name field. This tooltip provides contextual information about the Autom name, aiding users in understanding its relevance and purpose in the log summary.

      1. Tooltip Description:

         • The tooltip displays a brief explanation of the Autom name's significance, offering helpful guidance for users navigating the log summary.

         • Purpose:

           • Ensures users can quickly grasp the context and details of the Autom name without needing additional documentation or support.

      This enhancement improves the usability of the log summary dialog, making it more intuitive for users to interpret the data presented.

1. Disabled Output Tab for Empty Log Outputs

   1. To improve user experience and reduce confusion, the Output Tab in the log summary dialog will no longer be accessible when the log output data is empty.

      1. Behavior Update:

         • If the log output contains no data, the Output Tab will be visually disabled and unclickable.

         • A message or tooltip may be displayed to indicate that no output data is available.

         • Purpose

           • Streamlines the user interface by hiding irrelevant or unavailable options.

           • Prevents users from navigating to an empty tab, saving time and improving usability.

         • Impact

           • Enhances clarity and Automs efficiency when reviewing logs in the system.

2. Clear Button for Search Input Values

   1. This enhancement introduces a more intuitive and efficient way for users to manage their search input fields:

      1. New Clear Button Functionality:

         • When users type any value in the search input field, an 'x' icon will dynamically appear on the right side of the input box.

         • Clicking the 'x' icon will immediately clear all input values from the field, resetting it to a blank state.

         • Benefits:

           • Improves ease of use by eliminating the need for users to manually delete characters.

           • Enhances user experience by streamlining input management during search operations.

         • Visual Indicators:

           • The 'x' icon is context-sensitive and will only appear when there is text in the input field.

           • The icon will disappear automatically once the input is cleared or empty.

1. Autom List Page FE Enhancements

   1. Select All/Deselect All Button

      • A "Select All/Deselect All" button has been added to the Autom List Page for improved usability.

        • This button allows users to quickly select or deselect all Automs in the list, streamlining bulk actions like deletion or updates.

   2. Language Change for Single Autom Deletion

      • The confirmation message for deleting a single Autom has been revised for better clarity.

        • Example of New Language: "Are you sure you want to delete this Autom? This action cannot be undone."

   3. Language Change for Multi-Selected Autom Deletion

      • The confirmation prompt for deleting multiple selected Automs has been updated.

        • Example of New Language: "Are you sure you want to delete the selected Automs? This action will remove all selected items permanently."

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

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

1. Base64 Encode Action 250MB Data Limit

   1. A 250MB data limit has been enforced for the Base64 Encode action. This ensures that data encoded in Base64 will not exceed the specified size, preventing memory overloads and potential performance issues.

   2. This limit applies to both incoming data and the resulting encoded data to ensure consistent behavior and performance.

   3. Prevents errors or slowdowns when users attempt to process very large data sets that could cause the system to exceed memory or time limits.

   4. Users attempting to encode data exceeding 250MB will be informed of the limitation and instructed to reduce the data size before attempting again.

1. Repeat n Times - Maximum Limit of 999

   1. A character validation has been introduced to restrict users from entering more than 3 digits for the "Repeat n times" field. The validation ensures that when users enter a number, they can only input values up to 999. When users try to input a number with 4 digits (e.g., 1000 or higher), they will not be allowed to enter the value. However, if a variable is used in this field, it will still work as expected. Additional Restriction: The validation also ensures that users cannot paste numbers larger than 999 (e.g., using Ctrl+V or other paste actions). However, they can still paste variables.

2. Release Notes: 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.

1. Log Search Detail Page

   • Introduced an advanced Log Search Detail Page with improved filtering, navigation, and highlighting. This feature simplifies log analysis by allowing users to pinpoint specific entries.

   • Added a log search detail page that introduces the ability to navigate between logs based on filter criteria, with index highlighting.

   • Error Handling Autom features now include an E-sign, improving error visibility in Autom Automs.

1. Log Detail Service Update

   • Enhanced the Log Detail Service by merging start and end logs for each action, providing users with a single, comprehensive log view.

1. Input & Output Log Merging

   • Combined input and output logs for clearer tracking of each action’s lifecycle in log reports.

1. Automs Started & Ended Status in Monitoring Logs

   • Added Automs Started and Automs Ended indicators on the Monitoring Log Details, alongside enhanced error-handling notifications.

1. HaloITSM Application Integration

   • Integrated HaloITSM into the database, expanding Autom Mate’s connectivity with external applications.

   • Detailed documentation will be add.

1. Grouped Log Display

   • Introduced expandable grouped logs under parent elements for cleaner log viewing on the frontend. Backend updates ensure group logs display under the correct parent elements.

   • Check Log Details Screens and Usage Video

1. Log Search Service

   • Developed a new Log Search Service to enable efficient querying of log data.

   • Check Log Details Screens and Usage Video

1. Search Function on Detail Page

   • Implemented the first phase of search functionality on the detail page, allowing more refined searches within specific logs.

   • Check Log Details Screens and Usage Video

1. Removal of "Download Advanced Log" Button

   • With recent improvements to log monitoring, the "Download Advanced Log" button is no longer necessary and has been removed from the product. Users now have access to advanced log details directly in the Log Monitoring section, offering seamless, real-time log tracking without the need for downloads. This update enhances log visibility and ensures that all logging information is immediately available within the product’s UI.

2. Logging of Error Handling Autom

   • This update introduces logging capabilities for error-handling automations, enabling greater visibility into error management Automs. Previously, error-handling actions within automations were not logged, limiting traceability. With this feature, users can now see detailed logs for each error-handling action directly within the log interface. This enhancement improves monitoring, troubleshooting, and overall control over automated error-handling processes.

1. Limiting Input and Output Variables

   • To enhance system performance and improve data manageability, limits for input and output variable types have been implemented. These restrictions apply to various data formats, ensuring Automs remain efficient and stable.

1. Enhanced Data Table Log Previews and Variable Limits

1. Trigger Param Log Improvement

   • Empty Object Display:

     • Resolved an issue where {} was unnecessarily shown in logs for empty trigger parameters.

     Log Organization:

     • Trigger logs now have two distinct sections: Trigger Body and Trigger Header.

     • The Trigger Body value has been removed from the info section and relocated to its dedicated tab.

     • Updated tab labels to Trigger Body and Trigger Header instead of the generic Input and Output buttons for improved clarity.

     • Trigger Header now displays its values directly in the log view for easier access and understanding.

2. Self-Healing for Failed and In-Progress Operations

   • A retry icon will appear on operations that fail or get stuck in the "in-progress" state. Users can click on this icon to automatically retry the operation until it completes successfully or the retry limit is reached.

   • Expected Outcome:

     • Improved user experience with less manual intervention required.

     • Reduced downtime through automatic retries of failed operations.

     • Operational continuity for stuck or failed processes.

   • User Action:

     • Click the retry icon to initiate the retry process. The system will handle the retry automatically.

1. Select All / Deselect All Button Added

   • A new Select All and Deselect All button has been added to the Automs page to simplify the process of selecting and deselecting items. This addition will save time for users who need to perform actions on all items within the list. Users can now quickly select or deselect all items on the Automs page without needing to manually check each item. This improves navigation and selection tasks when working with large lists. Users can now easily manage item selection with the new buttons, making batch operations more efficient and reducing the number of manual clicks required.