Skip to Content

Changes for page 277 - First Farewell

Last modified by Erik Bakker on 2026/09/23 16:09
From version 249.1
edited by Erik Bakker
on 2025/05/07 15:46
Change comment: There is no comment for this version
To version 359.1
edited by Erik Bakker
on 2026/09/23 16:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -244 - Forgotten Frontiers
1 +277 - First Farewell
Content
... ... @@ -1,22 +1,27 @@
1 -In the last sprint, we released several stability options, mainly regarding the deletion behavior within the platform. We also released an update to the flow configuration of Mendix systems to avoid conflicts with another module that you could be using in Mendix, the Excel Importer.
1 +This release includes many smaller improvements across the platform's various phases. It also introduces a **new** runtime image in response to several CVE reports. Furthermore, it marks the **end of support** for our Event Streaming-related alerting for models still running on our old infrastructure (Aiven).
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.244 - Forgotten Frontiers.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.277 - First Farewell.WebHome||target="blank"]].
4 4  
5 -====New Features====
5 +==== Major Changes ====
6 6  
7 -* General - Support: System admins can manually log out other users with active sessions. This is added to cover certain edge cases regarding locked flows. (#1197)
7 +* General - API MAM Migration: Topic alerting for the legacy Aiven-based Kafka topics has been marked as **End of Support**. This means the functionality will keep running as-is, but we will no longer provide support, bug fixes, or updates for this feature. This only affects customers who have not yet migrated to our new event streaming broker.
8 8  
9 -====Major Changes====
9 +==== Minor Changes ====
10 10  
11 -* Create - Add Integrations: We have updated the functionality behind the "Add Integration" overview to support the following deletion cases better. (#1378)
12 -** Users cannot un-transfer an integration in the Create phase if another user is editing a part of the flow attached to the integration.
13 -** Users cannot un-transfer the last integration of a System in the Create phase if another user is editing the connector infra.
14 -** Users can un-transfer the Exit/Entry connector in the Create phase either by selecting one of the integrations or both of the integrations of the Exit/Entry connector. This process is also successful when the Exit/Entry connector is in the Deploy phase.
11 +* General - Runtime Image: A new [[runtime image>>doc:Main.Release Information.Runtime Images.V360.WebHome||target="blank"]] for **all** customers is available.
12 +* General - UI/UX: Some UI elements have been replaced with newer versions, which should improve User experience.
13 +* Design - System Message: OpenAPI import functionality from the system message of an API integration is revised and improved. The functionality lets you select the desired path and operation to import from the selected OpenAPI file. Also, it imports both the request and response messages for the selected operation and sets them as root. (#1421)
14 +* Design - CDM: We improved the loading of data model-related information. This improves performance when interacting with larger data models.
15 15  
16 -====Bug fixes====
16 +===== Bug Fixes ====
17 17  
18 -* Design - API Data Model: Users can remove entities that were once part of a gateway message of an API operation that has been removed/un-transferred from the Create Phase. (#1577)
19 -* Create - Flow Designer: Create phase - The help text of the “Max fetch size” property of the “IMAP idle channel adapter” better reflects its behavior and usage. (#1410)
20 -* eMagiz Connector - Flow Configuration: The issue where the new eMagizConnector Mendix module would cause conflicts with the Mendix Excel Importer module has now been resolved.
21 -** If you already have a synchronous messaging flow for a Mendix connector system, this flow must be reset before creating a new release. Make sure this new version is included in your next release. Failing to do so can break error handling for these synchronous entry flows.
22 -** After setting the new release as active, the Mendix application has to be stopped and started to use the new image. This doesn’t have to be done right away, you can await the following restart.
18 +* Capture - Requirements Designer: Fixed default message format changing inappropriately. As a result, we will not change the default message format when the user previously selected a non default option (#1805)
19 +* Design - Solution Design: Event Streaming processors with errors in their message mapping are also displayed when the Design phase “Only errors” switch is enabled. (#1422)
20 +* Design - Solution Design: Sorting of the tenants on a multi-tenant system is aligned between Capture and Design. (#1736)
21 +* Design - System message: Fixed two typos found when attempting to delete and edit annotations. (#1813)
22 +* Design - Event Streaming: The prompt for entering edit mode correctly references event streaming when the integration type is event streaming. (#1780)
23 +* Create - Flow designer: We fixed an issue regarding the HTTP security support object that prevented the underlying flow from working even though the security was disabled.
24 +* Create - Properties tab: Improved the logic for property highlighting when selecting a component for properties with similar names. (#1774)
25 +* Deploy - Releases: We fixed a minor typo when a step is determined not to be relevant in the deployment plan. (#1781)
26 +* Deploy - Missing flows for runtimes: The pop-up also includes the display name of the system in Design. (#1812)
27 +* Manage - Flows With Error Messages: Filter option on the "flow with error messages" page to be carried over to the pop-up when opening the overview of a specific flow containing errors (#1766)