Skip to Content

Changes for page 61

Last modified by eMagiz on 2022/08/18 16:25
From version 12.1
edited by eMagiz
on 2022/08/18 16:25
Change comment: There is no comment for this version
To version 2.1
edited by Erik Bakker
on 2022/05/05 14:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -61
1 +Building Time
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.Release Information.Build numbers.WebHome
1 +Main.Release Information.Portal.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -1,22 +1,31 @@
1 -Small update that fixes three specific issues.
1 +Release that brings flow testing and JSON support improvements and a new build number with runtime bug fixes. In addition, this release includes several other improvements and tackles some minor issues. To benefit from the improvements, please make sure to clear your browser cache (Ctrl+Shift+Del) before signing in the first time.
2 2  
3 -Release date - August 19th 2022
3 +Find out more on our release blog here: [[https:~~/~~/www.emagiz.com/en/release-blog-en/175-building-time-release-blog/>>https://www.emagiz.com/en/release-blog-en/175-building-time-release-blog/]]
4 4  
5 +
6 +===== Major Changes =====
7 +
8 +* This release brings build number 61 with several runtime improvements.
9 +** The OAuth 2.0 authorization interceptor in the Rest Template component contained client 'Authentication methods’ that were invalid and caused a flow not to start in build 59. Also the clockskew is now configurable so we can handle the requirements of more oauth2 authentication providers.
10 +** The Amazon S3 authentication interceptor in the Rest Template component had a threading issue where the key would be invalid on heavy usage. The threading has been changed and is now behaving correctly.
11 +** In several flow designer components, you can add Groovy scripts. Since build 59 using FastStringUtils (JSON parsing) in Groovy scripts did not work.
12 +** For Gen3 runtimes we upgraded to Spring Boot 2.6.6 to bring the latest security patches.
13 +
14 +
5 5  ===== Minor Changes =====
6 6  
7 -* Updated bundle 'com.emagiz.bundles.groovy-all' from 3.0.9.1 to 3.0.9.2
8 -* Removed bundle 'com.sun.mail.javax.mail' because it was not used anymore
9 -* Updated bundle 'com.emagiz.components.security' from 7.1.1 to 7.2.0
10 -* Updated bundle 'com.emagiz.components.http' from 7.2.1 to 7.2.2
11 -* Updated bundle 'com.emagiz.util.codec' from 6.1.0 to 6.1.1
17 +* Create - Flow designer: Message Definitions: Added JSON Array support for JSON message definitions. Using this, you can have an array of simple values based on an entity.
18 +* Create - Flow testing: Flow testing has better support for components that use flow resources like groovy scripts or database initialization scripts.
19 +* Create - Flow testing: Flow testing was not compatible with flows that contain queued message channels.
20 +* Manage - Monitoring: We removed the obsolete statistics screens 'Channel statistics', 'Handler statistics', and 'Cloud statistics'.
12 12  
22 +
13 13  ===== Bug Fixes =====
14 14  
15 -* The OAuth 2.0 authorization interceptor in the Rest Template component contained client 'Authentication methods’ that were invalid and caused a flow not to start in build 59. Also the clockskew is now configurable so we can handle the requirements of more oauth2 authentication providers.
16 -* The Amazon S3 authentication interceptor in the Rest Template component had a threading issue where the key would be invalid on heavy usage. The threading has been changed and is now behaving correctly.
17 -* In several flow designer components you can add Groovy scripts. Since build 59 using FastStringUtils (JSON parsing) did not work.
18 -* For Gen3 runtimes we upgraded to Spring Boot 2.6.6 to bring the latest security patches.
25 +* Design - Message Mapping: We fixed an issue where some warnings were showing as errors in right panel.
26 +* Create - Flow Designer: Improved transformation of JSON messages when 2 similar structures in the source message definition are mapped to the same structure in the output definition.
19 19  
20 -==== Known issues ====
21 -* In case a flow doesn't start properly and that flow contains HTTP components, please try to create a new flow version from Create and use that version in your release. In some specific cases, a duplicate chain error message could appear that indicates this specific case.
22 22  
29 +===== Remarks =====
30 +
31 +* Mendix Runtime has been upgraded to Mendix 9.12.1.