Skip to Content

Changes for page 268 - Underlying Update

Last modified by Erik Bakker on 2026/05/18 16:45
From version 165.1
edited by CarlijnKokkeler
on 2023/12/04 15:30
Change comment: There is no comment for this version
To version 335.1
edited by Erik Bakker
on 2026/05/18 11:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -210 - Deployment Delights
1 +268 - Underlying Update
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,28 +1,19 @@
1 -In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
1 +This release includes significant improvements regarding our internal platforms. This includes improvements in the DSH proxy certificate rotation process. On top of that, it introduces a new version of Mendix on which we are running, as well as various updates to underlying libraries. Subsequently, we introduced a fix to improve the stability of our documentation platform. Enjoy reading our latest updates on the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.210 - Deployment Delights||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.268 - Underlying Update.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +==== Minor Changes ====
6 6  
7 -* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
8 -* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 -* All - The next generation architecture is the default now. New models will use this generation as default.
7 +* General - Event Streaming: Various updates regarding the proxy certificate rotation process.
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 ACCP and PROD
10 +* General - Feedback Functionality: Updated the feedback functionality. Although this changes the user process, it should allow you to provide more elaborate feedback.
10 10  
11 -=====Minor changes=====
12 +==== Bug fixes ====
12 12  
13 -* Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
14 -* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
15 -* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
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 -====Bug fixes====
17 +==== Remarks ====
18 18  
19 -* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
20 -* Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.
21 -* Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
22 -
23 -
24 -
25 -
26 -
27 -
28 -
19 +* Upgraded our main application to Mendix 10