Skip to Content

Changes for page 237.1 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 112.1
edited by Erik Bakker
on 2023/09/27 18:53
Change comment: There is no comment for this version
To version 48.1
edited by Erik Bakker
on 2023/02/16 08:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Wrap Up
1 +192 - Small Step
Content
... ... @@ -1,15 +1,29 @@
1 -This release signifies our efforts to wrap up our quarter. It consists of several must-needed functionalities for specific use cases regarding the next-generation architecture.
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.206 - Wrap Up.WebHome||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 +=====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 +
5 5  =====Minor changes=====
6 6  
7 -* Deploy - Releases: The related unused images in the on-premises machines will also be removed when the release is removed.
8 -* Create - Transfer settings from Design: Added a migration step. If the custom error handling is set to false, we set the error channel to “errorChannel” for all inbounds in a flow.
9 -* Create - Transfer settings from Design: Added a check in the migration that validates whether every targetNamespace is filled in when a SOAP web service is migrated and split as part of the migration to the next-generation architecture.
10 -* Create - Transfer settings from Design: Added a check in the migration that validates whether a specific old component, the Jetty server support object, remains in a flow after the migration. If so, the user is notified that they need to take action on this.
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.
11 11  
12 -=====Infra and image changes=====
13 13  
14 -* New logging feature enabling us to make better choices in deprecating old encryption standards.
15 -* Carwash change to enable our direct connect offering for customers on the next-generation architecture.
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.21.0.
29 +