Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 216.1
edited by Carlijn Kokkeler
on 2024/04/08 14:41
Change comment: There is no comment for this version
To version 166.1
edited by Carlijn Kokkeler
on 2023/12/04 15:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +210 - Deployment Delights
Content
... ... @@ -1,14 +1,24 @@
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 improving the speed of the deployment plan and making the next generation architecture the default. On top of that, we have worked to release new cloud templates for Docker Single Lane and Docker Double Lane, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
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.210 - Deployment Delights||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 +* Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
11 11  
9 +=====Minor changes=====
10 +
11 +* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
12 +* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images.
13 +
12 12  ====Bug fixes====
13 13  
14 -* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)
16 +* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
17 +* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
18 +* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
19 +* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
20 +* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
21 +* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
22 +* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
23 +
24 +