Skip to Content

Changes for page 225 - Pop-up Party

Last modified by Bouke Reitsma on 2024/07/18 09:55
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 201.1
edited by Carlijn Kokkeler
on 2024/02/26 10:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -203 - Fast Paced
1 +215 - Tiny Tales
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,19 +1,15 @@
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 +In the last sprint cycle, we focused on improving the event streaming graph. Moreover, we have done some bug fixes. First of all, the validation for queue names with respect to spaces has been improved. Moreover, it is now possible to remove an onramp that was previously linked to an all entry. Lastly, it is now possible to login to eMagiz by pressing enter when having the username field selected.
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.215 - Tiny Tales||target="blank"]].
4 4  
5 5  =====Minor changes=====
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.
7 +* Manage - Monitoring: The event streaming graph has been improved to better reflect the state of your topics. (#951)
9 9  
10 10  ====Bug fixes====
11 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.
11 +* Login: In the login screen, users now have the ability to press enter to log in when having the username field selected.
12 +* Create - Flow Designer: The validation regarding undesired spaces for components that use a queue name has been improved. (#1012)
13 +* Create - Flow Designer: An issue has been fixed where it was not possible to remove an onramp that was previously linked to a combined entry. (#1021)
15 15  
16 -=====Infra and image changes=====
17 17  
18 -* Infrastructure: Tightened security policies for a more secure infrastructure.
19 -* Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower