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	+192 - Small Step

Content

...	...	@@ -1,15 +1,24 @@
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	+The release introduces two new features for our 3rd generation runtime. Subsequently, we will release several minor feedback points and bug fixes.
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.192 - Small Step.WebHome||target= "blank"]].
4	4
5		-====Minor Changes====
	5	+=====New features=====
	6	+* Deploy - Architecture: We add a new option per container to open a page that you can use a feature "Start / Stop flows" for runtime running on the 3rd generation runtime. Note that the debugger functionality can also be started on this view.
	7	+* Manage - Monitoring: New dashboard, ‘Event streaming statistics,’ is available for you to monitor your topics and consumer groups.
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)
	9	+=====Minor changes=====
10	10
	11	+* Design- Kafka topic: As a user, you can now only define the retention size on the topic level. Based on that input value and a set of best practices eMagiz will, in turn, calculate the correct settings for you. Don't hesitate to contact your partner manager if you want to change the default settings. When applying the configured settings to your topic, we also send configuration settings for segment bytes and segment ms based on our best practice to improve performance.
	12	+* Create - Flow Designer: You can make a multiple selection zone by pressing and holding the left mouse button instead of pressing the "Shift" key from now on.
	13	+* Deploy- User Management: Transfer from design button imports users and roles
	14	+* Deploy - Release: We improved the activation process of a release with one or more 3rd generation runtimes. As of now, we are preparing the release as the first step of deploying your release. In this overview, you can see the progress of the preparation step when you execute the deployment of a release. Note that a new deployment plan is needed to make this work.
	15	+
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)
	18	+* Deploy/Monitoring - Debugger: We have improved the error handling on the debugger functionality to ensure it does not show the error code and technical error anymore.
	19	+* Deploy/Monitoring - Debugger: Pressing the "Stop debugger" button now functions correctly
	20	+
	21	+====Remarks====
	22	+
	23	+* Mendix Runtime has been upgraded to Mendix 9.22.0.
	24	+