Skip to Content

Changes for page 273 - Squash Squash

Last modified by Erik Bakker on 2026/07/27 11:44
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 348.1
edited by Erik Bakker
on 2026/07/27 11:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +273 - Squash Squash
Content
... ... @@ -1,29 +1,19 @@
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 includes various smaller improvements throughout the various phases of the platform. On top of that, we have updated certain parts of our Mendix project to their respective latest version.
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.273 - Squash Squash.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 +* Deploy - History (Releases): Introduced various changes to this overview to make the information we show here more specific. The main changes are that we show a full timestamp in the “When” column instead of the date itself, and the “eye” icon is only present when the registered audit log exceeds a predefined length. (#1779)
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.
9 +===== Bug Fixes ====
12 12  
13 -=====Minor changes=====
11 +* Design - Message Mapping: Bug fix for the Design Message mapping right-panel where, if the number of errors exceeded a certain threshold, it would push the bottom bar out of the viewing window. Also properly aligned action buttons.
12 +* Design - Architecture: We fixed an inconsistency that prevented users from adding a multi-runtime system to their Design Architecture.
13 +* Deploy - Container overview: We fixed an inconsistency in this overview that would incorrectly mark the deployed version as unexpected. Furthermore, we have renamed this overview to better align with what we show. (#1673)
14 +* Manage - Queue dashboards: Fixed detailed message throughput graph with spikey first and last observations. (#1763)
15 +* Manage - Alerting - Triggers (Notification Settings): Improved user feedback and interaction when no recipient is selected, preventing users from pressing Save. (#1765)
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.
17 +==== Remarks ====
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 -
19 +* Updated various UI related modules within our Mendix project to their respective latest version.