Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
From version 212.1
edited by Carlijn Kokkeler
on 2024/03/25 14:39
Change comment: There is no comment for this version
To version 102.1
edited by Erik Bakker
on 2023/08/15 12:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -217 - Template Tango
1 +203 - Fast Paced
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,17 +1,19 @@
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 the scalability and stability of our infrastructure. On top of that, we will release several minor changes with a potentially significant impact.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.217 - Template Tango||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.203 - Fast Paced.WebHome||target= "blank"]].
4 4  
5 -=====New features=====
6 -
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 dynamic trigger for each model and environment, allowing users to edit this trigger.
10 -
11 11  =====Minor changes=====
12 12  
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.
7 +* Create - Integrations: Improved the performance of adding or removing API gateway integrations for split entry configurations. (#1023)
8 +* Manage - Alerting: Identifiers of triggers are now visible in the edit screen.
14 14  
15 15  ====Bug fixes====
16 16  
17 -* Deploy - Runtime Overview: The runtime overview has been improved with respect to checks on the runtime version. (#1243)
12 +* Create - Flows: Fixed an issue where removing some split entry flows from Create phase was not possible after splitting your all entry/combined entry flow. (#1016)
13 +* Deploy - Releases: We fixed an issue that your release contains a JMS server flow twice with different build version numbers when adding another flow to your release. (#597)
14 +* Deploy properties: When a user activates a release containing nested properties and the property is not created, we show it now as missing. On top of that, we add the property placeholder after the user tries to activate the release.
15 +
16 +=====Infra and image changes=====
17 +
18 +* Infrastructure: Tightened security policies for a more secure infrastructure.
19 +* Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower