Skip to Content

Changes for page 263 - User Update

Last modified by Erik Bakker on 2026/03/10 12:40
From version 320.1
edited by Erik Bakker
on 2026/03/09 13:25
Change comment: There is no comment for this version
To version 49.1
edited by Erik Bakker
on 2023/02/16 08:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -263 - User Update
1 +192 - Small Step
Content
... ... @@ -1,20 +1,29 @@
1 -This release includes many user-driven updates to our platform to enhance your everyday work.
1 +The release introduces two new features for our 3rd generation runtime. Subsequently, we will release several minor feedback points and bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.263 - User Update.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.192 - Small Step.WebHome||target= "blank"]].
4 4  
5 -==== Minor changes ====
5 +=====New features=====
6 +* Deploy - Architecture: We add a new option per container to open a page that you can use a feature "Start / Stop flows" for runtime running on the 3rd generation runtime. Note that the debugger functionality can also be started on this view.
7 +* Manage - Monitoring: New dashboard, ‘Event streaming statistics,’ is available for you to monitor your topics and consumer groups.
6 6  
7 -* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V351.WebHome||target="blank"]] for **all** customers is available.
8 -* Create - Flow Designer: Improved the help text of the advanced ‘Match value’ attribute of the XPath filter, so it is clear how this option of the XPath filter can be used. (#1542)
9 +=====Major changes=====
9 9  
10 -==== Bug fixes ====
11 +* Create - Flow Designer: We applied a new setting for the JMS flow where the JMS flow will try to shrink the journal files to 50, so it does not end up with a high amount of JMS files that take too long to read. For this to be applied, please reset your JMS flow and deploy the new version on your model.
11 11  
12 -* Deploy - Deployment plan execution: The failure message shown during release preparation has been improved to be more descriptive. (#1568)
13 -* Deploy - Releases: We fixed an issue where the UI of the Create phase and Deploy phase were not aligned since the Releases screen did not show the new additions, but you can find them in the Release details popup. (#1675)
14 -* Manage - Explore - Topic browser: We fixed two problems with the topic browser.
15 -** When navigating to the last page of messages on a topic’s partition, the amount of messages shown in the paging will now correspond to the number of messages on that partition (#1714)
16 -** The first page of messages on a topic’s partition will now include the last message, with offset 1 below the ‘last offset’.
17 -* Manage - Export - Data sink: When opening this page on an empty data sink bucket, there will be a warning on top of the page (“no results found”). (#1096)
18 -==== Remarks ====
13 +=====Minor changes=====
19 19  
20 -* General - Portal: We have removed part of our platform's functionality as it was not used anymore.
15 +* Design- Kafka topic: As a user, you can now only define the retention size on the topic level. Based on that input value and a set of best practices eMagiz will, in turn, calculate the correct settings for you. Don't hesitate to contact your partner manager if you want to change the default settings. When applying the configured settings to your topic, we also send configuration settings for segment bytes and segment ms based on our best practice to improve performance.
16 +* Create - Flow Designer: You can make a multiple selection zone by pressing and holding the left mouse button instead of pressing the "Shift" key from now on.
17 +* Deploy- User Management: Transfer from design button imports users and roles
18 +* Deploy - Release: We improved the activation process of a release with one or more 3rd generation runtimes. As of now, we are preparing the release as the first step of deploying your release. In this overview, you can see the progress of the preparation step when you execute the deployment of a release. Note that a new deployment plan is needed to make this work.
19 +
20 +
21 +====Bug fixes====
22 +
23 +* Deploy/Monitoring - Debugger: We have improved the error handling on the debugger functionality to ensure it does not show the error code and technical error anymore.
24 +* Deploy/Monitoring - Debugger: Pressing the "Stop debugger" button now functions correctly
25 +
26 +====Remarks====
27 +
28 +* Mendix Runtime has been upgraded to Mendix 9.22.0.
29 +