Skip to Content

Changes for page 208 - Controlled State

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

Summary

Details

Page properties
Content
... ... @@ -73,8 +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, next generation migration would set the error channel to “errorChannel” only for the first inbound in an entry flow.
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.
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.
78 78  
79 79  //__Highlighting resources__//
80 80  The performance of highlighting resources of selected components is improved in Read only mode.
... ... @@ -88,12 +88,13 @@
88 88  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.
89 89  
90 90  //__Error checking__//
91 -Besides checking error header, the error trigger is now configured to check if an error message contains a term.
90 +The error trigger is now configured to check if an error message contains a certain term, besides checking the error header.
92 92  
93 93  //__Alerting__//
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.
93 +For the next generation architecture models, several adaptations to alerts have been made.
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.