Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
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 141.1
edited by Carlijn Kokkeler
on 2023/10/23 16:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,29 +1,29 @@
1 -The release introduces two new features for our 3rd generation runtime. Subsequently, we will release several minor feedback points and bug fixes.
1 +In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
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.207 - Aligned State .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 -
13 13  =====Minor changes=====
14 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.
7 +* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 +* Design - Performance: Performance improvements for the Flow Designer have been implemented.
9 +* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
10 +* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
11 +* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
12 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
13 +* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946)
14 +* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
15 +For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
16 +The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
17 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
18 +* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
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
22 +* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
23 +* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
25 25  
26 -====Remarks====
27 27  
28 -* Mendix Runtime has been upgraded to Mendix 9.22.0.
29 29  
27 +=====Infra and image changes=====
28 +
29 +* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.