Changes for page 262 - Good News

Last modified by Erik Bakker on 2026/02/23 08:06

From version 318.1
edited by Erik Bakker
on 2026/02/23 08:05
Change comment: There is no comment for this version
To version 314.1
edited by Erik Bakker
on 2026/02/20 13:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,7 +17,7 @@
17 17  
18 18  ==== Bug fixes ====
19 19  
20 -* Create - Flow Designer: When using DSH support objects, the required admin-only fields are automatically filled in. (#1755)
20 +* Create - FlowDesigner: When using DSH support objects, the required admin-only fields are automatically filled in. (#1755)
21 21  * Create - Untransfer integration: We fixed an issue where you could not remove an integration of the Mendix connector system, which was migrated from the Legacy eMagiz Mendix Connector to the current eMagiz Mendix Connector in Create.
22 22  * Design - Catalog: Help texts related to “content”, “Json format”, and “Gateway message definition” are updated. (#1082)
23 23  * Create - Store: When importing a store component with properties, validation feedback will now be provided if the property value does not align with the expected type. (#1276)
... ... @@ -25,4 +25,4 @@
25 25  
26 26  ==== Remarks ====
27 27  
28 -* General - Infrastructure: We updated our image builder for Windows images to use the latest Java versions for images. Effectively, this means that any image built for Windows from this release onwards that uses a base image //3.4.0// or above, will use Java 21.0.10 as baseline. Images below version //3.4.0// will now use Java 17.0.18. Therefore, new (property) releases that use the same eMagiz base image, will still use a different Java version, and may therefore have some changed behavior. Normally that would not be noticable, but since these Java version increases drops support for some weak cipher suites, connectivity may be affected. For more information, please refer to the release notes of image 3.5.1.
28 +* Generic: When retrieving information from our infrastructure about available customer agents, we improved performance by reducing the amount of data we retrieve and process.