Changes for page 240 - Spring Cleaning

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

From version 623.1
edited by Carlijn Kokkeler
on 2024/07/29 12:22
Change comment: There is no comment for this version
To version 646.1
edited by Carlijn Kokkeler
on 2024/07/30 13:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,11 +3,11 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release,
6 +**Hi there, eMagiz developers!** The past few weeks we have worked hard to release our new queue alerting design. Please find out all new features in our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning. Note that the new queue alerting will not yet be availalbe for queues with message redelivery. Next to alerting, we have worked on tenant items, machine pop-ups and progress bars, as well as the Infinispan Cache Manager. Find out all below!
7 7  
8 8  == **Feedback Items** ==
9 9  //__Queue alerting__//
10 -Alerting for message queues has been improved, which includes the following improvements:
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 11  * New UI that shows all queues and the alerting that is active on them.
12 12  * Every queue in the model will be automatically added to the list of queues in Manage - Alerting.
13 13  * Triggers of a queue will be automatically enabled or disabled based on whether that queue is included in the release.
... ... @@ -15,16 +15,44 @@
15 15  ** These checks can now run for a (very) long time, whereas the "queue throughput" was limited by 1 hour.
16 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 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.
18 -
19 -== **Bug Fixes** ==
20 20  
19 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
20 +
21 +
22 +{{info}}Please check out our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning for an elaborate explanation of our new queue alerting design. {{/info}}
23 +
24 +eMagiz will migrate your dynamic queue alerts on the **release day** when you are **fully** or **partially** migrated to the [[current runtime architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]. When doing so, we will configure the new queue alert in a similar fashion to best match its current behaviour. Note that the queue alerting will only function for models that are **fully** migrated to the [[current runtime architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]. Should you want to change or create new queue alerts, you can do so starting the day **after** the release to avoid conflicts with our migration.
25 +
26 +{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
27 +
28 +//__Tenant technical name__//
29 +The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
30 +
31 +//__Tenant transfer__//
32 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
33 +
34 +//__Property placeholder__//
35 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
36 +
37 +//__Machine pop-up__//
38 +* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
39 +* The machine health indicator has been improved visually.
40 +* Several progress bars have been improved visually.
41 +
42 +[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]]
43 +
44 +//__Infinispan Cache Manager__//
45 +The Infinispan Cache Manager has been updated to:
46 +* Provide an additional 'transport type' to offer more means for creating a clustered setup;
47 +* Provide clearer helptexts explaining which of the options is needed and what its effect is;
48 +* Include validation on fields depending on the selected 'transport type'.
49 +
21 21  == **Fancy Forum Answers** ==
22 22  
23 23  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:
24 24  
25 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
26 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
27 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
54 +* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]
55 +* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]
28 28  
29 29  == **Key Takeaways** ==
30 30  
... ... @@ -34,7 +34,7 @@
34 34  * If you have feedback or ideas for us, talk to the Platypus
35 35  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
36 36  * Clear your browser cache (Ctrl + Shift + Del)
37 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
65 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
38 38  * Start thinking about how the license tracker can aid your development
39 39  * Start thinking about major, minor, and patch
40 40  * Keep making great integrations