Skip to Content

Changes for page R13 - Double Lane

Last modified by Erik Bakker on 2022/06/16 13:13
From version 6.1
edited by Erik Bakker
on 2022/06/16 12:11
Change comment: There is no comment for this version
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 -Time Saver
1 +60
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.Release Information.Portal.WebHome
1 +Main.Release Information.Build numbers.WebHome
Content
... ... @@ -1,23 +1,14 @@
1 -Release that brings flow testing available for Gen3 API management flows. In addition, this release includes several other improvements across the portal.
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.
3 +Find out more in our [release blog]
4 4  
5 -Find out more on our release blog here:
6 -https://www.emagiz.com/en/release-blog-en/173-time-saver-release-blog/
7 7  
8 -
9 -===== Minor Changes =====
10 -
11 -* Design - CDM: Save and add new button added for new entity attributes. (#203)
12 -* Create - Flow testing: Flow testing is now enabled for API management flows designed to run Gen3 runtimes.
13 -* Deploy - Properties: You can not create properties with reserved property names.
14 -
15 -
16 16  ===== Bug Fixes =====
17 17  
18 -* Design - Data/Message modeling: You can only delete data model entities that are not part of a message definition. (#601)
19 -* Create - JMS flow: Artemis server connection settings are generated correctly in a failover setup for build number 60 and higher. You need to reset your JMS flows in order to generate them with correct settings.
20 -* Manage - Code mapping: Fixed an issue where custom attributes on CDM code mappings were not saved. (#604)
21 -* Manage - Error Messages: You can select multiple or all messages at the time and assign a status. (#428)
22 -* Fixed that the Create, Deploy & Manage screen layouts sometimes rendered incorrectly until the cache was refreshed manually.
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.
23 23  
12 +===== Minor Changes =====
13 +
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]".