Skip to Content

Changes for page 241.1 - Wild West

Last modified by Erik Bakker on 2025/04/04 08:35
From version 122.1
edited by Carlijn Kokkeler
on 2023/10/12 12:18
Change comment: There is no comment for this version
To version 124.1
edited by Carlijn Kokkeler
on 2023/10/12 12:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,7 +8,7 @@
8 8  * Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
9 9  * Create - SSL: Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
10 10  * Create - Framework: The framework used in the flow designer has been updated to the latest version.
11 -* Deploy - Architecture: The title of the 'apply to environment' action for changing topic retention size has been changed to be less confusing.
11 +* Deploy - Architecture: The description users see when alerting the topic retention size has been changed to be less confusing.
12 12  * Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. (#1009)
13 13  * Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
14 14  * Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
... ... @@ -17,7 +17,7 @@
17 17  * Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
18 18  * Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
19 19  * Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
20 -* Manage - Alerting: Inactivated users should be removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
20 +* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
21 21  * 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)
22 22  * Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
23 23  * Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)