Skip to Content

Changes for page 230 - Petite Peaks

Last modified by Carlijn Kokkeler on 2024/09/27 09:36
From version 294.1
edited by Carlijn Kokkeler
on 2024/08/12 12:25
Change comment: There is no comment for this version
To version 293.1
edited by Carlijn Kokkeler
on 2024/08/12 12:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,15 +1,13 @@
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.
1 +During our recent sprint cycle, we have ......
2 2  
3 3  Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]].
4 4  
5 5  ====Minor changes====
6 -* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
7 7  * Deploy - Architecture: The user is now able to search in the Start/Stop flows overview.
8 8  
9 9  ====Bug fixes====
10 10  * Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking.
11 -* Create - Flow Testing: The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
12 -* Create - Flow Testing: In case opening a log of test execution is not possible, a warning message will now be shown.
10 +* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
13 13  * 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.
14 14  * 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.
15 15  * 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.