Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 323.1
edited by Carlijn Kokkeler
on 2024/09/23 13:48
Change comment: There is no comment for this version
To version 228.1
edited by Carlijn Kokkeler
on 2024/04/23 12:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -230 - Petite Peaks
1 +219 - Creation Carousel
Content
... ... @@ -1,10 +1,13 @@
1 -During our recent sprint cycle, we improved the functionality of adding an integration to an existing API in Design, ensured that queues with illegal characters will not generate errors anymore, and we fixed an issue where the execution of a deployment step would be blocked. Read all about it below!
1 +In the last sprint cycle, we focused on releasing new [[environment templates>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for docker single and double lane. Moreover, we have worked on a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] that contains a fix regarding SFTP sessions. Furthermore, we developed a new version of our eMagiz Mendix connector to support Mendix version 10 and higher. Lastly, we did several bug fixes.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.230 - Petite Peaks||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.219 - Creation Carousel||target="blank"]].
4 4  
5 -====Minor changes====
6 -* Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
5 +=====New features=====
7 7  
8 -====Bug fixes====
9 -* Manage - Explore: Queues with illegal characters will not generate errors anymore.
10 -* Deploy - Deployment: We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
7 +* Architecture: Several components are affected by the migration to Spring 6. Please check out our [[release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]] for specifications.
8 +* 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"]].
9 +
10 +=====Minor changes=====
11 +* Manage - Monitoring: Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
12 +* Deploy - Cloud: Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
13 +