Skip to Content

Changes for page 256 - Power Up

Last modified by Erik Bakker on 2025/11/04 12:44
From version 282.1
edited by Erik Bakker
on 2025/09/21 21:33
Change comment: There is no comment for this version
To version 233.1
edited by Erik Bakker
on 2025/03/10 09:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -253 - Rince Repeat
1 +240 - Spring Cleaning
Content
... ... @@ -1,22 +1,13 @@
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.
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.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.253 - Rince Repeat.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.240 - Spring Cleaning.WebHome||target="blank"]].
4 4  
5 -==== Major Changes ====
5 +====Minor Changes====
6 6  
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)
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 8  
9 -==== Minor changes ====
10 +====Bug fixes====
10 10  
11 -
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.
15 -
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.
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.