Changes for page 237.1 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 49.1
edited by Erik Bakker
on 2023/02/16 08:49
on 2023/02/16 08:49
Change comment:
There is no comment for this version
To version 85.1
edited by Erik Bakker
on 2023/06/05 16:03
on 2023/06/05 16:03
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -19 2-Small Step1 +199 - Home Improvements - Content
-
... ... @@ -1,29 +1,20 @@ 1 - The release introduces twonewfeatures forour3rdgeneration runtime. Subsequently,wewillreleaseseveral minorfeedbackpointsand bugfixes.1 +In the last sprint cycle we have focused on improving various aspects of the portal functionality. Among others we focused on the next-generation architecture, the store, security and certificate management. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.19 2-Small Step.WebHome||target= "blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.199 - Home Improvements.WebHome||target= "blank"]]. 4 4 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. 8 - 9 -=====Major changes===== 10 - 11 -* Create - Flow Designer: We applied a new setting for the JMS flow where the JMS flow will try to shrink the journal files to 50, so it does not end up with a high amount of JMS files that take too long to read. For this to be applied, please reset your JMS flow and deploy the new version on your model. 12 - 13 13 =====Minor changes===== 14 14 15 -* 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. 16 -* 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. 17 -* Deploy- User Management: Transfer from design button imports users and roles 18 -* 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. 7 +* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately 3 months before the expiration dates of event streaming users' access certificates. 8 +* Deploy - Release: After successful machine deployments, unused runtime images will be automatically removed. This can be disabled by changing the machine step in your deployment plan. 9 +* Manage - Monitoring: HTTP statistics page now displays all of the resources. 10 +* Manage - Alerting: congestion control wil be enabled by default with 10 alerts per 10 minutes and user cannot see or change it. 11 +* General - Infra: Changed the library used for storing metadata in the eMagiz Control Tower. 19 19 20 - 21 21 ====Bug fixes==== 22 22 23 -* Deploy/Monitoring- Debugger: We haveimproved theerror handlingonthedebugger functionalityto ensure itdoes not showtheerrorcodeandtechnicalerroranymore.24 -* Deploy/Monitoring- Debugger:Pressingthe"Stopdebugger"buttonnowfunctionscorrectly15 +* Create - Store: Spring Reserved words that contain * are not incorrectly replaced with the prefix of the flow. 16 +* Manage - Monitoring: When an application failed to start, not all log messages were visible in the manage phase. 25 25 26 26 ====Remarks==== 27 27 28 -* Mendix Runtime has been upgraded to Mendix 9.22.0. 29 - 20 +* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.