Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 154.3
edited by Danniar Firdausy
on 2023/11/07 11:46
Change comment: There is no comment for this version
To version 140.1
edited by Carlijn Kokkeler
on 2023/10/23 16:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -208 - Controlled State
1 +207 - Aligned State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,24 +1,23 @@
1 -In the last sprint cycle, we focused on delivering monitoring functionality for the state generation components. On top of that, we also made several improvements on the components interfacing the users to improve the user experience aspect of our platform. Moreover, we made some bug fixes and improvements on releases in Deploy and monitoring in Manage.
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.208 - Controlled State .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 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.
7 7  * Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 -* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
9 -* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
10 -* Manage - Monitoring: There is a new page called the "State generation statistics" that is located right under the Topic statistics navigation menu, which is only shown and accessible for models that has the add-on license for state generation.
9 +* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking.
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.
12 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
13 13  
13 +
14 +
14 14  ====Bug fixes====
15 15  
16 -* 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)
17 -* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
18 -* 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)
19 -* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
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.
20 20  
21 21  
20 +
22 22  =====Infra and image changes=====
23 23  
24 24  * 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.