Skip to Content

Changes for page 245 - Limited Exposure

Last modified by Erik Bakker on 2025/05/21 09:01
From version 219.1
edited by Erik Bakker
on 2025/01/13 09:32
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 -236 - Another Agent
1 +244 - Forgotten Frontiers
Content
... ... @@ -1,20 +1,19 @@
1 -In the last sprint cycle, we focused on delivering new [[cloud templates>>Main.Release Information.Cloud Templates||target="blank"]] for docker single and docker double lane. Moreover, we have addressed several key feedback points within our platform.
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>>Main.Release Information.Release Blogs.236 - Another Agent||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 5  ====Major Changes====
6 6  
7 -* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
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 -====Minor Changes====
10 -
11 -* Create - Flow Designer: Improved help texts for the FTP & SFTP local filter options.
12 -* Deploy - Overview: Spring6 pop-up has been removed.
13 -* Manage - Alerting: The recipients tab for the new Alerting triggers has seen a small update in regards of UX: You will get an explanation when you are trying to enable notifications when no recipients are selected yet.
14 -
15 15  ====Bug fixes====
16 16  
17 -* Design - Message (CDM) Definition: The possibility of importing anything from the store in Design is now blocked when the system has no technical name yet. (#1456)
18 -* Create - Transfer Settings: You can now increase and decrease the number of runtimes for existing Systems. And transfer them from Design Architecture to Deploy Architecture. This can be done in “Create – Settings - Transfer Settings from Design”. (#1543)
19 -* Manage - Alerting: Inactive users in your model are removed from the list of selectable recipients.
20 -
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.