Skip to Content

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
Change comment: There is no comment for this version
To version 154.1
edited by Carlijn Kokkeler
on 2023/11/21 12:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -245 - Limited Exposure
1 +209 - Max Verstappen
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,18 +1,37 @@
1 -In the last sprint, we released functionality to increase the stability of Windows runtimes. This means that those runtimes are now better limited in the memory they can utilize to prevent resource limitations on the machine level. Furthermore, we introduced several small improvements on the platform.
1 +In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components and we did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.245 - Limited Exposure.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.WebHome||target="blank"]].
4 4  
5 -====Minor Changes====
5 +=====Runtime release notes=====
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 +There is a new eMagiz Mendix connector available because a memory leak was found, only affecting Mendix connectors that have been migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture. For specific information, please check out this link to the [[release notes>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime/eMagiz%20Mendix%20Connector%20-%206.0.2/]]
13 13  
9 +=====Minor changes=====
10 +
11 +* Design - Message Mapping: The button 'Import from Store' will directly open the store.
12 +* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
13 +* Create - Flow Designer: When importing items from the store, flow fragments that are hidden in Design will be listed under the versions in Create. (#1044)
14 +* Create - Flow Designer: Resources without names won't trigger error messages when users select components. (#950)
15 +* Create - Flow Designer: A migration step has been added, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
16 +* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read-only mode.
17 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
18 +* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
19 +* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
20 +* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
21 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
22 +* Manage - Data Sink: The data sink page has been moved to the “Explore” tab. (#946)
23 +* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of the configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
24 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
25 +* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
26 +
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)
29 +* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
30 +* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
31 +* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
32 +* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
33 +
34 +
35 +=====Infra and image changes=====
36 +
37 +* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.