Changes for page 210 - Deployment Delights

Summary

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

Details

Page properties

Content

...	...	@@ -3,12 +3,12 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** We have...
	6	+**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7	7
8	8	== **Alerts** ==
9	9
10	10	//__Topic approaching max size alert__//
11		-The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
	11	+The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
12	12
13	13	//__Missing metrics alert__//
14	14	We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
...	...	@@ -26,7 +26,6 @@
26	26	//__Rebuilding of images__//
27	27	Changing the list of flows that should run on a container will now trigger the rebuilding of images.
28	28
29		-
30	30	== **Bug Fixes** ==
31	31
32	32	//__Runtime metrics processing__//
...	...	@@ -33,11 +33,8 @@
33	33	The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
34	34
35	35	//__Deployment plan__//
36		-We solved a bug where a deployment step in the deployment plan could randomly get stuck.
	35	+We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
37	37
38		-//__Store message merging__//
39		-The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
40		-
41	41	//__View all store items__//
42	42	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.
43	43
...	...	@@ -45,15 +45,19 @@
45	45	We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
46	46
47	47	//__Max fetch size__//
48		-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.
49		-
	44	+In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
50	50
51	51	== **Fancy Forum Answers** ==
52	52
53	53	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:
54	54
55		-* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	50	+* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
	51	+* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
	52	+* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
	53	+* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
	54	+* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
56	56
	56	+
57	57	== **Key takeaways** ==
58	58
59	59	Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: