Changes for page 234 - Alert Adventures

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-218 - Sprightly Spring
	1	+219 - Creation Carousel

Content

...	...	@@ -1,14 +1,13 @@
1		-In the last sprint cycle, we focused on delivering new cloud templates for docker single and docker double lane. Moreover, we have added clipboard buttons to several pages, and migrated the generic alert trigger "More than 100 messages on queue over 10 minutes" to a dynamic trigger. Lastly, we enabled the removal of eMagiz infra H2 databases for connector machines, and improved the checks on the runtime versions in the runtime overview.
	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	3	Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]].
4	4
5	5	=====New features=====
6	6
7		-* Create - Flow Designer: Copy to clipboard buttons have been added to various pages.
8		-* Deploy - Releases: Copy to clipboard buttons have been added to various pages.
9		-* Deploy - Architecture: For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note that only H2 databases that are registered under the standard eMagiz data folder will be removed. Moreover, it is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime. Lastly, for on-premise runtimes, only a reset of the runtime is needed. To use this new functionality, new Cloud Templates are available in our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture for single and double environments. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
10		-* Manage - Alerting: The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
	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"]].
11	11
12		-====Bug fixes====
	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	13
14		-* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)