Skip to Content

Changes for page 275 - Summer Sounds

Last modified by Erik Bakker on 2026/08/24 13:37
From version 351.1
edited by Erik Bakker
on 2026/08/24 10:27
Change comment: There is no comment for this version
To version 325.1
edited by Erik Bakker
on 2026/03/22 21:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -275 - Summer Sounds
1 +264 - Strict Separation
Content
... ... @@ -1,31 +1,32 @@
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 +This release includes our new user management for models running on our latest versions of the API Gateway **and** Event Streaming offerings. Furthermore, it includes a new **[[environment template>>Main.Release Information.Cloud Templates.WebHome||target="blank"]]** that improves machine behavior in a single-lane cloud configuration when runtimes are added or removed. On top of that, we introduce several improvements that enhance and clarify the user experience throughout the platform.
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>>doc:Main.Release Information.Release Blogs.264 - Strict Separation.WebHome||target="blank"]].
4 4  
5 -==== Minor Changes ====
5 +==== Minor changes ====
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 - 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).
11 -* 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.
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.
7 +* Deploy - User management: Several new functionalities are released, improving the user experience when dealing with user management. To experience these improvements, you need to be running on the latest version of our API Gateway and/or Event Streaming offering.
8 +** When you click “Apply to environment” in Deploy > User management, a pop-up now displays all pending changes. You can select only the changes you want to apply (cherry-pick), and any related dependencies will be automatically selected. This helps prevent mistakes and ensures consistency when applying updates. With this enhancement, you can more easily and safely customize configurations per environment.
9 +** For fully migrated models (using DSH for Eventstreaming), the ‘transfer to design’ and ‘apply to environment’ buttons are combined. All changes will be shown when you press ‘apply to environment’ and will be applied when you press ‘apply’.
10 +** For fully migrated models (using API MAM for API gateway), the ‘transfer to design’ and ‘apply to environment’ buttons are combined. All changes will be shown when you press ‘apply to environment’ and will be applied when you press ‘apply’.
11 +* Deploy - Property: When saving a property, we now perform an optimization check. These improvements help reduce redundancy and keep property configurations cleaner and easier to maintain.
12 +** If other properties share the same name and value, we will recommend grouping them to improve manageability.
13 +** If any runtimes in the list of linked runtimes do not use the property, we suggest removing those runtimes from the list.
14 +** If none of the linked runtimes use the property, we recommend removing it.
15 +* Deploy - Releases: It is no longer possible to try to deploy a release that contains runtimes that are not linked to any flows in the architecture. (#1066)
16 +* Deploy - Architecture: Adding/moving/deleting containers from machines will now not replace the underlying instances. This was only the case for singlelanes. Doublelanes do not have this behaviour and are not affected.
23 23  
24 -===== Bug Fixes ====
18 +==== Bug fixes ====
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)
20 +* Design - Import XSD: Added the ability to import XSD files with an element of type 'all'. (#1146)
21 +* Design - Swagger Configuration: Errors related to the generation of the Swagger UI in eMagiz have been resolved. Users will no longer encounter errors when generating JSON (new cases). (#1424) (#1337)
22 +** Additionally, users can now define multiple tags per operation. Multiple tags should be separated using “-”. (#838)
23 +** An issue affecting the generation of examples for custom-defined schemas in the request and response body has also been fixed.
24 +** Schema validation has been extended to help prevent configuration mistakes. Existing errors related to referencing or schema definitions in the request/response body may still be present. However, when opening the edit page and clicking Save, the extended validation will be triggered. If the configuration results in an error, the validation will indicate this so it can be corrected before saving. (#924)
25 +* Create - Flow Testing: Users will get a pop-up error message related to their broken test case and will be asked to fix it. For automated test cases, a warning about broken test cases is shown to users who want to create a new version in the flow designer.
26 +* Deploy - Release Execution: The description of a manual step in the deployment plan is only shown once while deploying. (#933)
27 +* Manage - Alerting - Triggers: Fixed synchronization issue for log triggers, preventing unexpected behavior when all log triggers must be re-sent (#961)
28 28  
29 29  ==== Remarks ====
30 30  
31 -* Updated various UI related modules within our Mendix project to their respective latest version.
31 +* General - Portal: We have removed part of our platform's functionality as it was not used anymore.
32 +* General - Help Text: We have updated our help text widget to align it with the new UI options in Mendix. (#1757)