Changes for page 240 - Spring Cleaning

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-234 - Alert Adventures
	1	+235 - TBD

Content

...	...	@@ -3,13 +3,16 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** In this release, our new error alerting will be available! Please find out more about it here (LINK). Apart from this, .
	6	+**Hi there, eMagiz developers!**
7	7
	8	+{{info}}Please note that this is our last release of the year. Our next release will be on the 19th of January!{{/info}}
	9	+
8	8	== **Feedback Items** ==
9	9	//__Error alerting__//
10		-Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, following our queue alerting design that has been [[released>>doc:Main.Release Information.Release Blogs.226 - Alerting Alchemy.WebHome||target="blank"]] a couple of months ago. The new error alerting feature allows you to trigger an alert on all incoming errors, or choose to trigger when specific filters on the error’s headers, message or class have been met. Furthermore, you can select the specific runtime the error originated from as one of the filters as well.
	12	+Error alerting has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, following our queue alerting design that has been [[released>>doc:Main.Release Information.Release Blogs.226 - Alerting Alchemy.WebHome||target="blank"]] several months ago. The new error alerting feature allows you to trigger an alert on **all** incoming errors, or choose to trigger when **specific filters** on the error’s headers, message or class have been met. Furthermore, you can select the specific runtime the error originated from as one of the filters as well.
11	11
12		-{{info}}Please take into consideration the following migration actions:
	14	+{{info}}
	15	+Please take into consideration the following migration actions:
13	13	* All existing error message alert triggers from the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture models will be automatically migrated to the new alerting feature.
14	14	* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
15	15	** The 'Description' field has been replaced by the new 'Instructions' field (note: the 'Description' field no longer exists).
...	...	@@ -25,7 +25,7 @@
25	25
26	26	{{warning}}To keep a better overview, we recommend you to remove your old dynamic triggers after the new error triggers are activated, these have already been disabled by our migration process. The same applies for your queue-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page.{{/warning}}
27	27
28		-{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}
	31	+{{warning}}Please check out our [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-error-alerting.WebHome||target="blank"]] for an elaborate explanation of our new error alerting. {{/warning}}
29	29
30	30	//__Attribute selection__//
31	31	When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted.
...	...	@@ -32,24 +32,27 @@
32	32
33	33	[[image:Main.Images.Release Blog.WebHome@release-234-cdm.png]]
34	34
35		-//__Attribute selection__//
36		-We have removed some deprecated components from our runtime image:
	38	+//__Runtime image__//
	39	+We have removed some deprecated components from our runtime image.
37	37	* TCP support object 'Byte array text length header (de)serializer'
38	38	* Mikrotik service activator
39		-
40		- image
41		- image
42		-
	42	+
43	43	Please find out more [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]].
44	44
	45	+{{warning}}We recommend evaluating custom groovy scripts and SpEL expressions to ensure that they do not rely on functionality that may have been removed due to one of the library removals.
	46	+* Calls to com.emagiz.util.Assert can be replaced with org.springframework.util.Assert
	47	+* Calls to com.emagiz.util.StringUtils can be replaced with org.springframework.util.StringUtils
	48	+* Calls to com.emagiz.util.CollectionUtils can be replaced with org.springframework.util.CollectionUtils{{/warning}}
	49	+
45	45	== **Bug Fixes** ==
	51	+//__Failover container__//
	52	+The failover container will now be shown correctly.
46	46
47		-
48	48	== **Fancy Forum Answers** ==
49	49
50	50	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:
51	51
52		-* [[JSON-TO-JSON java.lang.NumberFormatException in string field>>https://my.emagiz.com/p/question/172825635703991104||target="blank"]]
	58	+* [[H2 database following a queue channel without message store>>https://my.emagiz.com/p/question/172825635704003822||target="blank"]]
53	53
54	54	== **Key Takeaways** ==
55	55
...	...	@@ -59,7 +59,7 @@
59	59	* If you have feedback or ideas for us, talk to the Platypus
60	60	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
61	61	* Clear your browser cache (Ctrl + Shift + Del)
62		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.233 - Policy Polish.WebHome||target="blank"]]
	68	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.234 - Alert Adventures.WebHome||target="blank"]]
63	63	* Start thinking about how the license tracker can aid your development
64	64	* Start thinking about major, minor, and patch
65	65	* Keep making great integrations