Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 290.1
edited by Carlijn Kokkeler
on 2024/08/12 12:00
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 -227 - Fix Frenzy
1 +203 - Fast Paced
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,17 +1,19 @@
1 -During our recent sprint cycle, we have ......
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.227 - Fix Frenzy||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 -====Minor changes====
6 -* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview.
5 +=====Minor changes=====
7 7  
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.
9 +
8 8  ====Bug fixes====
9 -* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking.
10 -* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
11 -* Create - Message Definitions: The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions.
12 -* Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted.
13 -* Deploy - Releases: When moving to the Deploy phase for the first time, a background action could fail, preventing deploying a release
14 -* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version.
15 -* Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
16 -* Manage - Alerting: You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly.
17 -* Manage - Alerting: We have fixed a case where a tenant-queue-trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime.
11 +
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