Changes for page 245 - Limited Exposure

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-245 - Limited Exposure
	1	+239 - Modern Talking

Content

...	...	@@ -1,15 +1,18 @@
1		-In the last sprint, we released increased stability on 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, we focused on testing the eMagiz Mendix Connector and solving internal feedback on the process and the connector itself. With that behind us, we are ready to launch the new eMagiz Mendix Connector in our community. With this release, we will make it available for all new Mendix systems in models running on the current-generation architecture. In a future release, we will bring a migration wizard aiding a simple and smooth migration to the new eMagiz Mendix Connector. On top of that, we have some minor updates to improve the quality of the platform.
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.239 - Modern Talking.WebHome||target="blank"]].
4	4
	5	+====New Features====
	6	+
	7	+* New Mendix connector: We will introduce a new eMagiz Mendix connector. This new connector delivers improved stability and a simpler setup process. It is better integrated into your eMagiz models and will receive full support. The connector can be used for new systems and will be enabled by default for new models.
	8	+** A migration wizard will be released later, allowing you to quickly and smoothly migrate your legacy Mendix connectors to the new Mendix connector.
	9	+** We will publish the new module to the Mendix Marketplace on **February 28.**
	10	+
5	5	====Minor Changes====
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)
	13	+* Create - Flow Designer: The view button that can be found by navigating to the right panel of the Flow Designer and choosing the Support Objects tab opens a pop-up that shows a list of all support objects that can be added. This button is accessible only in the view mode of the Flow Designer. (#870)
10	10
11	11	====Bug fixes====
12	12
13		-* 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)
14		-* 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)
15		-* 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 Creation: When creating the corresponding infra and entry flows belonging to a system that will host a SOAP endpoint, we fixed a bug causing two support objects to break upon creation. (#1517)
	18	+* Manage - Dashboard: The manage phase dashboard no longer breaks when an error occurs in a component with an id that does not follow the {{code}}[id].[system].[flow]{{/code}} convention, or when that value is longer than expected. (#1566)