Changes for page 237 - Fabulous Flow
Last modified by Erik Bakker on 2025/01/31 11:52
From version 51.1
edited by Erik Bakker
on 2023/02/17 08:05
on 2023/02/17 08:05
Change comment:
There is no comment for this version
To version 104.1
edited by Erik Bakker
on 2023/09/13 07:16
on 2023/09/13 07:16
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 - 192 -SmallStep1 +205 - World Explorers - Content
-
... ... @@ -1,24 +1,27 @@ 1 - Thereleaseintroducestwo newfeaturesforour3rdgeneration runtime.Subsequently, we will release several minorfeedbackpointsandbugxes.1 +In the last sprint cycle, we focused on what we show in Manage concerning the next-generation architecture. Furthermore, we will release a new cloud template. On top of that, we will release several minor changes with a potentially significant impact. 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.205 - World Explorers.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 +* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 8 8 9 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 (#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. 10 +* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration. 11 +* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869) 12 +* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1046) 13 +* Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80%. 14 +* Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (3rd generation only) 15 15 16 16 ====Bug fixes==== 17 17 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 18 +* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054) 19 +* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes. 20 +* Manage - Queue statistics: Models with a vast number of queues will now show all queues. This used to be cut off. (Gen3 only) 21 +* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed. 22 +* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues. 20 20 21 -====Remarks==== 22 22 23 - *MendixRuntime has beenupgraded to Mendix 9.22.0.25 +=====Infra and image changes===== 24 24 27 +* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.