Changes for page 232 - Bug Busters

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-229 - Xpath Alignment
	1	+212 - Failover Fiesta

Author

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

Content

...	...	@@ -1,10 +1,27 @@
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. Please find all our changes and bug fixes below.
	1	+In the last sprint cycle, we focused on ....
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.212 - Failover Fiesta||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.
	5	+=====New features=====
7	7
	7	+* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
	8	+* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
	9	+
	10	+=====Minor changes=====
	11	+
	12	+* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
	13	+* Deploy - Deployment: The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
	14	+* Deploy - Architecture: The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
	15	+* Manage - Alerting: You can now add external recipients to your environment directly, like internal users. (#917)
	16	+* Manage - Monitoring: It is now possible to select the MQTT broker in the queue metrics dashboards.
	17	+* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
	18	+
8	8	====Bug fixes====
9		-* Create - Flow Designer: Improved the help text of the edit/new header menu in the XPath header enricher component (#727)
10		-* Create - Transformation: Fixed bug that causes the value input field to disappear if you switch from custom xpath to if it exists. (#1010)
	20	+
	21	+* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
	22	+* Deploy - Cloud template: An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
	23	+* Deploy - Deployment: Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
	24	+* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by a container.
	25	+* Manage - Monitoring: The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. (#1108)
	26	+
	27	+