Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 289.1
edited by Carlijn Kokkeler
on 2024/08/12 11:58
Change comment: There is no comment for this version
To version 173.1
edited by Carlijn Kokkeler
on 2023/12/21 16:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -227 - Fix Frenzy
1 +211 - Log Luminary
Content
... ... @@ -1,16 +1,19 @@
1 -During our recent sprint cycle, we have ......
1 +In the last sprint cycle, we focused on improving several aspects related 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.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
4 4  
5 -====Minor changes====
6 -* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview.
5 +=====New features=====
7 7  
7 +
8 +
9 +=====Minor changes=====
10 +
11 +* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
12 +
13 +
14 +
8 8  ====Bug fixes====
9 -* Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking.
10 -* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
11 -* Create - Message Definitions: The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes to your namespaces in your message definitions.
12 -* Deploy - Releases: We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of flows that will be restarted.
13 -* Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version.
14 -* Manage - Alerting: We have implemented a fix that allows you to activate and test queue triggers per environment when you are migrating your model to the current runtime architecture. You will be able to test the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
15 -* Manage - Alerting: You can now add internal and external recipients to your default trigger configuration at the same time, and they will be applied to your triggers correctly.
16 -* Manage - Alerting: We have fixed a case where a tenant-queue-trigger could be activated on a hybrid environment, before the JMS of that environment had been deployed to the current runtime.
16 +
17 +
18 +
19 +