Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 220.1
edited by Carlijn Kokkeler
on 2023/10/24 11:39
Change comment: There is no comment for this version
To version 222.1
edited by Carlijn Kokkeler
on 2023/10/24 11:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -49,7 +49,7 @@
49 49  The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
50 50  
51 51  //__User session times__//
52 -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.
53 53  
54 54  //__Cancel and next buttons order__//
55 55  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.
... ... @@ -64,7 +64,7 @@
64 64  Performance improvements for the Flow Designer have been implemented.
65 65  
66 66  //__Properties with special characters__//
67 -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.
68 68  
69 69  //__Hidden flow fragements__//
70 70  When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
... ... @@ -73,7 +73,7 @@
73 73  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.
74 74  
75 75  //__Error channel for all inbounds__//
76 -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.
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.
77 77  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.
78 78  
79 79  //__Highlighting resources__//
... ... @@ -91,9 +91,9 @@
91 91  Besides checking error header, the error trigger is now configured to check if an error message contains a term.
92 92  
93 93  //__Alerting__//
94 -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%.
95 -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%.
96 -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.
94 +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%.
95 +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%.
96 +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.
97 97  
98 98  //__Unused containers__//
99 99  Containers are set inactive when they are unused and removed in Design.
... ... @@ -108,7 +108,7 @@
108 108  * [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
109 109  * [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
110 110  * [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
111 -* [[3rd generation runtime with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
111 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
112 112  
113 113  
114 114  == **Key takeaways** ==