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	+230 - Petite Peaks

Content

...	...	@@ -3,42 +3,31 @@
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!** In this release, we have some small improvements and bug fixes. First of all, the pop-up when adding an integration to an existing API in Design has been improved. Secondly, queues with illegal characters will not cause errors anymore. Thirdly, an issue has been fixed where a deployment step would get blocked. Please find out all below!
7	7
	8	+{{info}}Please note that during this deployment, Kafka metrics will be unavailable and lost for the duration of the deployment. After the deployment is complete, Kafka metrics will resume and be reflected in the monitoring graphs, but no metrics will be present corresponding to the deployment period.{{/info}}
	9	+
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.
18		-
	11	+//__Add integration__//
	12	+When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
19	19
20		-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.
	14	+[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
21	21
22		-{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
23	23
24		-//__Tenant technical name__//
25		- The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
26		-
27		-//__Tenant transfer__//
28		-A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
29		-
30		-//__Property placeholder__//
31		-A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
32		-
33	33	== **Bug Fixes** ==
	18	+//__Queues with illegal characters__//
	19	+Existing queues with illegal characters will not generate errors anymore. They can now be searched, deleted, explored, wiretapped, etc. in Manage -> Explore.
34	34
	21	+//__Blocked deployment step__//
	22	+We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
	23	+
35	35	== **Fancy Forum Answers** ==
36	36
37	37	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:
38	38
39		-* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
40		-* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
41		-* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
	28	+* [[Error being stamped on the wrong "last flow">>https://my.emagiz.com/p/question/172825635703952578||target="blank"]]
	29	+* [[AMQP broker hostname for JMS-host instead of IP>>https://my.emagiz.com/p/question/172825635703965465||target="blank"]]
	30	+* [[Calling a soap webservice that is secured with a client certificate>>https://my.emagiz.com/p/question/172825635703965402||target="blank"]]
42	42
43	43	== **Key Takeaways** ==
44	44
...	...	@@ -48,7 +48,7 @@
48	48	* If you have feedback or ideas for us, talk to the Platypus
49	49	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
50	50	* Clear your browser cache (Ctrl + Shift + Del)
51		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
	40	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.WebHome||target="blank"]]
52	52	* Start thinking about how the license tracker can aid your development
53	53	* Start thinking about major, minor, and patch
54	54	* Keep making great integrations