Skip to Content

Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06
From version 35.1
edited by Erik Bakker
on 2022/12/06 16:11
Change comment: There is no comment for this version
To version 281.1
edited by Erik Bakker
on 2025/09/21 21:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +253 - Rince Repeat
Content
... ... @@ -1,29 +1,21 @@
1 -The release brings a private store to our community and makes the latest runtime image available for our customers running on the 3rd generation architecture. Furthermore, we introduce several improvements to our 3rd generation runtime and its interaction with the portal.
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>>Main.Release Information.Release Blogs.189 - Private Eye.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 -=====New features=====
6 -* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
5 +==== Major Changes ====
7 7  
8 -=====Major changes=====
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)
9 9  
10 -* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your jms-server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
9 +==== Minor changes ====
11 11  
12 -=====Minor changes=====
11 +* 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 +* 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.
13 13  
14 -* Create - Event Streaming: Event streaming is now available for models migrating to the 3rd generation runtime.
15 -* Create - Transformation: source filter on attribute with empty field is more readable in read-only mode. (#732)
16 -* Create - Migration: Improved compatibility checks related to the 3rd generation runtime migration.
17 -* Deploy - Check properties: Informative error messages when saving or creating a property. (#576)
18 -* Deploy - Deployment plan: We improved the deployment plan to avoid crashing the server when executing a deployment plan.
19 -* Deploy - Architecture: Added reset feature for 3rd generation runtimes.
16 +==== Bug fixes ====
20 20  
21 -====Bug fixes====
22 -* Create - Settings: We fixed an issue where changing the connection type did not update all relevant flows.
23 -* Create - Flow designer: Newly generated flows were configured with incorrect resource locations under specific circumstances.
24 -* Deploy - User management: Fixed an issue where 'Apply to environment' would take very long to finish.
25 -* Deploy - Deployment plan: While generating a default plan, flow type steps will not be created for OSGi runtimes that run on a Docker machine. (#798)
26 -* Deploy - Architecture: Cloud slots now wake up without potential need to apply to environment.
27 -
28 -====Remarks====
29 -* Mendix Runtime has been upgraded to Mendix 9.19.0.
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)