Skip to Content

Changes for page 230 - Petite Peaks

Last modified by Carlijn Kokkeler on 2024/09/27 09:36
From version 301.1
edited by Carlijn Kokkeler
on 2024/08/14 09:16
Change comment: There is no comment for this version
To version 297.1
edited by Carlijn Kokkeler
on 2024/08/12 13:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,17 +3,17 @@
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: Tracing errors in flow testing has been improved.
7 -* Deploy - Architecture: It is now possible to search in the Start/Stop flows overview. (#1311)
6 +* Create - Flow Testing: The tracing information for errorChannel messages has been improved.
7 +* Deploy - Architecture: The user is now able to search in the Start/Stop flows overview. (#1311)
8 8  * Manage - Alerting: The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.
9 9  
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 -* Deploy - Releases: We have resolved a bug that prevented you from deploying anything on a newly created model.
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.
17 17  * Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version. (#1310)
18 18  * 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.
19 19  * 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.