Changes for page 234 - Alert Adventures

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-229 - XPath Alignment
	1	+234 - Alert Adventures

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,12 +1,11 @@
1		-During our recent sprint cycle, we made several improvements to keep our model running smoothly. We also made some small changes to various XPath-related parts of the portal and updated our deployment plan. Please find all our changes and bug fixes below.
	1	+In this release, our new error alerting will be available! Please find out more about it here (LINK). Moreover, a new runtime image is available, check it out [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]]. Lastly, we have improved the selection visibility in data models, and have fixed a bug regarding failover containers.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.229 - Xpath Alignment||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.234 - Alert Adventures||target="blank"]].
4	4
5	5	====Minor changes====
6		-* Deploy - Deployment plan: We updated the deployment step that temporarily disables the triggers in your model. As a result, you can now define after which waiting period (determined in minutes) you want eMagiz to take action. When it reaches this point, eMagiz will act according to the selected option. You can opt to "automatically re-enable triggers," "receive a notification mail," or "both." On top of that, we reintroduced the automatic "enable trigger" step, which can be added as the last step of your deployment plan to automatically re-enable triggers. Be aware that you **still** need to enable triggers manually if you have manually disabled them before deploying. This can be done via the Manage phase. (#1367)
7		-* Create - Flow Designer: SFTP (caching) session factories now have an additional option to specify the authentication methods that should be used, and in which order. Note that the latest [[runtime image>>Main.Release Information.Runtime Images.V313||target="blank"]] is needed to make the functionality work in eMagiz.
8		-* Create - Flow designer: We fixed an issue related to the legacy property “web service-URL “ of an exit connector flow related to a Mendix (connector) system. In your Mendix application, you can download and start them from an activating release.
	6	+* Manage - Alerting: 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. Please check out our [[release blog>>Main.Release Information.Release Blogs.234 - Alert Adventures||target="blank"]] for the migration actions, and our new [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-error-alerting.WebHome||target="blank"]] about the design.
	7	+* Design - CDM: When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted. (#1150)
	8	+* Deploy - Deployment: We have removed some deprecated components from our runtime image. Please find out more [[here>>doc:Main.Release Information.Runtime Images.V320.WebHome||target="blank"]].
9	9
10	10	====Bug fixes====
11		-* Create - Flow Designer: Improved the help text of the edit/new header menu in the XPath header enricher component, to better inform how a list of results can be handled. (#727)
12		-* Create - Transformation: Fixed a bug that caused the value input field to disappear if you switch from “custom xpath“ to “if it exists“. (#1010)
	11	+* Deploy - Architecture: The failover container will now be shown correctly.