Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00

From version 664.1
edited by Carlijn Kokkeler
on 2024/08/13 13:29
Change comment: There is no comment for this version
To version 660.1
edited by Carlijn Kokkeler
on 2024/08/12 12:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,21 +3,19 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release we have many fixes! Mainly for flow testing, the deploy phase, and alerting for hybrid models several small bugs have been resolved. Apart from these fixes, search functionality has been added to the start/stop flows screen. Moreover, the tracing information for errorChannel messages in flow test traces has been improved and we have enabled our new queue trigger functionality for redelivery-enabled messaging queues. Find out all about it below!
6 +**Hi there, eMagiz developers!** This release we have many fixes! Mainly for flow testing, the deploy phase, and alerting for hybrid models several small bugs have been resolved. Apart from these fixes, search functionality has been added to the start/stop flows screen. Moreover, the tracing information for errorChannel messages in flow test traces has been improved. Find out all about it below!
7 7  
8 8  == **Feedback Items** ==
9 -//__Tracing information__//
10 -The tracing errors in flow testing has been improved.
11 -
12 -[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
13 -
14 14  //__Start/stop flows search__//
15 15  The user is now able to search in the Start/Stop flows overview.
16 16  
17 17  [[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-search.png]]
18 18  
19 -//__Message redelivery queue triggers__//
20 -The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.
14 +//__Tracing information__//
15 +The tracing information for errorChannel messages in flow test traces has been improved.
16 +
17 +[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
18 +
21 21  
22 22  == **Bug Fixes** ==
23 23  //__Update namespace resources__//
... ... @@ -24,7 +24,7 @@
24 24  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.
25 25  
26 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 use the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
25 +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 28  
29 29  //__Internal/External recipients__//
30 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.
... ... @@ -65,7 +65,7 @@
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 66  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.227 - Fix Frenzy.WebHome||target="blank"]]
66 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
69 69  * Start thinking about how the license tracker can aid your development
70 70  * Start thinking about major, minor, and patch
71 71  * Keep making great integrations