Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 09:59
From version 185.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
Change comment: There is no comment for this version
To version 191.1
edited by Carlijn Kokkeler
on 2024/01/29 15:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +213 - Joyful Journeys
Content
... ... @@ -1,27 +1,31 @@
1 -In the last sprint cycle, we focused on ....
1 +In the last sprint cycle, we focused on improving pop-up messages to improve the user experience. Moreover, we did several alignment & formatting improvements. Lastly, some more feedback items have been solved, and several more bug fixes have been done.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.213 - Joyful Journeys||target="blank"]].
4 4  
5 5  =====New features=====
6 6  
7 -* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
8 -* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
7 +* Home - Q&A: The option to search by pressing the Enter key has been added.
9 9  
10 10  =====Minor changes=====
11 11  
12 -* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
13 -* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
14 -* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
15 -* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
16 -* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
17 -* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
11 +* All - Input fields: Multiple input fields have been updated to expand when the amount of characters exceeds the default size. (#822)
12 +* Design - Message: The tooltip for the optional/required toggle has been improved. (#1172)
13 +* Create - Transformation: UI improvements for static input components have been done. (#1172)
14 +* Create - Resources: A button "Update flows" has been added to update versions of all flows in which a resource is used. (#1129)
15 +* Deploy - Releases: When a new property release is created, this property release can now be viewed and deleted. (#1031)
16 +* Deploy - Containers: The error message that is displayed when deleting a runtime is now more descriptive. (#1053)
17 +* Deploy - Runtime overview: Insight into invented and actual deployments has been improved.
18 +* Deploy - Architecture: It is now possible to change the memory settings of a container before pressing "Apply to environment". (#968)
19 +* Deploy - Architecture: Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. (#977)
20 +* Deploy - Architecture: The formatting of action messages regarding changes in retention bytes/hours has been improved.
21 +* Manage - Explore: The error messages that may be displayed when using wiretaps and the debugger have been improved.
18 18  
19 19  ====Bug fixes====
20 20  
21 -* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
22 -* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
23 -* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
24 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
25 -* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
26 -
27 -
25 +* Create - Flow Designer: We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). (#1021)
26 +* Create - Flow Designer: A bug has been fixed where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. (#1030)
27 +* Deploy - Architecture: During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
28 +* Manage - Monitoring: The correct number of cache hits and misses are now shown in the state generation statistics. (#1161)
29 +* Manage - Monitoring: We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
30 +* Manage - Explorer: We aligned all timestamp formatting to yyyy-MM-dd HH:mm:ss.SSS.
31 +* Manage - Notification settings: Internal recipients are now added correctly.