Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 667.1
edited by Carlijn Kokkeler
on 2024/08/14 09:03
Change comment: There is no comment for this version
To version 629.1
edited by Carlijn Kokkeler
on 2024/07/29 12:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -227 - Fix Frenzy
1 +226 - Alerting Alchemy
Content
... ... @@ -3,59 +3,42 @@
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!** In this release,
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 -//__Start/stop flows search__//
15 -The user is now able to search in the Start/Stop flows overview.
16 -
17 -[[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-searchterm.png]]
18 -
19 -//__Message redelivery queue triggers__//
20 -The new queue triggers feature has been updated to be able to handle redelivery-enabled messaging queues.
9 +//__Queue alerting__//
10 +Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, which includes the following improvements:
11 +* New UI that shows all queues and the alerting that is active on them.
12 +* Every queue in the model will be automatically added to the list of queues in Manage - Alerting.
13 +* Triggers of a queue will be automatically enabled or disabled based on whether that queue is included in the release.
14 +* Added 2 new trigger types "inactivity check" and "periodic activity check" that replace the "queue throughput" alert.
15 +** These checks can now run for a (very) long time, whereas the "queue throughput" was limited by 1 hour.
16 +* The alert generation has been solidified to reduce the likelihood that your alerting is affected with false positives or false negatives during eMagiz maintenance.
17 +* When the same check of multiple queues trigger at the same time, the alerts will be aggregated into a single summarized email instead of a single email per alert.
21 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 to your namespaces in your message definitions.
25 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 use the queue triggers of any environment that is fully migrated, even if another environment is still in the process of migrating.
20 +If your model is running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, you will be migrated on the day of release. eMagiz will transfer the queue alerts that you have currently configured to the closest match in the new alerting stack. Models that are in the process of migrating to the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture during the time of the release of this feature will be able to pre-configure their new queue alert triggers, but will not be able to make active use of them until the runtime migration has finished.
28 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.
22 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
31 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.
24 +//__Tenant technical name__//
25 + The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
34 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.
27 +//__Tenant transfer__//
28 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
37 37  
38 -//__Runtime overview__//
39 -The runtime overview will now always display the correct container version.
30 +//__Property placeholder__//
31 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
40 40  
41 -//__List of flows__//
42 -We fixed a bug where runtimes that did not change appeared in the deployment plan in the list of runtimes that will be restarted.
33 +== **Bug Fixes** ==
43 43  
44 -//__Deploy prevention__//
45 -We have resolved a bug that prevented you from deploying anything on a newly created model.
46 -
47 -//__Cancel button__//
48 -The cancel button on the new/edit pages of test messages in flow testing, now actually cancels changes.
49 -
50 -//__Log test execution__//
51 -If opening a test execution log is not possible during flow testing, a warning message will now be displayed.
52 -
53 53  == **Fancy Forum Answers** ==
54 54  
55 55  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:
56 56  
57 -* [[Messages are not being delivered correctly to the SFTP location>>https://my.emagiz.com/p/question/172825635703914167||target="blank"]]
58 -* [[Uploading XSD>>https://my.emagiz.com/p/question/172825635703914284||target="blank"]]
39 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
40 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
41 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
59 59  
60 60  == **Key Takeaways** ==
61 61  
... ... @@ -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"]]
51 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.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