Skip to Content

Changes for page 273 - Squash Squash

Last modified by Erik Bakker on 2026/07/27 11:44
From version 348.1
edited by Erik Bakker
on 2026/07/27 11:44
Change comment: There is no comment for this version
To version 250.1
edited by Erik Bakker
on 2025/05/07 15:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -273 - Squash Squash
1 +244 - Forgotten Frontiers
Content
... ... @@ -1,19 +1,19 @@
1 -This release includes various smaller improvements throughout the various phases of the platform. On top of that, we have updated certain parts of our Mendix project to their respective latest version.
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.
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.273 - Squash Squash.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.244 - Forgotten Frontiers.WebHome||target="blank"]].
4 4  
5 -==== Minor Changes ====
5 +====Major Changes====
6 6  
7 -* Deploy - History (Releases): Introduced various changes to this overview to make the information we show here more specific. The main changes are that we show a full timestamp in the “When” column instead of the date itself, and the “eye” icon is only present when the registered audit log exceeds a predefined length. (#1779)
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)
8 +* Create - Add Integrations: We have updated the functionality behind the "Add Integration" overview to support the following deletion cases better. (#1378)
9 +** Users cannot un-transfer an integration in the Create phase if another user is editing a part of the flow attached to the integration.
10 +** Users cannot un-transfer the last integration of a System in the Create phase if another user is editing the connector infra.
11 +** 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.
8 8  
9 -===== Bug Fixes ====
13 +====Bug fixes====
10 10  
11 -* Design - Message Mapping: Bug fix for the Design Message mapping right-panel where, if the number of errors exceeded a certain threshold, it would push the bottom bar out of the viewing window. Also properly aligned action buttons.
12 -* Design - Architecture: We fixed an inconsistency that prevented users from adding a multi-runtime system to their Design Architecture.
13 -* Deploy - Container overview: We fixed an inconsistency in this overview that would incorrectly mark the deployed version as unexpected. Furthermore, we have renamed this overview to better align with what we show. (#1673)
14 -* Manage - Queue dashboards: Fixed detailed message throughput graph with spikey first and last observations. (#1763)
15 -* Manage - Alerting - Triggers (Notification Settings): Improved user feedback and interaction when no recipient is selected, preventing users from pressing Save. (#1765)
16 -
17 -==== Remarks ====
18 -
19 -* Updated various UI related modules within our Mendix project to their respective latest version.
15 +* 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)
16 +* 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)
17 +* 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.
18 +** 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.
19 +** 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.