Skip to Content
Last modified by Erik Bakker on 2026/05/06 23:07
From version 50.1
edited by Erik Bakker
on 2023/02/17 08:04
Change comment: There is no comment for this version
To version 330.1
edited by Erik Bakker
on 2026/04/20 22:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +266 - Feel Free
Content
... ... @@ -1,24 +1,31 @@
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 has a significant impact on users. Both in delivering functional value to our end users and in moving away from a legacy construct within our platform, and taking the UI one step into the future. On top of that, we have squashed some bugs. Sadly, however, we also have to announce that the announced **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** in [[release 264>>doc:Main.Release Information.Release Blogs.264 - Strict Separation.WebHome||target="blank"]] has been pulled due to not meeting quality standards. Having said that, enjoy reading our latest updates on the platform.
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.266 - Feel Free.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 -=====Minor changes=====
7 +* General - Event Streaming: To authenticate at DSH, our event streaming broker, we use certificates. These certificates have an expiration date, so they must be rotated. We have introduced a new way of rotating these certificates for you.
8 +** Proxy certificates must always be valid in DSH to prevent clients from encountering issues. A scheduled event runs daily during working hours to verify this.
9 +** If certificate rotation fails in the test environment, it will **not** continue to the acceptance or production environments.
10 +* General - Platform: Improved our general deletion behavior when deleting a model.
11 +* Create - System: We now show the parent entity when selecting an entity or attribute in the right panel. This allows a user to identify better where in the message's structure they currently are. (#1520)
12 +* Create - Add Integrations: Improved how we autogenerate flows for the user.
13 +* Deploy - Release: Creating a new release automatically puts you in “edit mode” for that release. (#672)
10 10  
11 -* 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.
12 -* 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.
13 -* Deploy- User Management: Transfer from design button imports users and roles
14 -* 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.
15 +==== Bug fixes ====
15 15  
16 -====Bug fixes====
17 +* Capture - Integration: Users are prevented from clicking the "Save integration" button too fast after creating a new message type to prevent a timing issue resulting in an error. The save button at the integration level is inactive until a message type is set for that integration. (#531)
18 +* Design - Catalog: The default request body is generated automatically for the POST operation when added as an integration in the Design phase.
19 +* Design - Edit an API integration - New/Edit resource: Added reserved keywords for the path of a resource, which can no longer be used. (#1585)
20 +* Create - Transformation - Custom XSLT snippet: Trying to save a newly edited XSLT snippet is only possible in “Edit mode”. (#1670)
21 +* Deploy - Architecture: Fixed an issue in the execution of the environment upgrade for models that have API MAM.
22 +* Deploy - Upgrade: Fixes a bug where the portainer agent could not be updated, as part of the environment template procedures, for Windows systems where portainer is installed on another drive than C:\. [CSP-1922]
23 +* Deploy - History: Entries stating 'null' will no longer be shown. (#1479)
24 +* Manage - Monitoring - HTTP Statistics (Other metrics): The mean and max for the response time are split into two graphs. (#1200)
25 +* Manage - Monitoring - Log Entries: The search/reset buttons are disabled while the reset/search is still being processed. (#1538)
17 17  
18 -* 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.
19 -* Deploy/Monitoring - Debugger: Pressing the "Stop debugger" button now functions correctly
27 +==== Remarks ====
20 20  
21 -====Remarks====
22 -
23 -* Mendix Runtime has been upgraded to Mendix 9.22.0.
24 -
29 +* General - Infrastructure: An update has been applied to the internal communication with the eMagiz-managed authorization server.
30 +* General - Platform: An update has been applied across the platform regarding the UI. As a result, all reference selectors have been replaced with combo boxes, aligning with current best practices and enabling users to interact with the platform more effectively.
31 +** Slightly modified the creation of new message types by implementing a new type of input widget that combines drop-down selection functionality with actions.