Skip to Content

Changes for page 245 - Limited Exposure

Last modified by Erik Bakker on 2025/05/21 09:01
From version 250.1
edited by Erik Bakker
on 2025/05/07 15:56
Change comment: There is no comment for this version
To version 165.1
edited by Carlijn Kokkeler
on 2023/12/04 15:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -244 - Forgotten Frontiers
1 +210 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,19 +1,28 @@
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 +In the last sprint cycle, we focused on improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
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>>Main.Release Information.Release Blogs.210 - Deployment Delights||target="blank"]].
4 4  
5 -====Major Changes====
5 +=====New features=====
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)
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.
7 +* Deploy - Releases: We added the ability to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties.
8 +* Deploy - Cloud Templates: New Cloud Templates are available for docker single and double environments to introduce faster machine boot up and improved auto-healing. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 +* All - The next generation architecture is the default now. New models will use this generation as default.
12 12  
11 +=====Minor changes=====
12 +
13 +* Deploy - Releases: We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
14 +* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
15 +* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
16 +
13 13  ====Bug fixes====
14 14  
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.
19 +* Create - Flow Designer: An issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
20 +* Deploy - Deployment plan: We fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped.
21 +* Manage - Monitoring - We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
22 +
23 +
24 +
25 +
26 +
27 +
28 +