Skip to Content

Changes for page 247.1 - Help Out

Last modified by Erik Bakker on 2025/06/25 19:51
From version 266.1
edited by Erik Bakker
on 2025/06/17 09:16
Change comment: There is no comment for this version
To version 185.1
edited by Carlijn Kokkeler
on 2024/01/15 14:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -247 - Help Out
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,12 +1,27 @@
1 -This release focuses on helping our community by improving various aspects of our platform in anticipation of some of the larger features that are just around the corner. So, without further ado, let's take a look at what's on the menu today!
1 +In the last sprint cycle, we focused on ....
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.247 - Help Out.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Failover Fiesta||target="blank"]].
4 4  
5 -==== Bug fixes ====
5 +=====New features=====
6 6  
7 -* Design - Architecture: A change is made to ensure that the "Design architecture" is correctly updated based on message type changes in the Capture phase. (#1614)
8 -* Design - System: New help text is generated for the “SOAP entry connector” check box. The check box is present in the "Design phase" while editing the system. (#1413)
9 -* Create - Flow designer: On the "File item reader message source," various help texts have been added to give additional clarity on what the component does. (#1463)
10 -* Create - Flow Designer: Resetting a flow and deploying the changes from the reset flow are corrected so that the flow is deployed with the correct flow version and component list. (#1618)
11 -* Deploy - Architecture: Deploy architecture for displaying the retention bytes is aligned with the Design architecture. It shows the topic retention bytes, as users are only allowed to modify this variable. (#1358)
12 -* Manage - Explore: The bug is fixed so that all the options within the explore section of the Manage phase are responsive at all times. (#1524)
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.
9 +
10 +=====Minor changes=====
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.
18 +
19 +====Bug fixes====
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 +