Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 49.1
edited by Erik Bakker
on 2023/02/16 08:49
Change comment: There is no comment for this version
To version 325.1
edited by Carlijn Kokkeler
on 2024/09/25 16:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +230 - Petite Peaks
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,29 +1,13 @@
1 -The release introduces two new features for our 3rd generation runtime. Subsequently, we will release several minor feedback points and bug fixes.
1 +During our recent sprint cycle, we improved the functionality of adding an integration to an existing API in Design, ensured that queues with illegal characters will not generate errors anymore, and we fixed an issue where the execution of a deployment step would be blocked. Read all about it below!
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.192 - Small Step.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.230 - Petite Peaks||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.
5 +====New features====
6 +* All - Failover: We have introduced a new failover feature, allowing you to enable failover on messaging flows with minimal setup required. Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more on our documentation page (LINK).
8 8  
9 -=====Major changes=====
8 +====Minor changes====
9 +* Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
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 -=====Minor changes=====
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.
19 -
20 -
21 21  ====Bug fixes====
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
25 -
26 -====Remarks====
27 -
28 -* Mendix Runtime has been upgraded to Mendix 9.22.0.
29 -
12 +* Manage - Explore: Queues with illegal characters will not generate errors anymore. As a result they can be explored and if needed removed from your model.
13 +* Deploy - Deployment: We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.