Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 26-Alerting Alchemy1 +231 - Microscopic Madness - Content
-
... ... @@ -3,54 +3,33 @@ 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!** 7 7 8 8 == **Feedback Items** == 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. 9 +//__Unused properties__// 10 +Search options for flow test logs have been improved: 11 +* You can now search for 'logger' and 'message'. Search options for 'timestamp from' and 'to' have been removed. 12 +* The UI has been unified with the logging in the Manage phase for a more streamlined experience. 13 +* 14 + 15 + 16 +[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]] 18 18 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 -{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}} 19 +== **Bug Fixes** == 20 +//__Unused properties__// 21 +We fixed an issue where used properties defined in Deploy Architecture were shown incorrectly in the missing properties overview and the unused properties overview. 22 22 23 -[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]] 23 +//__Router deletion__// 24 +Router containers that were deleted from the Deploy Architecture, are now cleaned up completely from the environment. 24 24 25 -//__Tenant technical name__// 26 - The technical name of a tenant cannot be changed once the tenant has been transferred to Create. 27 - 28 -//__Tenant transfer__// 29 -A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. 30 - 31 -//__Property placeholder__// 32 -A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal. 33 - 34 -//__Machine pop-up__// 35 -* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. 36 -* The machine health indicator has been improved visually. 37 -* Several progress bars have been improved visually. 38 - 39 -[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]] 40 - 41 -//__Infinispan Cache Manager__// 42 -The Infinispan Cache Manager has been updated to: 43 -* Provide an additional 'transport type' to offer more means for creating a clustered setup; 44 -* Provide clearer helptexts explaining which of the options is needed and what its effect is; 45 -* Include validation on fields depending on the selected 'transport type'. 46 - 47 47 == **Fancy Forum Answers** == 48 48 49 49 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: 50 50 51 -* [[ Transactionfailedandhas beenrolledback>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]52 -* [[ HowtocalculateHMAC-SHA1signature forwebhookverification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]53 -* [[ How canyouconvertanjsonarrayto xmlwiththenewapproach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]30 +* [[Error being stamped on the wrong "last flow">>https://my.emagiz.com/p/question/172825635703952578||target="blank"]] 31 +* [[AMQP broker hostname for JMS-host instead of IP>>https://my.emagiz.com/p/question/172825635703965465||target="blank"]] 32 +* [[Calling a soap webservice that is secured with a client certificate>>https://my.emagiz.com/p/question/172825635703965402||target="blank"]] 54 54 55 55 == **Key Takeaways** == 56 56 ... ... @@ -60,7 +60,7 @@ 60 60 * If you have feedback or ideas for us, talk to the Platypus 61 61 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 62 62 * Clear your browser cache (Ctrl + Shift + Del) 63 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.2 25- Pop-upParty.WebHome||target="blank"]]42 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.WebHome||target="blank"]] 64 64 * Start thinking about how the license tracker can aid your development 65 65 * Start thinking about major, minor, and patch 66 66 * Keep making great integrations