Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 140.1
edited by Carlijn Kokkeler
on 2023/10/23 16:48
Change comment: There is no comment for this version
To version 145.1
edited by Carlijn Kokkeler
on 2023/10/24 09:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,20 +4,30 @@
4 4  
5 5  =====Minor changes=====
6 6  
7 -* 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.
8 8  * Design - Message Mapping: The button 'Import from Store' will directly open the store.
9 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking.
8 +* Design - Performance: Performance improvements for the Flow Designer have been implemented.
9 +* Create - Flow Designer: When importing items from the store, flowfragments that are hidden in Design will be listed under the versions in Create. (#1044)
10 +* Create - Flow Designer: Resources without name won't trigger error messages when users select components. (#950)
11 +* Create - Flow Designer: We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
12 +* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read only mode.
13 +* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
14 +* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
15 +* 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)
10 10  * Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
11 11  * Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
18 +* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946)
19 +* 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%. 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%. 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.
20 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
21 +* 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)
12 12  
13 -
14 -
15 15  ====Bug fixes====
16 16  
17 -* 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.
25 +* 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)
26 +* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
27 +* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
28 +* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
18 18  
19 19  
20 -
21 21  =====Infra and image changes=====
22 22  
23 23  * 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.