Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 574.11
edited by Danniar Firdausy
on 2024/07/01 14:33
Change comment: There is no comment for this version
To version 574.4
edited by Danniar Firdausy
on 2024/07/01 13:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,14 +3,18 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** Over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor.
6 +**Hi there, eMagiz developers!** In the past week, we focused our effort to improve the usability of our platform as well as addressing feedback we received from the community. More specifically, we improved user interface issues on several pages that are revolving around the description of help texts, external links in the help texts, the page layouts of help texts, pop-up pages, as well as <mention EPB-1332 here>. Next to that <mention improvements on debugging here, EZ-18118 and EZ-18285>. Finally, we also fixed an issue of incorrectly generated resource paths of Keystores and Trustores when creating an Event Processor for models that got migrated from the legacy runtime architecture to the current generation architecture.
7 7  
8 8  == **Feedback Items** ==
9 -//__Integration requirements: retention duration and bytes__//
10 -The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes.
9 +//__SwaggerUI default__//
10 +Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown.
11 11  
12 -//__Integration requirements: Help text__//
13 -Collapsing the help text of this pop-up page by clicking the "?" icon on the top right corner of the pop-up page will now correctly hide the help text pane.
12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
13 +
14 +//__Used message types__//
15 +It is now possible to filter the message types in Capture on whether they are used.
16 +
17 +[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]]
14 14  
15 15  //__Debugger duration__//
16 16  Wiretaps and debugging sessions will now collect messages for ten minutes, this used to be five. Note that the JMS server needs to be updated in order to also store the messages for ten minutes instead of five. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.