Changes for page 247.1 - Help Out

Last modified by Erik Bakker on 2025/06/25 19:51

From version 208.1
edited by Carlijn Kokkeler
on 2024/03/25 12:18
Change comment: There is no comment for this version
To version 256.1
edited by Erik Bakker
on 2025/06/02 09:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -217 - Template Tango
1 +246 - Preparation Paradise
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,18 +1,18 @@
1 -In the last sprint cycle, we focused on improving the event streaming graph. Moreover, we have done some bug fixes. First of all, the validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected.
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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.217 - Template Tango||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.246 - Preparation Paradise.WebHome||target= "blank"]].
4 4  
5 -=====New features=====
6 -* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce the ability to clean H2 databases from the portal. Please check out the cloud template release notes for more information.
5 +====Minor Changes====
7 7  
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.
8 8  
9 -=====Minor changes=====
10 -
11 -* Manage - Monitoring: The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic. (#951)
12 -* Deploy - Releases: Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available. (#1137)
13 -
14 14  ====Bug fixes====
15 15  
16 -* Generic - Login: In the login screen, users can now press "enter" to log in when the username field is selected.
17 -* Create - Flow Designer: The validation regarding undesired spaces for components that use a queue name has been improved. (#1012)
18 -* Create - Flow Designer: An issue has been fixed where removing an onramp linked to a combined entry was impossible. (#1021)
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)