Skip to Content

Changes for page 247.1 - Help Out

Last modified by Erik Bakker on 2025/06/25 19:51
From version 256.1
edited by Erik Bakker
on 2025/06/02 09:26
Change comment: There is no comment for this version
To version 80.1
edited by Erik Bakker
on 2023/05/12 09:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -246 - Preparation Paradise
1 +197 - Pay Attention
Content
... ... @@ -1,18 +1,26 @@
1 -In our previous release, we released functionality to increase the stability of Windows runtimes. This time we followed that up by adding additional safety measures on runtime level. On top of that we have several pieces now available to prepare for pending changes on our event streaming offering. Furthermore, we introduced several small improvements on the platform.
1 +Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.246 - Preparation Paradise.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]].
4 4  
5 -====Minor Changes====
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.
6 6  
7 -* Deploy - General: Updated the Java arguments that will be applied to Windows containers, to align better with the limits that are applied to the containers and therefore improve stability of these containers.
8 -* Deploy - Architecture: You can now manually set the memory of your on-premise machine in design architecture. This memory is considered when checking the machine's health in "Deploy architecture."
9 -* General - Runtime: We have two updates on runtime level.
10 -** A new [[runtime image>>doc:Main.Release Information.Runtime Images.V331.WebHome||target="blank"]] is available that adds support for consuming Kafka topics based on a ‘topics’ pattern instead of a fixed list of topic names.
11 -** A new runtime version that updates our Java runtime version from Java 17.0.13 to Java 17.0.15. This is primarily a security update.
9 +=====Minor changes=====
12 12  
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.
14 +
13 13  ====Bug fixes====
14 14  
15 -* Create - Flow designer: We have fixed a bug where you could not add a new entry flow to a ‘SOAP Entry Connector’ enabled system.
16 -* Manage - Error Messages: Non-working download button for payload content files has a more descriptive error message text. (#886)
17 -* Manage - Explore (Queue Browser): Updated styling for the action buttons related to the debug functionality. (#1653)
18 -* Q&A Forum - General: You will no longer receive an email notification about your own comment on a post on the Q&A forum. (#1462)
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.
22 +* Design - Message Definitions: "Message format" button is also available in view mode. (#919)
23 +
24 +====Remarks====
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.