Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35

From version 233.1
edited by Erik Bakker
on 2025/03/10 09:59
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 -240 - Spring Cleaning
1 +2411 - Wild West
Content
... ... @@ -1,13 +1,10 @@
1 -In the last sprint, we focused on tidying up our house to prepare for various cool things later this year. As a result, we have a series of improvements and bug fixes for you to enjoy.
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.240 - Spring Cleaning.WebHome||target="blank"]].
3 +====Bug fixes====
4 4  
5 -====Minor Changes====
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.
6 6  
7 -* Overall UI/UX: Alerts / Notifications now have an icon before the text to further emphasize the meaning.
8 -* Overall UI/UX: We have updated our badge, switch, and progress bar components.
8 +====Remarks====
9 9  
10 -====Bug fixes====
11 -
12 -* Create - Flow Creation: We have changed the auto-creation behavior for entry gates. This means we now avoid creating functionality in these entry gates only relevant for flows running inside a Mendix app.
13 -* Create - Reset Infra: Infra flows for systems labeled as a "Mendix Connector" can now be reset once more under all circumstances, including when your model utilizes the code mapping functionality.
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.