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	+211 - Log Luminary

Author

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

Content

...	...	@@ -1,10 +1,24 @@
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 improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.
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.211 - Log Luminary||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 - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots of the release in the Deploy phase.
	8	+
	9	+=====Minor changes=====
	10	+
	11	+* Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
	12	+* Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images.
	13	+
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)
	15	+
	16	+* Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
	17	+* Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. (#1100)
	18	+* Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
	19	+* Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
	20	+* Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
	21	+* Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
	22	+* Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
	23	+
	24	+