Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 421.1
edited by Carlijn Kokkeler
on 2024/03/25 12:28
Change comment: There is no comment for this version
To version 424.1
edited by Carlijn Kokkeler
on 2024/03/25 14:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -12,8 +12,8 @@
12 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>>doc:Main.Release Information.Cloud Templates.R14 Docker - Double Lane.WebHome||target="blank"]].
13 13  
14 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.
15 +//__Dynamic trigger__//
16 +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.
17 17  
18 18  [[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
19 19  
... ... @@ -27,11 +27,11 @@
27 27  [[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
28 28  
29 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 -
30 +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 the following:
31 +{{info}}
32 32  * Only H2 databases that are registered under the standard eMagiz data folder will be removed.
33 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.
34 +* For on-premise runtimes, only a reset of the runtime is needed.{{/info}}
35 35  
36 36  [[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
37 37