Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 289.1
edited by Carlijn Kokkeler
on 2024/08/12 11:58
Change comment: There is no comment for this version
To version 51.1
edited by Erik Bakker
on 2023/02/17 08:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -227 - Fix Frenzy
1 +192 - Small Step
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,16 +1,24 @@
1 -During our recent sprint cycle, we have ......
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.227 - Fix Frenzy||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====
6 -* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview.
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.
7 7  
9 +=====Minor changes=====
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.
15 +
8 8  ====Bug fixes====
9 -* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking.
10 -* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
11 -* Create - Message Definitions: The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions.
12 -* Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted.
13 -* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version.
14 -* Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
15 -* Manage - Alerting: You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly.
16 -* Manage - Alerting: We have fixed a case where a tenant-queue-trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime.
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
20 +
21 +====Remarks====
22 +
23 +* Mendix Runtime has been upgraded to Mendix 9.22.0.
24 +