Skip to Content

Changes for page 169 - Check, Act

Last modified by Carlijn Kokkeler on 2024/05/22 13:50
From version 1.1
edited by Erik Bakker
on 2022/05/05 14:03
Change comment: There is no comment for this version
To version 7.1
edited by Erik Bakker
on 2022/06/16 12:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Building Time
1 +Automation Activation
Content
... ... @@ -1,33 +1,31 @@
1 -Version 175, released 2022-04-29
1 +Release that introduces a visual refresh on the Capture widget. In addition, this release includes several other improvements and tackles some minor issues.
2 2  
3 -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.
3 +To benefit from the improvements, please make sure to clear your browser cache (Ctrl+Shift+Del) before signing in the first time.
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/]]
5 +Find out more in our [release blog]
6 6  
7 7  
8 -===== Major Changes =====
8 +===== New features =====
9 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.
10 +* Built-in support for EDI messages
11 + ** Design - System: EDI is a new message format supported in eMagiz. You can select this as the default option when editing a system or when editing a system message. Note that, this option is supported only for Generation 3 runtimes.
12 + ** Create - Flow designer: The autogenerated definitions and transformations components are customized so that EDI to XML validations and transformations are possible. Note that in this version the filter will not work with the eMagiz message definitions if they use multiple namespaces, in that case, a custom XSD should be used.
15 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'.
16 +* Deploy - Releases: Improved performance for deploying releases using the deployment plan.
17 +* Capture - Requirements Designer: The requirements designer got a visual refresh. Furthermore, new (multi-tenant) systems can now be created by clicking the blue rectangles in the left panel, rather than by dragging them in.
18 +* Design - System Message Definition: Importing message definitions from store with multiple namespaces is supported.
19 +* Deploy - Releases. You are now able to prevent releases to be deleted (either by eMagiz or manually) by enabling the block autodeletion feature per release. This can be done for at most 3 releases in total. (#587)
20 +* Create - Flow designer: Improved the help texts of HTTP outbound components to clarify the exact working of the ‘encoding mode’ setting.
23 23  
24 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.
25 +* Deploy - Releases: We fix a small issue that adds an onramp (or an offramp) that is linked to an exit/entry connector to a release at a later moment. (#442)
26 +* Community - Q&A: The richtext editor no longer adds a break line when you change a style of text.
27 +* Create - Transformation: Fixed the position of the ‘View XSLT Button’ that in some cases was not correct.
28 +* Manage - Dashboard: The popup with detailed information on errors did not work for certain types of errors. (#583)
29 +* Deploy - Releases: You will not see an error in “Outdated Flows” pop-up if your release has outdated flows.
30 +* The help text is appearing correctly when clicking attributes on a page.
29 29  
30 -
31 -===== Remarks =====
32 -
33 -* Mendix Runtime has been upgraded to Mendix 9.12.1.