Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 652.1
edited by Carlijn Kokkeler
on 2024/08/12 11:13
Change comment: There is no comment for this version
To version 655.1
edited by Carlijn Kokkeler
on 2024/08/12 11:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,6 +16,8 @@
16 16  
17 17  [[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
18 18  
19 +
20 +
19 19  == **Bug Fixes** ==
20 20  //__Update namespace resources__//
21 21  The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes on your namespaces in your message definitions.
... ... @@ -26,6 +26,27 @@
26 26  //__Internal/External recipients__//
27 27  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. Cases where this was applied incorrectly have been automatically fixed.
28 28  
31 +//__Tenant queue trigger__//
32 +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.
33 +
34 +//__Area selector__//
35 +We fixed an issue where the area selector of the flow designer started when only hovering over the white canvas.
36 +
37 +//__Runtime overview__//
38 +The runtime overview will now always display the correct container version.
39 +
40 +//__List of flows__//
41 +We fixed a bug where runtimes that did not appear in the list of flows of the deployment plan were restarted anyway.
42 +
43 +//__Deploy prevention__//
44 +When moving to Deploy phase for the first time, a background action could fail, which would prevent deploying a release. This has been resolved.
45 +
46 +//__Cancel button__//
47 +The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
48 +
49 +//__Log test execution__//
50 +In case opening a log of test execution is not possible in flow testing, a warning message will now be shown.
51 +
29 29  == **Fancy Forum Answers** ==
30 30  
31 31  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: