Changes for page 225 - Pop-up Party
Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 230.1
edited by Carlijn Kokkeler
on 2024/04/23 13:01
on 2024/04/23 13:01
Change comment:
There is no comment for this version
To version 232.1
edited by Carlijn Kokkeler
on 2024/04/23 13:09
on 2024/04/23 13:09
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,11 +3,12 @@ 3 3 Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.219 - Creation Carousel||target="blank"]]. 4 4 5 5 =====New features===== 6 - 6 +* Design - API Gateway: The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 7 7 * Deploy - Architecture: We have released new environment templates, that ensures that on-premise machine agents are updated. Please check out the [[environment template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. 8 +* eMagiz Mendix Connector: We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 8 8 9 -* Architecture: Moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]]. 10 - 11 11 =====Minor changes===== 11 +* Create - When removing an integration from Create, the Create phase is now correctly updated. 12 +* Create - Flow Designer: Default error handling is now migrated correctly when moving to the current runtime architecture. 12 12 * Deploy - Architecture: SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. A new runtime image containing a fix is available, please check it out [[here>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]]. 13 - 14 +* Deploy - Architecture: Passwords for network volumes are now hidden on the machine after deployment.