Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 195.1
edited by Carlijn Kokkeler
on 2023/10/23 15:13
Change comment: There is no comment for this version
To version 196.1
edited by Carlijn Kokkeler
on 2023/10/23 15:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -31,7 +31,7 @@
31 31  Pages to add the new components have been created. Forms have been created nicely with proper help texts. The EHCache cache manager has been removed.
32 32  
33 33  == **Metrics Storage Duration** ==
34 -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.
34 +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.
35 35  
36 36  [[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
37 37  
... ... @@ -38,20 +38,27 @@
38 38  == **Feedback Items** ==
39 39  
40 40  //__Import from store__//
41 -Design - Message Mapping: The button 'Import from Store' will directly open the store instead of showing a pop asking whether the store should be opened.
41 +The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened.
42 42  
43 -//__Save and cancel buttons__//
44 -The Save and Cancel buttons have been placed slightly further apart from each other to avoid misclicking.
43 +//__Save and cancel buttons placement__//
44 +The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
45 45  
46 46  //__User session times__//
47 -Manage - Monitoring: The user session times for 3rd generation runtime dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour.
47 +The user session times for 3rd generation runtime dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour.
48 48  
49 +//__Cancel and next buttons order//
50 +The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
49 49  
50 50  
51 51  == **Bug Fixes** ==
54 +//__Topic and event-processor names__//
55 +The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
52 52  
57 +//__System alignment__//
58 +The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases.
53 53  
54 -
60 +
61 +
55 55  == **Fancy Forum Answers** ==
56 56  
57 57  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: