Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 49.1
edited by Erik Bakker
on 2023/02/16 08:49
Change comment: There is no comment for this version
To version 287.1
edited by Erik Bakker
on 2025/10/21 10:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +255 - Fine Form
Content
... ... @@ -1,29 +1,21 @@
1 -The release introduces two new features for our 3rd generation runtime. Subsequently, we will release several minor feedback points and bug fixes.
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. Additionally, we will release a new **[[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]]** for selected customers and on our flow testing engine.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.192 - Small Step.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.255 - Fine Form.WebHome||target="blank"]].
4 4  
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.
5 +==== Minor changes ====
8 8  
9 -=====Major changes=====
7 +* General - Runtime: A new [[runtime image>>Main.Release Information.Runtime Images.V340.WebHome||target="blank"]], for selected customers, and our flow testing will be made available.
8 +* General: The user can now see the names of deactived users again across the platform (i.e. flow history, Q&A). (#1163)
9 +* Deploy - Releases: We have updated the editing release behaviour for the Event streaming pattern. You now have more flexibility for you to add or remove either Event streaming processor flow(s) or Event streaming Mendix connector flow(s) in the release.
10 +** Additionally, we have also fixed the issue where adding or removing event streaming flow(s) resulted in incorrect flow(s) being included or excluded. This update ensures that the correct Event streaming flow(s) are now properly managed during release editing.
11 +* Create - Add Integrations: Users can un-transfer event streaming integrations that have the default message type messaging by using the ‘Create/Settings/Transfer settings from design/ES Integrations’. (#1485)
10 10  
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.
13 +==== Bug fixes ====
12 12  
13 -=====Minor changes=====
15 +* Design - Model Designer: Changed “align top“ and “align left“ to “align horizontally“ and “align vertically“ to be consistent with similar functionality in the Flow Designer. (#1611)
16 +* Create - Settings: The SOAP settings tab allows syncing the SOAP settings of systems in Design and Create. (#1569)
17 +* Create - Transformation: Updated the pattern used in dateTime transformations for the +HH:mm format. These used to fall back to +HHmm instead (dropping the ':'), this has now been resolved. (#1368)
18 +** Existing transformations are not automatically updated, but if you are using a custom XPath to do the transformation right now, you can now use the default functionality again.
19 +** The updated pattern (using XXX instead of ZZ) does not work on the previous generation runtime. If you are still using the previous generation runtime, and you have edited the specific part of the transformation, you can instead use the custom XPath where you use the pattern that is composed when using the dropdown menus, and replacing the XXX at the end with ZZ
14 14  
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 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 -