Wiki source code of 227 - Fix Frenzy
Version 295.1 by CarlijnKokkeler on 2024/08/12 12:27
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
294.1 | 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.1 | 2 | |
| |
286.1 | 3 | Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.227 - Fix Frenzy||target="blank"]]. |
| |
35.1 | 4 | |
| |
272.1 | 5 | ====Minor changes==== |
| |
294.1 | 6 | * Create - Flow Testing: The tracing information for errorChannel messages has been improved. |
| |
295.1 | 7 | * Deploy - Architecture: The user is now able to search in the Start/Stop flows overview. (#1311) |
| |
288.1 | 8 | |
| 9 | ====Bug fixes==== | ||
| |
295.1 | 10 | * Create - Flow Designer: We fixed an issue where certain areas were selected in the flow designer when only hovering over them, without clicking. (#1294) |
| |
294.1 | 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. | ||
| |
289.1 | 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. |
| |
295.1 | 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. (#1379) |
| |
293.1 | 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. |
| |
295.1 | 16 | * Deploy - Runtime Overview: We fixed a bug such that the runtime overview now shows the correct container version. (#1310) |
| |
289.1 | 17 | * 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. |
| 18 | * 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. | ||
| 19 | * 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. |