Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 145.1
edited by Carlijn Kokkeler
on 2023/10/24 09:06
on 2023/10/24 09:06
Change comment:
There is no comment for this version
To version 12.1
edited by Erik Bakker
on 2022/10/24 12:01
on 2022/10/24 12:01
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 207-AlignedState1 +186 - Daemon Switch - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,33 +1,25 @@ 1 - In thesprintcycle,wefocused ondelivering stategenerationcomponents. On top of that, wemade severalimprovementsregardingthealignment ofcomponents, and did someperformanceimprovements and bug fixes.Moreover, we made a change in the metrics storage duration.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. 2 2 3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs. 207-AlignedState.WebHome||target="blank"]].3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.186 - Daemon Switch.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. 7 + 5 5 =====Minor changes===== 6 6 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 -* 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) 16 -* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards. 17 -* 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) 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 22 22 23 23 ====Bug fixes==== 24 - 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. 29 - 30 - 31 -=====Infra and image changes===== 32 - 33 -* 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. 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.