Changes for page 232 - Bug Busters

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-229 - XPath Alignment
	1	+199 - Home Improvements

Content

...	...	@@ -1,11 +1,19 @@
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 the last sprint cycle, we focused on improving various aspects of the portal functionality. Among others, we focused on the next-generation architecture, the store, security, and certificate management.
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.199 - Home Improvements.WebHome||target= "blank"]].
4	4
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.
	5	+=====Minor changes=====
8	8
	7	+* Design - Message mapping: It is now possbile to create a message mapping to an imported system message from the store.
	8	+* Deploy - Architecture: In the details view of a machine, you can now see the Static IP that was assigned to this machine by the eMagiz cloud. This way, you no longer have to contact your partner manager to retrieve this information. To use this functionality, please ensure you upgrade (automatically) to the latest cloud template. (#899)
	9	+* Deploy - User management: Added a new overview pop-up to manage your event streaming users with expiring access certificates. You will also receive a notification email approximately three months before event streaming users' access certificates expire.
	10	+* Deploy - Release: Unused runtime images will be automatically removed after successful machine deployments. This can be disabled by changing the machine step in your deployment plan.
	11	+* Manage - Monitoring: HTTP statistics page now displays all the resources. (#960)
	12	+* Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.
	13	+* General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.
	14	+
9	9	====Bug fixes====
10		-* 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)
11		-* Create - Transformation: Fixed a bug that caused the value input field to disappear if you switch from “custom xpath“ to “if it exists“. (#1010)
	16	+
	17	+* Create - Store: Spring Reserved words containing * are not incorrectly replaced with the flow prefix. (#864)
	18	+* Manage - Monitoring: Not all log messages were visible in the manage phase when an application failed to start. Note that this functionality requires a newly deployed release. (#937)
	19	+