Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 650.1
edited by Carlijn Kokkeler
on 2024/08/12 10:47
Change comment: There is no comment for this version
To version 654.1
edited by Carlijn Kokkeler
on 2024/08/12 11:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,15 +6,45 @@
6 6  **Hi there, eMagiz developers!**
7 7  
8 8  == **Feedback Items** ==
9 -//__Queue alerting__//
10 -
11 -== **Bug Fixes** ==
12 -//__Internal server error__//
9 +//__Start/stop flows search__//
13 13  The user is now able to search in the Start/Stop flows overview.
14 14  
15 15  [[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-search.png]]
16 16  
14 +//__Tracing information__//
15 +The tracing information for errorChannel messages in flow test traces has been improved.
17 17  
17 +[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
18 +
19 +//__Cancel button__//
20 +A cancel button has been added to the new/edit pages of flow testing test messages, such that the user is able to cancel changes to test messages if desired.
21 +
22 +== **Bug Fixes** ==
23 +//__Update namespace resources__//
24 +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.
25 +
26 +//__Queue triggers hybrid models__//
27 +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.
28 +
29 +//__Internal/External recipients__//
30 +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.
31 +
32 +//__Tenant queue trigger__//
33 +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.
34 +
35 +//__Area selector__//
36 +We fixed an issue where the area selector of the flow designer started when only hovering over the white canvas.
37 +
38 +//__Runtime overview__//
39 +The runtime overview will now always display the correct container version.
40 +
41 +//__List of flows__//
42 +We fixed a bug where runtimes that did not appear in the list of flows of the deployment plan were restarted anyway.
43 +
44 +//__Deploy prevention__//
45 +When moving to Deploy phase for the first time, a background action could fail, which would prevent deploying a release. This has been resolved.
46 +
47 +
18 18  == **Fancy Forum Answers** ==
19 19  
20 20  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: