Wiki source code of 203 - Fast Paced
Last modified by Carlijn Kokkeler on 2024/05/22 13:39
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
102.1 | 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.1 | 2 | |
| |
102.1 | 3 | Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.203 - Fast Paced.WebHome||target= "blank"]]. |
| |
35.1 | 4 | |
| |
103.1 | 5 | ====Minor changes==== |
| |
37.1 | 6 | |
| |
102.1 | 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. | ||
| |
93.1 | 9 | |
| |
97.1 | 10 | ====Bug fixes==== |
| |
93.1 | 11 | |
| |
102.1 | 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. | ||
| |
37.1 | 15 | |
| |
103.1 | 16 | ====Infra and image changes==== |
| |
101.1 | 17 | |
| 18 | * Infrastructure: Tightened security policies for a more secure infrastructure. | ||
| |
102.1 | 19 | * Infrastructure: Added and improved auto-scaling behavior for the eMagiz Control Tower |