Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-226 - Alerting Alchemy
	1	+222 - Flee Frustration

Content

...	...	@@ -3,56 +3,45 @@
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!** This release, we have worked to allow cron trigggers for hours, days and months prepended by a 0. Moreover, changes in Design that will create or delete runtimes, or impact your model architecture, will trigger a warning before being put into effect in Design Architecture. We have also done several bug fixes, for example, users are not logged out from the portal anymore while deploying. Furthermore, users are now blocked from deploying at the same time on the same environment. Dive into our release blog to find out about the details and the rest of our bug fixes!
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	+//__Cron triggers__//
	10	+Cron triggers now allow for hours, days and months prepended by a 0, for example 05, which was not allowed before.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
	12	+[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
20	20
	14	+//__Design changes__//
	15	+If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
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-222-affect-design-architecture.png]]
23	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.
	19	+== **Bug Fixes** ==
	20	+//__Trigger activation__//
	21	+Previously, when you were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived your triggers, but this was not done. From now on, the deployer is blocked from logging out during the deployment execution, so that the triggers are re-enabled after the deployment plan has been executed.
25	25
26		-{{warning}}Please note that the new queue alerting will not yet be available for models with message redelivery. {{/warning}}
	23	+//__Multiple users deploying__//
	24	+Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
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	+[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
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.
	28	+//__Invalid memory configurations__//
	29	+We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
33	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.
	31	+//__Property value synchronization__//
	32	+Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
36	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.
	34	+//__JMS number__//
	35	+The number on the JMS container correctly displays the amount of queues present in Design.
41	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'.
	37	+[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
49	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:
53	53
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"]]
	43	+* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
	44	+* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
56	56
57	57	== **Key Takeaways** ==
58	58
...	...	@@ -62,7 +62,7 @@
62	62	* If you have feedback or ideas for us, talk to the Platypus
63	63	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64	64	* Clear your browser cache (Ctrl + Shift + Del)
65		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
	54	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.221 - Swift Shift.WebHome||target="blank"]]
66	66	* Start thinking about how the license tracker can aid your development
67	67	* Start thinking about major, minor, and patch
68	68	* Keep making great integrations