Changes for page 262 - Good News
Last modified by Erik Bakker on 2026/02/23 08:06
From version 81.1
edited by Erik Bakker
on 2023/05/16 09:06
on 2023/05/16 09:06
Change comment:
There is no comment for this version
To version 300.1
edited by Erik Bakker
on 2026/01/15 09:20
on 2026/01/15 09:20
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 197-Pay Attention1 +259 - Improve Infinitely - Content
-
... ... @@ -1,26 +1,21 @@ 1 - Anothercoupleofweekshavepassed,soitistimeforanew release.Wehavedelivered additionalminor (bug)fixesinthisrelease and releasedtheeventstreamingalerting. Thelastis a realimprovementinmanaging youreventstreamingsolution.Furthermore,you will find severalenhancements in workingin nextGenenvironments.1 +This release features various updates to our platform, just after the holiday season. Apart from various more minor improvements, we have also launched a new [[runtime image>>doc:Main.Release Information.Runtime Images.V350.WebHome||target="blank"]] for **all** customers. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 197-Pay Attention.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.259 - Improve Infinitely.WebHome||target="blank"]]. 4 4 5 -=====New features===== 6 -* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 7 -* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information. 5 +==== New features ==== 8 8 9 - =====Minor changes=====7 +* General - Runtime Image: Maintenance update where we primarily updated Spring Boot from version 3.4.1 to 3.5.8 and ensured all our external libraries are up-to-date. 10 10 11 -* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated. 12 -* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute." 13 -* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments. 9 +==== Minor changes ==== 14 14 15 -====Bug fixes==== 11 +* Create - Flow Designer: Selector expression is added on the channel interceptors page. (#1738) 12 +* Manage - Error Messages: Search by complete flow name functionality is added to the flows with error messages page. Additionally, the grid is updated to improve the page's appearance. (#1738) 16 16 17 -* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item. 18 -* Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952) 19 -* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947) 20 -* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture. 21 -* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments. 22 -* Design - Message Definitions: "Message format" button is also available in view mode. (#919) 14 +==== Bug fixes ==== 23 23 24 -====Remarks==== 16 +* Create - Transformation: The content section of the XSLT snippet is converted to an XML editor to beautify the field. (#1739) 17 +* Create - Transformation: Validation feedback is visualised on the flat file field right before the save action to provide clarity to the user. (#891) 18 +* Create - Transformation: The same display name was being used for two similar support objects, which caused confusion. The incorrectly labeled object has now been renamed. The second "Byte array length header (de)serializer" has been renamed to "ByteArrayRawSerializer". (#1751) 19 +* Deploy - Known Hosts String: When you create a new property and select the drop-down called “Data type”, choose the option called “Known hosting string”. Behind the “Value” field, a cog wheel appears. It leads you to a pop-up. In this pop-up, the Host and Port fields have been swapped. We did it because this ordering aligns with the common defaults used across IT systems. (#1749) 20 +* Monitoring - Runtimes: two graphs, namely “Problematic runtimes memory usage” and “Max memory usage”, are fixed and show correct information. (#1654) 25 25 26 -* Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture. Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off.