Skip to Content

Changes for page 270 - Round Round

Last modified by Erik Bakker on 2026/06/15 10:37
From version 179.1
edited by CarlijnKokkeler
on 2024/01/02 10:29
Change comment: There is no comment for this version
To version 338.1
edited by Erik Bakker
on 2026/06/01 09:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +269 - Additional Acceleration
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,27 +1,12 @@
1 -In the last sprint cycle, we focused on improving several aspects related to overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.
1 +This release includes additional accelerants for all integration developers out there. This includes improvements in the flow designer navigation and the missing properties functionality. Subsequently, we introduced a fix to improve the stability of our flow designer. Enjoy reading our latest updates on the platform.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
3 +Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.269 - Additional Acceleration.WebHome||target="blank"]].
4 4  
5 -=====New features=====
5 +==== Minor Changes ====
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 +* Create - Flow Designer: When part of an integration is opened for the first time, the entire flow is generated as an initial version so that the user can navigate to the previous and next flow using the inbound and outbound components. (#1660)
8 +* Deploy - Release - Missing Properties: To improve overall performance, we update the missing properties list in such a way that we do not need to recalculate the full list every time a user makes a change in the list. Furthermore, various UI/UX improvements have been made throughout the process to optimize the user experience. (#1796)
9 9  
10 -=====Minor changes=====
10 +==== Bug fixes ====
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: Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
15 -* Manage - Alerting: You can now add external recipients to your environment directly, like internal users.
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 unjustly 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 the container.
25 -* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal.
26 -
27 -
12 +* Create - Flow Designer: A fix has been implemented to resolve an issue where an error popup would occasionally appear when opening the Flow Designer. (#1644)