Skip to Content

Changes for page 220 - Patch Parade

Last modified by Carlijn Kokkeler on 2024/05/22 13:30
From version 219.1
edited by Carlijn Kokkeler
on 2024/04/08 14:57
Change comment: There is no comment for this version
To version 210.1
edited by Carlijn Kokkeler
on 2024/03/25 12:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +217 - Template Tango
Content
... ... @@ -1,13 +1,17 @@
1 -In the last sprint cycle, we focused on releasing a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. Please refer to our new [[runtime image>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Apart from this, we have improved event streaming logging, such that these logs are not cluttered with irrelevant information anymore. Moreover, we have removed the deprecated cloud option 'Root' from the portal.
1 +In the last sprint cycle, we focused on improving the event streaming graph. Moreover, we have done some bug fixes. First of all, the validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.218 - Sprightly Spring||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.217 - Template Tango||target="blank"]].
4 4  
5 5  =====New features=====
6 6  
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>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]].
7 +* Create - Flow Designer & Deploy: Copy to clipboard buttons have been added to various pages.
8 +* Deploy - Cloud Templates: New Cloud Templates are available for single and double environments to introduce the ability to clean H2 databases from the portal. Please check out the [[cloud template release notes>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
9 +* Manage - Alerting: The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a custom trigger for each model and environment, allowing users to edit this trigger.
9 9  
10 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  
13 +* Deploy - Architecture: For the current generation 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.
14 +
15 +====Bug fixes====
16 +
17 +* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)