Changes for page 209 - Max Verstappen

Summary

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

Details

Page properties

Content

...	...	@@ -15,7 +15,7 @@
15	15
16	16	== **Next Generation Architecture Default** ==
17	17
18		-With this release, the next generation architecture will become the default. New models will use this generation as default.
	18	+With this release, the next generation architecture will become the default. From now on, new models will then use this generation as the default architecture.
19	19
20	20	[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
21	21
...	...	@@ -36,15 +36,11 @@
36	36	* Not required by a flow that is in the Create phase release.
37	37	* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
38	38
	39	+[[image:Main.Images.Release Blog.WebHome@release-blog-209-unused-properties-overview.png]]
	40	+
39	39	//__Queue explorer milliseconds__//
40	40	The queue browser now displays milliseconds in the timestamps.
41	41
42		-//__Unused images__//
43		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
44		-
45		-//__Carwash logging__//
46		-A new logging feature enabling us to make better choices in encryption standards will be released.
47		-
48	48	//__Static alerts queue consumers__//
49	49	Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
50	50
...	...	@@ -51,14 +51,11 @@
51	51	== **Bug Fixes** ==
52	52
53	53	//__Flow Designer connection line__//
54		-In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
	50	+In the Flow Designer an issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
55	55
56	56	//__Portal for migrated models__//
57		-We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
	53	+We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
58	58
59		-//__Error channel inbounds__//
60		-We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
61		-
62	62	== **Fancy Forum Answers** ==
63	63
64	64	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:
...	...	@@ -65,7 +65,7 @@
65	65
66	66	* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
67	67
68		-== **Key takeaways** ==
	61	+== **Key Takeaways** ==
69	69
70	70	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:
71	71
...	...	@@ -73,7 +73,7 @@
73	73	* If you have feedback or ideas for us, talk to the Platypus
74	74	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
75	75	* Clear your browser cache (Ctrl + Shift + Del)
76		-* Check out the release notes [here]
	69	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.209 - Max Verstappen.WebHome||target="blank"]]
77	77	* Start thinking about how the license tracker can aid your development
78	78	* Start thinking about major, minor, and patch
79	79	* Upgrade to the latest build number