Skip to Content

Changes for page 233 - Policy Polish

Last modified by Carlijn Kokkeler on 2024/11/06 14:06
From version 298.1
edited by Carlijn Kokkeler
on 2024/08/13 14:54
Change comment: There is no comment for this version
To version 296.1
edited by Carlijn Kokkeler
on 2024/08/12 13:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -During our recent sprint cycle, we have done many fixes. These are mainly related to flow testing, alerting, and the deploy phase. Apart from that, we have improved the tracing information for errorChannel messages, added search functionality to the Start/Stop flows overview, and enabled our new queue trigger functionality for redelivery-enabled messaging queues.
1 +During our recent sprint cycle, we have done many fixes. These are mainly related to flow testing, alerting, and the deploy phase. Apart from that, we have improved the tracing information for errorChannel messages, and added search functionality to the Start/Stop flows overview.
2 2  
3 3  Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
4 4  
... ... @@ -10,7 +10,7 @@
10 10  ====Bug fixes====
11 11  * Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking. (#1294)
12 12  * Create - Flow Testing: The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
13 -* Create - Flow Testing: If opening a test execution log is not possible during flow testing, a warning message will now be displayed.
13 +* Create - Flow Testing: In case opening a log of test execution is not possible, a warning message will now be shown.
14 14  * 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.
15 15  * 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. (#1379)
16 16  * Deploy - Releases: When moving to the Deploy phase for the first time, a background action could fail, preventing deploying a release. This has been resolved.