Skip to Content

Changes for page 275 - Summer Sounds

Last modified by Erik Bakker on 2026/08/24 13:37
From version 350.1
edited by Erik Bakker
on 2026/08/24 10:14
Change comment: There is no comment for this version
To version 81.1
edited by Erik Bakker
on 2023/05/16 09:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -275 - Summer Sounds
1 +197 - Pay Attention
Content
... ... @@ -1,31 +1,26 @@
1 -This release includes several smaller improvements across the platform's phases. We also updated certain parts of our Mendix project to their latest versions.
1 +Another couple of weeks have passed, so it is time for a new release. We have delivered additional minor (bug) fixes in this release and released the event streaming alerting. The last is a real improvement in managing your event streaming solution. Furthermore, you will find several enhancements in working in nextGen environments.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.275 - Summer Sounds.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.197 - Pay Attention.WebHome||target= "blank"]].
4 4  
5 -==== Minor Changes ====
5 +=====New features=====
6 +* Deploy - Cloud Templates: New Cloud Templates are available for single-lane and double-lane environments. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7 +* Manage - Alerting: Added support for providing alerts on event streaming topics: consumer lag, topic approaching maximum size & messages added to the topic under the threshold. Two new alerts are introduced to send alerting messages to the user when messages added to the topic is greater than a threshold or when topic messages consumed is below a threshold. These new alerts are applied for all runtime architectures we support. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
6 6  
7 -* General - Platform: As part of our regular system maintenance, we have upgraded the application to the Mendix LTS version 11.12.
8 -** This upgrade improves the platform's overall stability, security, and long-term reliability. This upgrade has no impact on daily operations.
9 -** This update ensures the application remains well-supported and ready for future enhancements.
10 -* General - Legacy Event Streaming Broker: Updated Kafka Broker version from 3.8.1 to 3.9.2. This is a maintenance update and should not affect any functionality.
11 -* General - eMagiz Connector: We will release a new version of the eMagiz Connector (1.2.0) that is compatible with Mendix 11 (11.12.1 and higher).
12 -* Create - Flow designer: Various updates to flow designer components are introduced in preparation for the Spring 7 migration.
13 -** Two support object components are no longer available to create in the current generation.
14 -*** Access decision manager
15 -*** OAuth2 Bearer token authentication filter.
16 -** We updated validation for a few components in preparation for the Spring 7 migration to address missing or incorrect settings after the components are saved. Note that these updated settings can lead to alerts when opening a flow that currently has an incorrect configuration
17 -*** File inbound channel adapter
18 -*** TCP inbound channel adapter
19 -*** JMS outbound gateway
20 -*** Standard content enricher > Property
21 -*** HTTP security
22 -** On top of that, some components are end of support. They are no longer used in any client model and are therefore removed from the list of selectable Flow Designer components.
9 +=====Minor changes=====
23 23  
24 -===== Bug Fixes ====
11 +* Create - Flow Testing: we add some minor UI improvements and validation to prevent a test case from being in live mode and automated.
12 +* Deploy - Deployment plan: If you run the deployment plan to deploy machines and run into issues, your deployment plan will be stopped at the step that gets a warning, and you can see a warning message on the left side. That is easier for you to figure out problems and fix them. Afterward, you can run that step again by selecting "Refresh" and "Execute."
13 +* Deploy - Architecture: We increased the grace period for shutting down runtimes when they run on Docker environments.
25 25  
26 -* Design - Architecture: Updated display order calculation for machines when adding or moving them. (#1113)
27 -* Deploy - Swagger UI: Downloaded Swagger documentation has the full correct schema. (#1811)
15 +====Bug fixes====
28 28  
29 -==== Remarks ====
17 +* Create - Store: We fixed an issue that you sometimes do not see the list of message definitions or the list of transformations when you export new or update your store item.
18 +* Deploy - Architecture: We fixed an issue were some cloud environments would not automatically wake up. (#952)
19 +* Deploy - Architecture: You can apply your changes to only one or both zones on 3rd generation double-lane models. (#947)
20 +* Deploy - Architecture: We fixed an issue where runtimes were not removed from a machine, while this was expected behavior according to the architecture.
21 +* Deploy - Architecture: The gen two karaf container will now exit when an Out-of-memory error occurs for gen three cloud environments. This will cause an auto-healing restart, after which the container can run properly again. Note that to make this functionality available a new "base image" was created which will automatically be applied to all gen two karaf containers when you create a new release and deploy it via the deployment plan causing redeployments.
22 +* Design - Message Definitions: "Message format" button is also available in view mode. (#919)
30 30  
31 -* Updated various UI related modules within our Mendix project to their respective latest version.
24 +====Remarks====
25 +
26 +* Manage - Statistics: Improved rollup and storage of metrics when running your solution in the next generation archticture. Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off.