Changes for page 236 - Another Agent

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Max Verstappen
	1	+192 - Small Step

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -1,33 +1,24 @@
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.
	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.209 - Max Verstappen.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	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 - 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.
10		-
11	11	=====Minor changes=====
12	12
13		-* Deploy - Releases: We sped up the process of preparing runtime images in the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
14		-* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
15		-* Manage - Monitoring: The queue browser now displays milliseconds in the timestamps.
16		-* Manage - Alerting: Alerts will only be generated for queues that are created and managed by the eMagiz JMS server.
	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 (#562)
	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.
17	17
18	18	====Bug fixes====
19	19
20		-* Create - Flow Designer: An issue has been fixed in the flow designer where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
21		-* Create - Flow Designer: We added a migration step to set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
22		-* Deploy - Deployment plan: We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped.
23		-* Manage - Monitoring - We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that has just migrated to the next generation architecture.
	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
24	24
25		-====Infra and image changes====
	21	+====Remarks====
26	26
27		-* Infra: New logging feature enabling us to make better choices in encryption standards.
	23	+* Mendix Runtime has been upgraded to Mendix 9.22.0.
28	28
29		-
30		-
31		-
32		-
33		-