Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 574.9
edited by Danniar Firdausy
on 2024/07/01 14:29
Change comment: There is no comment for this version
To version 574.2
edited by Danniar Firdausy
on 2024/07/01 13:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,12 +3,16 @@
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.
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 +
8 8  == **Feedback Items** ==
9 -//__Retention duration and bytes requirements__//
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.
11 +//__SwaggerUI default__//
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.
11 11  
14 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
15 +
12 12  //__Used message types__//
13 13  It is now possible to filter the message types in Capture on whether they are used.
14 14