October 2024

October 14, 2024

These release notes cover several Automation Hub cloud updates from September 9 to October 14, 2024.

Improvements

• We have launched a series of performance improvements to reduce load time in the following situtations:
  • When viewing the Explore Automation Program page and the Automation Pipeline page,
  • When viewing an Idea Profile,
  • When downloading a Pipeline CSV.
• For better visibility, we are now also displaying the pipeline view count under the name of the view.
• We have updated the permissions for the System Admin role to match those of the Account Owner role.

What's fixed

• We have resolved an issue where downloading large amounts of data from the Cost Report dashboard resulted in a network error with the following message: Network Error, please check your internet connection. The fix helps you download large data sets successfully, without interruption.
• We have addressed an issue where users without any roles or tenant-level permissions were unable to create or edit personal saved views. Now, users can create and edit their personal saved views without needing any specific permissions.
• We have resolved an issue where not all users were displayed in the tenant when attempting to share pipeline views.
• We have identified and addressed an issue where uploading an .ahw file could sometimes result in an error due to references to deleted roles.
• We have updated the pipeline page so that you can view the number of different processes in various stages at any time. This helps you gain better visibility of the entire pipeline and make quick decisions on where to focus your efforts.
• We have fixed a bug where some ideas could not be deleted.
• We have fixed an issue where the Category filter in the Automation pipeline did not work properly.
• We have resolved an issue that was preventing you from deleting the "Analysis" phase of your custom idea flow.
• We have resolved an issue with the data displayed in the Automation Hub internal dashboards, such as the Automation Program Performance dashboard. The dashboard sometimes displayed an incorrect number of ideas in the Live phase compared to the actual pipeline.
• We have resolved an issue with the CSV output of Automation Hub > Automation Ideas. Previously, the CSV file contained double quotation marks for columns such as Phase, Status, and others. We have implemented a fix to ensure that the CSV output is now correctly formatted without unnecessary quotation marks.
• We have resolved an issue where System Admin users were unable to edit or delete idea flows despite having the necessary permissions.
• We have resolved an issue where some users were experiencing duplicate ideas in the Explore Automation Program after a migration.
• We have resolved an issue where the selected assessment option in a Change Request was not displayed after selection.
• We have resolved an issue where the Date submitted field was not displaying the local date and time. Now, the display will render the local date and time automatically.
• We have resolved an issue where large tenants occasionally experienced delays or failures when downloading CSV files. The download process has been optimized to handle large datasets efficiently.
• We have fixed an issue where some changes were not displayed in History when editing applications via API.
• We have resolved an issue with the OpenAPI date conversion in the Automation Hub Pipeline API.
• When editing applications via API, some changes were not displayed in History.
• We have fixed an issue where the idea's submission date displayed the wrong value.
• We have fixed an issue where loading all columns in the pipelines occasionally resulted in a 431 Request Header Fields Too Large error.
• When users attempted to submit an idea, they encountered a blank screen. This issue occured specifically when the idea flow was submitted from a file, rather than created from scratch.
• We have resolved an issue where moving an automation from Live -> In production to Live -> Decommissioned resulted in duplicate records. This issue has been fixed, and automations will now be handled correctly without creating duplicates.
• We have fixed an issue that caused inconsistencies between the number of processes fetched by OpenAPI and the actual number of items.