Skip to Content

Changes for page 217 - Template Tango

Last modified by Carlijn Kokkeler on 2024/05/22 13:34
From version 120.1
edited by Carlijn Kokkeler
on 2023/10/12 12:15
Change comment: There is no comment for this version
To version 126.1
edited by Carlijn Kokkeler
on 2023/10/12 13:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,13 +5,12 @@
5 5  
6 6  =====Minor changes=====
7 7  
8 -* Design - Framework: The framework used in the flow designer has been updated to the latest version.
9 9  * Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
10 10  * Create - SSL: Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
11 -* Deploy - Architecture: The title of the 'apply to environment' action for changing 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)
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 adapting 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)
13 13  * Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
14 -* Deploy - Logging: New logging feature enabling us to make better choices in deprecating old encryption standards.
15 15  * Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
16 16  * Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
17 17  * Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
... ... @@ -18,7 +18,7 @@
18 18  * Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
19 19  * Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
20 20  * Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
21 -* 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.
22 22  * 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)
23 23  * Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
24 24  * Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
... ... @@ -41,8 +41,6 @@
41 41  
42 42  
43 43  
44 -
45 -
46 46  =====Infra and image changes=====
47 47  
48 -* No infra and/or image changes is this release.
45 +* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.