Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 48.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 160.1
edited by Carlijn Kokkeler
on 2023/11/22 14:57
on 2023/11/22 14:57
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 192 -SmallStep1 +209 - Max Verstappen - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,29 +1,33 @@ 1 - The release introducestwo newfeatures for our3rdgeneration runtime.Subsequently, wewillrelease severalminorfeedbackpoints and bug fixes.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. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 192 -SmallStep.WebHome||target=3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.209 - Max Verstappen.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. 8 8 9 -=====Major changes===== 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 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 -* De sign- Kafka topic: As a user, youcannow only definetheretentionsizeonthetopiclevel. Basedonthatinputvalue and a setof bestpracticeseMagiz will, inturn, calculatetheorrectsettingsfor you. Don'tsitatetocontactyourpartnermanagerif you wantto changethedefault settings.When applyingtheconfigured settingstoyour topic, welso send configurationsettings forsegmentbytesand segment msbasedonurbestpracticeto improveperformance.16 -* Create-Flow Designer:You canmakea multiplelectionzone by pressing and holdingtheleftmousebuttoninsteadofpressingthe"Shift"keyfromnowon.17 -* Deploy- UserManagement: Transferfromdesignbuttonimports usersnd roles18 -* Deploy-Release: We improvedthe activationprocess of a releasewithoneor more3rdgeneration runtimes.As ofnow, we arepreparing thereleaseasthe first step of deploying your release. Inthisoverview,youcan see the progress ofthepreparationstep when you execute thedeployment ofarelease.Notethat a newdeployment planisneededto make thiswork.13 +* Deploy - Releases: We sped up the process of preparing runtime images in executing 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. 19 19 20 - 21 21 ====Bug fixes==== 22 22 23 -* 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. 24 -* Deploy/Monitoring - Debugger: Pressing the "Stop debugger" button now functions correctly 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 of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been 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. 25 25 26 -==== Remarks====25 +====Infra and image changes==== 27 27 28 -* MendixRuntimehasbeen upgradedtoMendix9.21.0.27 +* Infra: New logging feature enabling us to make better choices in encryption standards. 29 29 29 + 30 + 31 + 32 + 33 +