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 14.1
edited by Erik Bakker
on 2022/06/16 13:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Time Saver
1 +56
Parent
... ... @@ -1,1 +1,1 @@
1 -Main.Release Information.Portal.WebHome
1 +Main.Release Information.Build numbers.WebHome
Content
... ... @@ -1,23 +1,17 @@
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 improves platform error handling.
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  
6 +===== Major Changes =====
8 8  
8 +* Multiple improvements to the 'Error to XML transformer' to prevent error messages from growing too large in certain circumstances, which could negatively impact performance and stability:
9 + ** Removed the 'omit stack trace' functionality: this option wasn't used in eMagiz (defaulted to 'true') and would significantly increase the size of errors by including full stack frame info (Java class names, method names, line numbers, etc).
10 + ** Message history is now truncated to 100 entries max (keeping the first and last 50). Normally message history would never reach this limit, but when building (potentially infinite) loops in eMagiz flows it was possible to create humongous 'history' headers.
11 + ** Message headers are now truncated to 40 entries max (keeping the first 40 headers alphabetically).
12 + ** XML validation errors are now truncated to 40 entries max (keeping the first 40 validation errors reported by the underlying validation engine).
13 + ** "Caused by" exception chains are now truncated to a maximum depth of 5 levels. In normal circumstances exceptions would not be expected to reach this limit, but flows with incorrectly configured custom (recursive) error handling could cause extremely long exception chains.
14 +
9 9  ===== Minor Changes =====
10 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 -===== Bug Fixes =====
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.
23 -
17 +* Updated bundle 'com.emagiz.components.error' from 7.0.0 to 7.1.0