Boston 4.0.0
Autom Mate Boston Edition v4.0.0 Release Notes
Highlights of this Release
Fixes
UI: Advanced Logs are not available - Log-Advanced log limit - Advanced logs were not displaying due to a limit.
UI: If trigger data is too big, we can't show it on the advanced log - Large trigger data couldn't be displayed.
Service: RemoveHTML Function line space bug - The RemoveHTML function caused errors with HTML formats.
Service: Regex Issue - Remove HTML - Regex parentheses issue solved.
Service: Autom Store Get Autom library update - Compatibility issue with Autom Store Automs resolved.
UI: Data Manager Bug - Data Manager displayed a white screen when response output was empty.
UI: Error configuration creating a group for single action - Error handling flow creation for a single action was broken.
UI: Long action labels break action control server design - UI issues with long action labels.
UI: Variable names max width error - Long variable names caused a max width error.
Service: GO TO action in groups not working - GO TO action in groups only worked once.
Service: Logging failed with large file uploads - Logging failed with large file uploads.
Service: Error Configuration bug - Error handling flow's record mechanism did not work.
Service: Base64 encode file path giving empty field error - Custom string configuration in Base64 encode action caused an empty field error.
Service: Character limitations - Character limitations during Autom creation were problematic.
New Features
Service: WhatsApp actions value handling for fields - Improved handling of character limitations in fields.
Service: Data Manipulation - Added data manipulation capabilities.
Service: Save to Mate Drive Action Development - Developed the Save to Mate Drive action.
Service: EasyVista App - Development of EasyVista App.
Service: 4me client credential OAUTH - Implementation of 4me client credential OAUTH.
Service: 4me Import Action and Get Import Status Action - Added import actions for the 4me library.
Service: Jenkins - New Jenkins App developed.
Enhancements
Service: Solarwinds library refactor - Solarwinds enhancement and performance improvements.
UI: Groupable Automs - Improved dashboard with groupable feature.
UI & Service: Monitoring Page Refactoring- Improved monitoring page with backend services.
Service: Number Assign Issue - Default value in number assign was not working.
Details
UI: Advanced Logs are not available - Log-Advanced log limit. Advanced logs were not displaying due to a limit.
When the log file size is huge, the advanced log download button gets an error when trying to be clicked by the user. Additionally, some log rows do not appear with any download button due to the huge size of the log file. This issue was resolved by developers, and users can now use the download button to download large log files.
UI: If trigger data is too big, we can't show it on the advanced log. Large trigger data couldn't be displayed.
When users utilize the trigger mechanism to run Autom, there is a limitation on the payload data size. Autom Mate logs this situation in the advanced log file; however, the file does not contain all the payload data and logs an excessively long message. This limitation has been removed, and Autom Mate can now handle large payload data.
Service: RemoveHTML Function line space bug. The RemoveHTML function caused errors with HTML formats.
Users encountered errors when using the RemoveHTML function due to spaces and row structure in HTML formats. This issue has been resolved by developers, and the function now works properly.
Service: Regex Issue - Remove HTML. Regex parentheses issue solved.
The Regex feature was not accepting parentheses in HTML. This issue has been resolved, and all HTML entities are now detected automatically.
Service: Autom Store Get Autom library update. Compatibility issue with Autom Store Automs resolved.
When users downloaded Autom from Autom Store, the system checked the version between Autom and Autom Mate. If the versions did not match, users saw a pop-up to download and update the related application. The issue causing error messages during this process has been resolved.
UI: Data Manager Bug. Data Manager displayed a white screen when response output was empty.
After running a RESTful action, when users opened the Data Manager to see the response while the output was empty, a white screen appeared. This issue has been resolved, and it works properly now.
UI: Error configuration creating a group for single action. Error handling flow creation for a single action was broken.
When users created an error handling flow with only one action in the Autom, they got an Autom with only the added action without start and stop actions. This issue has been resolved, and users will now see the correct screen when configuring error handling.
UI: Long action labels break action control server design. UI issues with long action labels.
When users used long descriptions or names for library components, the action control center UI was not responsive. The system has been updated to prevent UI conflicts with long labels.
UI: Variable names max width error. Long variable names caused a max width error.
Long variable names caused issues with the maximum width of variable name fields. This issue has been resolved by developers, and it now works properly.
Service: GO TO action in groups not working. GO TO action in groups only worked once.
If users used the GO TO action in a group, it only worked the first time. When the Autom ran a second time, it did not route to the related action. This issue has been resolved, and it works properly.
Service: Logging failed with large file uploads. Logging failed with large file uploads.
Users encountered errors when uploading large files (over 512MB). This limitation has been resolved, and users can now upload files without size restrictions.
Service: Error Configuration bug. Error handling flow's record mechanism did not work.
When users created an error handling flow and selected an object to record errors, the record mechanism did not work. This issue has been resolved, and it now works properly.
Service: Base64 encode file path giving empty field error. Custom string configuration in Base64 encode action caused an empty field error.
When users used the Base64 encode action with a custom string configuration, it gave an empty field error. This issue has been resolved, and custom string selection now works properly.
Service: Character limitations. Character limitations during Autom creation were problematic.
Users encountered character limitations while creating Autom. This issue has been resolved, and it now works properly.
Last updated