Changes for page 245 - Limited Exposure
Last modified by Erik Bakker on 2025/05/21 09:01
From version 254.1
edited by Erik Bakker
on 2025/05/20 14:50
on 2025/05/20 14:50
Change comment:
There is no comment for this version
To version 200.1
edited by Carlijn Kokkeler
on 2024/02/16 12:08
on 2024/02/16 12:08
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -24 5-LimitedExposure1 +214 - System Symphony - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,18 +1,21 @@ 1 -In the last sprint, we releasedfunctionalityto increasethe stability ofWindows runtimes. This meansthat thoseruntimesarenow betterlimitedinthememorytheycanutilizetopreventresourcelimitationson the machinelevel.Furthermore,we introducedseveralsmallimprovementsontheplatform.1 +In the last sprint cycle, we focused on improving failover aspects. Moreover, we improved the history of monitoring graphs, it is now possible to view data from up to the last thirty days. Lastly, some more feedback items have been solved, and several more bug fixes have been done. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.24 5-LimitedExposure.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.214 - System Symphony||target="blank"]]. 4 4 5 -==== MinorChanges====5 +=====New features===== 6 6 7 -* Deploy - General: For current deployed Windows machines, the calculation of the memory limit of containers is updated, which will prevent memory leaks. 8 -* Deploy - Architecture: You can now manually set the memory of your on-premise machine in design architecture. This memory is considered when checking the machine's health in "Deploy architecture." 9 -* Q&A Forum - Moderation: Q&A Forum Moderators can choose to receive notifications by email about newly posted questions on the forum. (#1401) 10 -* General - eMagiz Connector: The new version is available in the Mendix Marketplace. 11 -** The eMagizConnector base image has been updated in preparation to support event streaming integrations. 12 -** The eMagizConnector Mendix module has been updated in preparation for event streaming support. 7 +* Design - CDM & System Message - It is now possible to add multiple attributes to an entity at once. (#1141) 8 +* Deploy - Architecture: We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. 13 13 10 +=====Minor changes===== 11 + 12 +* Deploy - Releases: Deletion of releases with deployed container versions will not be blocked anymore. (#1216) 13 +* Manage - Monitoring: New functionality to ensure that the monitoring graphs in Manage can show data from the last thirty days. 14 + 14 14 ====Bug fixes==== 15 15 16 -* Create - Flow designer: The help text for the "value expression" field for the "duplicate detector" support object better reflects the purpose of that field while also providing practical examples. (#1376) 17 -* Create - Flow Designer: The help text for the "virtual root "field of the "JSON source factory "support object better reflects the functionality and behavior of the field while also stating that arrays on the root level are not supported. (#1459) 18 -* General - User Access: Users with view rights in Deploy and Manage (but no rights in the other phases) can now see data in Manage grids. (#1525) 17 +* Create - Flow Designer: The help text of the Group attribute has been improved. 18 +* Create - Flow Testing: An issue has been solved where resource paths would change after running a flow test. (#802) 19 +* Deploy - Architecture: A new state 'Leader (single node)' has been added in case there is only one node for failover setup. A refresh button has been added in Group tab of "Start/Stop Flows" screen. To utilize this, a new runtime image, [[V.2.1.1>>Main.Release Information.Runtime Images.V211||target="blank"]], is needed. 20 + 21 +