Skip to Content

Changes for page 216 - Hack Heaven

Last modified by Carlijn Kokkeler on 2024/05/22 13:35
From version 155.1
edited by Carlijn Kokkeler
on 2023/11/21 12:24
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 -209 - Max Verstappen
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 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 Single Lane Docker and Double Lane Docker, to introduce faster machine boot up and improved auto-healing. Moreover, we processed several feedback items and did some bug fixes.
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.209 - Max Verstappen.WebHome||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 7  =====Minor changes=====
8 8  
9 -* Design - Message Mapping: The button 'Import from Store' will directly open the store.
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.
10 10  
11 -
12 12  ====Bug fixes====
13 13  
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.
14 14  
16 +=====Infra and image changes=====
15 15  
16 -
17 -
18 +* Infrastructure: Tightened security policies for a more secure infrastructure.
19 +* Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower