Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 441.1
edited by Carlijn Kokkeler
on 2024/04/08 12:40
Change comment: There is no comment for this version
To version 418.1
edited by Carlijn Kokkeler
on 2024/03/25 11:44
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
... ... @@ -3,31 +3,38 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
6 +**Hi there, eMagiz developers!**
7 7  
8 +== **Cloud Template R12 Docker - Single Lane** ==
9 +This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here.
8 8  
9 -== **Spring 6 Migration** ==
10 -As announced in our previous release blogs, we will release 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 in our release that will be released on April 11th, 2024, which is this release.
11 +== **Cloud Template R14 Docker - Double Lane** ==
12 +This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found here.
11 11  
12 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
13 -* JDBC BoneCP data source
14 -* SSL web service message sender
15 -* Web service outbound gateway
16 -* SFTP session factory
17 -* HTTP components message sender
18 -* Job manager
19 -* Credentials
20 -* Simple job launcher
21 -* Default SFTP session factory
14 +== **Feedback Items** ==
15 +//__Custom trigger__//
16 +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.
22 22  
23 -Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
18 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
24 24  
25 -In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]].
20 +//__Copy to clipboard buttons__//
21 +Copy to clipboard buttons have been added to various pages:
26 26  
27 -This large maintenance update, 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 image 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"]].
23 + * Deploy agent pop-up
24 + * Create - Flow designer: Properties
25 + * Deploy - Property releases: Property details
28 28  
29 -== **Feedback Items** ==
27 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
30 30  
29 +//__Reset H2 database__//
30 +For the current generation architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following:
31 +
32 +* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
33 +* 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.
34 +* For on-premise runtimes, only a reset of the runtime is needed.
35 +
36 +[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
37 +
31 31  == **Bug Fixes** ==
32 32  //__Runtime overview improvements__//
33 33  The runtime overview has been improved regarding checks on the runtime version.