Changes for page 208 - Controlled State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 224.1
edited by Carlijn Kokkeler
on 2023/10/24 11:54
on 2023/10/24 11:54
Change comment:
There is no comment for this version
To version 226.1
edited by Carlijn Kokkeler
on 2023/10/24 13:18
on 2023/10/24 13:18
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -17,7 +17,7 @@ 17 17 * Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers. 18 18 * Duplicate detector: support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded. 19 19 * Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher. 20 - 20 + 21 21 //__SpEL functions & JSON__// 22 22 Added SpEL functions for: 23 23 * Encoding & decoding Base64, Hex and hmac. ... ... @@ -30,6 +30,8 @@ 30 30 31 31 {{info}}The components are all configurable from the Flow Designer in Create and are accompanied by a help text explaining the use cases and the various technical configurations. Note that to make the components work in your model, a new release containing the latest image (2.0.0) needs to be deployed.{{/info}} 32 32 33 +{{warning}}Changed the library used for Code Mappings. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0{{/warning}} 34 + 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 ... ... @@ -90,9 +90,10 @@ 90 90 The error trigger is now configured to check if an error message contains a certain term, besides checking the error header. 91 91 92 92 //__Alerting__// 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. 95 +For the next generation architecture models, several adaptations to alerts have been made. 96 +* 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%. 97 +* 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%. 98 +* 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. 96 96 97 97 //__Unused containers__// 98 98 Containers are set inactive when they are unused and removed in Design.