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 89.1
edited by Erik Bakker
on 2023/06/09 10:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -246 - Preparation Paradise
1 +199 - Home Improvements
Content
... ... @@ -1,18 +1,19 @@
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 +In the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, the store, security, and certificate management.
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.199 - Home Improvements.WebHome||target= "blank"]].
4 4  
5 -====Minor Changes====
5 +=====Minor changes=====
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.
7 +* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store.
8 +* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899)
9 +* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately three months before event streaming users' access certificates expire.
10 +* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan.
11 +* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960)
12 +* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.
13 +* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.
12 12  
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: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864)
18 +* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937)
19 +