From version 1.1
edited by Erik Bakker
on 2022/05/05 14:03
on 2022/05/05 14:03
Change comment:
There is no comment for this version
Summary
-
Page properties (4 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - Building Time1 +61 - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Main.Release Information. Portal.WebHome1 +Main.Release Information.Build numbers.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e bakker1 +XWiki.eMagiz - Content
-
... ... @@ -1,33 +1,22 @@ 1 - Version175,released2022-04-291 +Small update that fixes three specific issues. 2 2 3 -Release thatbrings flow testingandJSON support improvements and a new build number with runtime bugfixes. In addition, this release includesseveral otherimprovements and tackles some minor issues. To benefit from theimprovements, please make sure to clear your browser cache (Ctrl+Shift+Del) before signing in the first time.3 +Release date - August 19th 2022 4 4 5 -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/]] 6 - 7 - 8 -===== Major Changes ===== 9 - 10 -* This release brings build number 61 with several runtime improvements. 11 -** 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. 12 -** 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. 13 -** In several flow designer components, you can add Groovy scripts. Since build 59 using FastStringUtils (JSON parsing) in Groovy scripts did not work. 14 -** For Gen3 runtimes we upgraded to Spring Boot 2.6.6 to bring the latest security patches. 15 - 16 - 17 17 ===== Minor Changes ===== 18 18 19 -* 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. 20 -* Create - Flow testing: Flow testing has better support for components that use flow resources like groovy scripts or database initialization scripts. 21 -* Create - Flow testing: Flow testing was not compatible with flows that contain queued message channels. 22 -* Manage - Monitoring: We removed the obsolete statistics screens 'Channel statistics', 'Handler statistics', and 'Cloud statistics'. 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 23 23 24 - 25 25 ===== Bug Fixes ===== 26 26 27 -* Design - Message Mapping: We fixed an issue where some warnings were showing as errors in right panel. 28 -* 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. 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. 29 29 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. 30 30 31 -===== Remarks ===== 32 - 33 -* Mendix Runtime has been upgraded to Mendix 9.12.1.