Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 102.1
edited by Erik Bakker
on 2023/08/15 12:23
Change comment: There is no comment for this version
To version 323.1
edited by Carlijn Kokkeler
on 2024/09/23 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -203 - Fast Paced
1 +230 - Petite Peaks
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,19 +1,10 @@
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.
1 +During our recent sprint cycle, we improved the functionality of adding an integration to an existing API in Design, ensured that queues with illegal characters will not generate errors anymore, and we fixed an issue where the execution of a deployment step would be blocked. Read all about it below!
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.203 - Fast Paced.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.230 - Petite Peaks||target="blank"]].
4 4  
5 -=====Minor changes=====
5 +====Minor changes====
6 +* Design - Solution Design: When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
6 6  
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 -
10 10  ====Bug fixes====
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
9 +* Manage - Explore: Queues with illegal characters will not generate errors anymore.
10 +* Deploy - Deployment: We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.