Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 239.1
edited by Carlijn Kokkeler
on 2023/10/26 10:36
Change comment: There is no comment for this version
To version 233.1
edited by Carlijn Kokkeler
on 2023/10/25 14:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -24,7 +24,7 @@
24 24  
25 25  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`.
26 26  
27 -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>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Create your transformations.advanced-create-your-transformations-xpath-advanced||target="blank"]].
27 +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.
28 28  
29 29  {{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}}
30 30  
... ... @@ -86,11 +86,11 @@
86 86  //__System alignment__//
87 87  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. This will be done for existing systems as well.
88 88  
89 -//__Error alerting__//
89 +//__Error checking__//
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, several adaptations to triggers have been made.
93 +For the next generation architecture models, several adaptations to alerts have been made.
94 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 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 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.
... ... @@ -101,8 +101,6 @@
101 101  //__Error popups when promoting a release version__//
102 102  We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
103 103  
104 -{{warning}}There is a new eMagiz Mendix connector available because a memory leak was found, only affecting customers that have been fully migrated to the next generation architecture. It is advised to upgrade to the new eMagiz Mendix connector before fully migrating to the next generation architecture. {{/warning}}
105 -
106 106  == **Fancy Forum Answers** ==
107 107  
108 108  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: