Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 574.3
edited by Danniar Firdausy
on 2024/07/01 13:40
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,10 +3,8 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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
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 -have worked hard to release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]]. This image contains several bug fixes, and increases the debugger duration. Next to this, improvements have been done to the SwaggerUI settings, we have resolved more deprecated warnings to prepare for Mendix version 10, and it is now possible to filter on the use of message types in Capture. Moreover, we have done bug fixes related to viewing an XSLT and SpEL expressions used for contructing a multipart/form-data HTTP request.
9 -
10 10  == **Feedback Items** ==
11 11  //__SwaggerUI default__//
12 12  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.