Skip to Content

Changes for page 56

Last modified by Erik Bakker on 2023/01/23 13:58
From version 7.2
edited by Erik Bakker
on 2022/06/16 12:46
Change comment: Update document after refactoring.
To version 9.1
edited by Erik Bakker
on 2022/06/16 12:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -61
1 +60
Content
... ... @@ -1,31 +1,14 @@
1 -Release that introduces a visual refresh on the Capture widget. In addition, this release includes several other improvements and tackles some minor issues.
1 +Small update that fixes three specific issues.
2 2  
3 -To benefit from the improvements, please make sure to clear your browser cache (Ctrl+Shift+Del) before signing in the first time.
4 -
5 5  Find out more in our [release blog]
6 6  
7 7  
8 -===== New features =====
6 +===== Bug Fixes =====
9 9  
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.
8 +* Build number 59 broke the debugger, build number 60 fixes this.
9 +* Fixed Kafka components not being able to use key- or truststores from the "resources" tab.
10 +* Deploying flows containing a 'Jetty server' support object in build number 59 only worked on the latest runtime version: build number 60 fixes the backwards compatibility with older runtimes. Note that it is still strongly recommended to update to the latest version of the runtime (5.0.4) if you haven't done so already, because this contains fixes for the Log4j security vulnerability.
13 13  
14 14  ===== Minor Changes =====
15 15  
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.
21 -
22 -
23 -===== Bug Fixes =====
24 -
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.
31 -
14 +* Change of behaviour when incoming HTTP headers are mapped to message headers: Up to build 58 the values of incoming HTTP headers were only mapped to an array when it contained multiple values, otherwise the first (and only) value was automatically extracted and used for the message header. Since build 59 the values are always mapped to an array. While this makes the data type of the header more predictable - it is no longer dependent on the number of values a client was sending - it does mean that your SpEL expressions that were previously expecting single values need to now handle array values. In many cases this can be as simple as extracting the first array value like this: "headers.myHeader[0]".