Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 164.1
edited by Carlijn Kokkeler
on 2023/11/23 08:56
Change comment: There is no comment for this version
To version 239.1
edited by Erik Bakker
on 2025/04/04 08:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -209 - Max Verstappen
1 +2411 - Wild West
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,28 +1,10 @@
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 +In this additional unplanned release, we have corrected two problems within the platform that were causing problems for our customers. On top of that, we updated our infrastructure in light of a recently discovered vulnerability in one of the underlying platforms we use.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]].
4 -
5 -=====New features=====
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.
10 -
11 -=====Minor changes=====
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.
16 -
17 17  ====Bug fixes====
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.
5 +* Overall - Feedback: Since our previous release, it has been impossible to issue feedback on our platform due to a tightened security policy. This problem has been fixed with this release.
6 +* Deploy - Releases: Due to our newly introduced feature regarding comparing properties, we lost performance when activating releases in models containing Mendix systems. As a result, users experienced delays in waiting for eMagiz to finish this process. This problem has been fixed with this release.
22 22  
8 +====Remarks====
23 23  
24 -
25 -
26 -
27 -
28 -
10 +* In light of a vulnerability discovered in one of the underlying platforms we use, we took proactive actions to safeguard our infrastructure against this even better.