Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
From version 639.1
edited by Carlijn Kokkeler
on 2024/07/29 13:20
on 2024/07/29 13:20
Change comment:
There is no comment for this version
To version 635.1
edited by Carlijn Kokkeler
on 2024/07/29 13:15
on 2024/07/29 13:15
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -3,7 +3,7 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** The past few weeks we have worked hard to release ournewqueue alerting design. Please find out all new features in our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.CrashCourse.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning. Note that the new queue alerting will not yet be availalbe for queueswith messageredelivery. Next toalerting, we have worked on tenant items, machinepop-ups and progress bars,and the Infinispan Cache Manager. Find out all below!6 +**Hi there, eMagiz developers!** In this release, 7 7 8 8 == **Feedback Items** == 9 9 //__Queue alerting__// ... ... @@ -19,9 +19,8 @@ 19 19 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. 20 20 21 21 {{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}} 22 +{{info}}Please check out our [[Standard Alerting eMagiz microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] for an elaborate explanation of our new alerting design. {{/info}} 22 22 23 -{{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}} 24 - 25 25 [[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]] 26 26 27 27 //__Tenant technical name__// ... ... @@ -50,8 +50,9 @@ 50 50 51 51 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: 52 52 53 -* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]] 54 -* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]] 52 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 53 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 54 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 55 55 56 56 == **Key Takeaways** == 57 57