Skip to Content

Changes for page 254 - Other One

Last modified by Erik Bakker on 2025/10/09 11:13
From version 261.1
edited by Erik Bakker
on 2025/06/05 09:53
Change comment: Renamed back-links.
To version 282.1
edited by Erik Bakker
on 2025/09/21 21:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -246 - Preparation Paradise
1 +253 - Rince Repeat
Content
... ... @@ -1,17 +1,22 @@
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 the runtime level. Additionally, we have several pieces now available to prepare for pending changes to our event streaming offering. Furthermore, we introduced several minor improvements to the platform.
1 +This release features various updates to our platform, with a user-centric focus, as we work on wrapping up improved functionality for our new event streaming broker. All those improvements will be shared in the future once everything is ready.
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>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]].
4 4  
5 -==== Minor Changes ====
5 +==== Major Changes ====
6 6  
7 -* Deploy - General: Updated the Java arguments applied to Windows containers to align with the container limits, thereby improving the stability of these containers.
8 -* General - Runtime: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V332.WebHome||target="blank"]] is available.
9 -** This adds support for consuming Kafka topics based on a ‘topics’ pattern instead of a fixed list of topic names.
10 -** This updates our Java runtime version from Java 17.0.13 to Java 17.0.15. This is primarily a security update.
7 +* Deploy -> Containers: The user can now easily see the containers a flow should run on in Deploy → Containers via the button in the flow grid. Furthermore, we have overhauled the user experience on this overview to align with recent improvements to other parts of Deploy. (#976)
11 11  
9 +==== Minor changes ====
10 +
11 +
12 +* Manage - Alerting - Triggers: Removed the deprecated, eMagiz-defined log trigger specified under the ‘other’ tab for Log entries. This trigger would generate an alert in the event of a runtime crash due to memory issues or failure to deliver a message.
13 +** Since the release of our new log alerting, it is possible to specify this alert rule yourself under the ‘logs’ tab if you still wish to receive these alerts. To do so, create four new log triggers as shown in our [[release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]]
14 +* Manage - Alerting - Triggers: Introduced a new ‘Quotas’ tab, where the quota limits for metrics, log, and error messages can be viewed per environment.
15 +
12 12  ==== Bug fixes ====
13 13  
14 -* Create - Flow designer: We have fixed a bug where you could not add a new entry flow to a ‘SOAP Entry Connector’ enabled system.
15 -* Manage - Error Messages: The non-working download button for payload content files now displays a more descriptive error message text. (#886)
16 -* Manage - Explore (Queue Browser): Updated styling for the action buttons related to the debug functionality. (#1653)
17 -* Q&A Forum - General: You will no longer receive an email notification about your comments on posts in the Q&A forum. (#1462)
18 +* Create - Flow Testing: Validation message is changed to make it more transparent to the user why they could not set the desired name for the flow test message. (#1702)
19 +* Create - Flow designer: You can no longer view the save button on a standard aggregator component while not in “Start Editing“ mode (#1703)
20 +* Deploy - Releases: Height of the release details pop-up is fixed to keep it consistent between all releases, including the Create Phase Release. (#1706)
21 +* API Management - Swagger (UI): NonEmptyString is now correctly represented in the swagger resource in Create, and therefore the Swagger UI that API users can check for details. (#1652)
22 +** When the user wants to use the Swagger resource with the correct information, one of the API flows in Create requires a flow version push.