Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 230.1
edited by Carlijn Kokkeler
on 2023/10/24 16:04
Change comment: There is no comment for this version
To version 232.1
edited by Carlijn Kokkeler
on 2023/10/24 16:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -26,11 +26,11 @@
26 26  
27 27  Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.
28 28  
29 -Added support for `#JsonPath` usage in SpEL expressions.
29 +Added support for `#JsonPath` usage in SpEL expressions. With this functionality, you can access your JSON payloads in a similar way as you would access XML payloads using xPath.
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}}The library used for Code Mappings has been changed. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0. This has no consequences on a functional level. {{/warning}}
33 +{{warning}}The library used for Code Mappings has been changed. Any customer with next generation architecture runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0. This has no consequences on a functional level. {{/warning}}
34 34  
35 35  == **Metrics Storage Duration** ==
36 36  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.