Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37

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 104.1
edited by Erik Bakker
on 2023/09/13 07:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -203 - Fast Paced
1 +205 - World Explorers
Content
... ... @@ -1,19 +1,27 @@
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 what we show in Manage concerning the next-generation architecture. Furthermore, we will release a new cloud template. 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.203 - Fast Paced.WebHome||target= "blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.205 - World Explorers.WebHome||target="blank"]].
4 4  
5 +=====New features=====
6 +* Deploy - Cloud Template: We have introduced new functionality for our next-generation architecture in the mount configuration of our file storage solution used on the model level. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information.
7 +
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.
10 +* Create - 3rd Generation runtime migration: Your containers will be validated to function with the 3rd generation structure before you approve the migration.
11 +* Deploy - Architecture: The container calculations are improved. For event streaming containers, these show the number of topic proccessors deployed. Gateway containers represent the amount of operations deployed on a container. For JMS containers, these represent the number of message queues deployed. The other types of containers display the amount of integrations deployed. (#544) (#869)
12 +* Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1046)
13 +* Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80%.
14 +* Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (3rd generation only)
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.
18 +* Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054)
19 +* Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.
20 +* Manage - Queue statistics: Models with a vast number of queues will now show all queues. This used to be cut off. (Gen3 only)
21 +* General: In some places, the context menu showed too much horizontal whitespace; this has been fixed.
22 +* Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.
15 15  
24 +
16 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
27 +* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.