Changes for page 240 - Spring Cleaning

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-226 - Alerting Alchemy
	1	+227 - TBD

Content

...	...	@@ -3,50 +3,29 @@
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 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!
	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	+//__Start/stop flows search__//
	10	+The user is now able to search in the Start/Stop flows overview.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
	12	+[[image:Main.Images.Release Blog.WebHome@release-227-start-stop-flows-search.png]]
20	20
	14	+//__Tracing information__//
	15	+The tracing information for errorChannel messages in flow test traces has been improved.
21	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}}
	17	+[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
23	23
24		-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.
	19	+== **Bug Fixes** ==
	20	+//__Update namespace resources__//
	21	+The "last changed by" and "last changed date" values of additional namespace resources are now updated correctly when you make changes on your namespaces in your message definitions.
25	25
26		-{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
	23	+//__Queue triggers hybrid models__//
	24	+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.
27	27
28		-//__Tenant technical name__//
29		-The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
	26	+//__Internal/External recipients__//
	27	+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.
30	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		-
50	50	== **Fancy Forum Answers** ==
51	51
52	52	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: