Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 218.1
edited by Carlijn Kokkeler
on 2023/10/24 11:37
Change comment: There is no comment for this version
To version 223.1
edited by Carlijn Kokkeler
on 2023/10/24 11:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -33,8 +33,6 @@
33 33  == **Metrics Storage Duration** ==
34 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 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.
35 35  
36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
37 -
38 38  ((((% border="3" cellpadding="10" cellspacing="10" style="width:400px" %)
39 39  |=(% style="width: 120px;" %)Future|=(% style="width: 180px;" %)Minute level|=(% style="width: 180px;" %)Hour level
40 40  |(% style="width:120px" %) Production|(% style="width:180px" %) 30 days|(% style="width:180px" %) 1 year
... ... @@ -45,13 +45,13 @@
45 45  == **Feedback Items** ==
46 46  
47 47  //__Import from store__//
48 -The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened.
46 +The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
49 49  
50 50  //__Save and cancel buttons placement__//
51 51  The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
52 52  
53 53  //__User session times__//
54 -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.
52 +The user session times for next generation architecture 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.
55 55  
56 56  //__Cancel and next buttons order__//
57 57  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.
... ... @@ -66,7 +66,7 @@
66 66  Performance improvements for the Flow Designer have been implemented.
67 67  
68 68  //__Properties with special characters__//
69 -When a user would migrate to gen3 and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
67 +When a user would migrate to the next generation architecture and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
70 70  
71 71  //__Hidden flow fragements__//
72 72  When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
... ... @@ -75,8 +75,7 @@
75 75  Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components.
76 76  
77 77  //__Error channel for all inbounds__//
78 -If there is no custom error handling, Gen3 migration would set the error channel to “errorChannel” only for the first inbound in an entry flow.
79 -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.
76 +If there is no custom error handling, next generation migration would set the error channel to “errorChannel” only for the first inbound in an entry flow. 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.
80 80  
81 81  //__Highlighting resources__//
82 82  The performance of highlighting resources of selected components is improved in Read only mode.
... ... @@ -93,9 +93,9 @@
93 93  Besides checking error header, the error trigger is now configured to check if an error message contains a term.
94 94  
95 95  //__Alerting__//
96 -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%.
97 -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%.
98 -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.
93 +For the next generation architecture models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
94 +For the next generation architecture 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%.
95 +The next generation architecture 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.
99 99  
100 100  //__Unused containers__//
101 101  Containers are set inactive when they are unused and removed in Design.
... ... @@ -110,7 +110,7 @@
110 110  * [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
111 111  * [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
112 112  * [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
113 -* [[3rd generation runtime with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
110 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
114 114  
115 115  
116 116  == **Key takeaways** ==