Skip to Content

Changes for page 237 - Fabulous Flow

Last modified by Erik Bakker on 2025/01/31 11:52
From version 12.1
edited by Erik Bakker
on 2022/10/24 12:01
Change comment: There is no comment for this version
To version 151.1
edited by Carlijn Kokkeler
on 2023/10/26 12:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -186 - Daemon Switch
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,25 +1,37 @@
1 -Release that brings the new monitoring stack to fruition and brings various updates to handling multiple namespaces. On top of that, we have released a sleuth of smaller feedback items 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 we 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.186 - Daemon Switch.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 - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
5 +=====Runtime release notes=====
7 7  
7 +There is a new eMagiz Mendix connector available because a memory leak was found, only affecting Mendix connectors that have been migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture.
8 +
8 8  =====Minor changes=====
9 9  
10 -* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
11 - ** Datagids, where there is now on hover action for example.
12 - ** Pop ups
13 - ** Context menus, also have on hover action
14 - ** Styling of scrollbars
15 - ** Warning, info and error context labels.
16 -* Message Redelivery - admin logs improved to better analyze issues when they occur
17 -* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
18 -* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
11 +* Design - Message Mapping: The button 'Import from Store' will directly open the store.
12 +* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
13 +* Create - Flow Designer: When importing items from the store, flow fragments that are hidden in Design will be listed under the versions in Create. (#1044)
14 +* Create - Flow Designer: Resources without names won't trigger error messages when users select components. (#950)
15 +* Create - Flow Designer: A migration step has been added, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
16 +* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read-only mode.
17 +* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
18 +* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
19 +* 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 7, 14 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)
20 +* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
21 +* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
22 +* Manage - Data Sink: The data sink page has been moved to the “Explore” tab. (#946)
23 +* 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 the 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.
24 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
25 +* 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 20  ====Bug fixes====
21 -* Deploy - Deployment plan. Performance of page to deploy a release increased significantly
22 -* Store - Import resources was incorrectly done in specific cases, which is now fixed
23 -* Store - Target namespace will be imported when importing an XML Message Definition
24 -* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.
25 -* Store - Importing items from the store sometimes resulted in invalid JMS connection factories.
28 +
29 +* 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)
30 +* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
31 +* 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)
32 +* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
33 +
34 +
35 +=====Infra and image changes=====
36 +
37 +* 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.