Skip to Content

Changes for page 277 - First Farewell

Last modified by Erik Bakker on 2026/09/23 16:09
From version 354.1
edited by Erik Bakker
on 2026/09/10 07:59
Change comment: There is no comment for this version
To version 184.1
edited by CarlijnKokkeler
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 -276 - API, API
1 +212 - Failover Fiesta
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,16 +1,27 @@
1 -This release includes various smaller improvements throughout the various phases of the platform. On top of that, it introduces a structured and simple way to navigate to our API MAM functionality for all models using the API Pattern in combination with the API Key security option.
1 +In the last sprint cycle, we focused on ....
2 2  
3 -Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.276 - API, API.WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.212 - Feedback Fiesta||target="blank"]].
4 4  
5 -==== Minor Changes ====
5 +=====New features=====
6 6  
7 -* General - Platform: Replaced several older widgets with newer equivalents. As a result, the look and feel of various parts of the platform have changed.
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.
8 8  
9 -===== Bug Fixes ====
10 +=====Minor changes=====
10 10  
11 -* Flow Designer - Save and Create New Version: We fixed a bug that prevented users from transferring their flows to Deploy when their initial action was to create an “Autosaved version” of the flow. (#1816)
12 -* Deploy - Release: We improved the release activation logic to prevent some uncertainty issues during the deployment of the release in the Deploy phase.
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.
13 13  
14 -==== Remarks ====
19 +====Bug fixes====
15 15  
16 -* Updated our //__emagiz.com__// certificate.
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 +