Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/05/22 13:37
From version 132.1
edited by Carlijn Kokkeler
on 2023/10/23 16:26
Change comment: There is no comment for this version
To version 123.1
edited by Carlijn Kokkeler
on 2023/10/12 12:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +206 - Situational Deployment
Content
... ... @@ -1,14 +1,15 @@
1 -In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
1 +In the last sprint cycle, we focused on improving our deployment plan. On top of that, we made several improvements to the store.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.206 - Situational Deployment.WebHome||target="blank"]].
4 4  
5 5  
6 6  =====Minor changes=====
7 7  
8 8  * Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
9 -* Create - Framework: The framework used in the flow designer has been updated, improving performance.
10 -* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
11 -* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
9 +* Create - SSL: Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
10 +* Create - Framework: The framework used in the flow designer has been updated to the latest version.
11 +* Deploy - Architecture: The description users see when alerting the topic retention size has been changed to be less confusing.
12 +* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. (#1009)
12 12  * Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
13 13  * Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
14 14  * Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
... ... @@ -16,7 +16,7 @@
16 16  * Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
17 17  * Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
18 18  * Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
19 -* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
20 +* Manage - Alerting: Inactivated users should be removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
20 20  * Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
21 21  * Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
22 22  * Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)