Skip to Content

Changes for page 268 - Underlying Update

Last modified by Erik Bakker on 2026/05/18 16:45
From version 334.1
edited by Erik Bakker
on 2026/05/18 11:25
Change comment: There is no comment for this version
To version 282.1
edited by Erik Bakker
on 2025/09/21 21:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -268 - Underlying Update
1 +253 - Rince Repeat
Content
... ... @@ -1,19 +1,22 @@
1 -This release includes significant improvements regarding our internal platforms. This includes improvements in the DSH proxy certifcate rotation process. On top of that, it introduces a new version of Mendix on which we are running and various updates on underlying libaries. Subsequently, we have introduced a fix for the stability of our documentation platform. Enjoy reading our latest updates on the platform.
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.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.268 - Underlying Update.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]].
4 4  
5 -==== Minor Changes ====
5 +==== Major Changes ====
6 6  
7 -* General - Event Streaming: Various updates regarding the proxy certificate rotation process.
8 -** Proxy certificates must always be valid in DSH so clients do not face any issues. A schedule event runs daily during working hours to verify this.
9 -** If certificate rotation fails in the test environment, it will not continue to ACCP and PROD
10 -* General - Feedback Functionality: Updated the feedback functionality. Although this changes the user process it should allow you to provide more elaborated feedback.
7 +* Deploy -> Containers: The user can now easily see the containers a flow should run on in Deploy → Containers via the button in the flow grid. Furthermore, we have overhauled the user experience on this overview to align with recent improvements to other parts of Deploy. (#976)
11 11  
12 -==== Bug fixes ====
9 +==== Minor changes ====
13 13  
14 -* General - User Access Control: While users are being deactivated, they are also being removed from the models unless they are the contact person for the model. (#943)
15 -* Create - Documentation Portal: A stability improvement will be rolled out for our documentation website.
16 16  
17 -==== Remarks ====
12 +* Manage - Alerting - Triggers: Removed the deprecated, eMagiz-defined log trigger specified under the ‘other’ tab for Log entries. This trigger would generate an alert in the event of a runtime crash due to memory issues or failure to deliver a message.
13 +** Since the release of our new log alerting, it is possible to specify this alert rule yourself under the ‘logs’ tab if you still wish to receive these alerts. To do so, create four new log triggers as shown in our [[release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]]
14 +* Manage - Alerting - Triggers: Introduced a new ‘Quotas’ tab, where the quota limits for metrics, log, and error messages can be viewed per environment.
18 18  
19 -* Upgraded our main application to Mendix 10
16 +==== Bug fixes ====
17 +
18 +* Create - Flow Testing: Validation message is changed to make it more transparent to the user why they could not set the desired name for the flow test message. (#1702)
19 +* Create - Flow designer: You can no longer view the save button on a standard aggregator component while not in “Start Editing“ mode (#1703)
20 +* Deploy - Releases: Height of the release details pop-up is fixed to keep it consistent between all releases, including the Create Phase Release. (#1706)
21 +* API Management - Swagger (UI): NonEmptyString is now correctly represented in the swagger resource in Create, and therefore the Swagger UI that API users can check for details. (#1652)
22 +** When the user wants to use the Swagger resource with the correct information, one of the API flows in Create requires a flow version push.