Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-219 - Creation Carousel
	1	+209 - Deployment Delights

Content

...	...	@@ -3,61 +3,56 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** This release, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
	6	+**Hi there, eMagiz developers!** We have...
7	7
8		-== **Feedback Items** ==
	8	+== **Release Maintenance** ==
9	9
10		-//__eMagiz Mendix connector__//
11		-We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
12	12
13		-//__Improved OpenAPI import__//
14		-The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
15	15
16		-//__Flow test stack trace__//
17		-If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
20	20
21		-{{info}}With the release of Spring 6 in our previous release, some users reported that their filters have begun logging warnings about discarding messages even though the filter is configured to not throw an exception on rejection. For flows that process high numbers of messages (and potentially discard a lot of messages as well) this can significantly disturb the overview of the logs in the manage phase.
	14	+== **Feedback Items** ==
22	22
23		-To mitigate this, you can change the filter that throws the warning so it specifically refers to a discard channel. Given the chosen configuration, we advice to use the nullChannel option. This will silently drop the message without registering a warning in the log. In case you find the warning in the log a nice addition, we suggest to add an explicit discard channel leading to a logging outbound channel adapter. This log component can then be configured to throw a warning.
	16	+//__Container version overview__//
	17	+In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
24	24
25		-In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}}
	19	+[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
26	26
	21	+//__Unchanged containers__//
	22	+When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
27	27
28		-== **Bug Fixes** ==
29		-//__Error handling__//
30		-When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
	24	+//__Rebuilding of images__//
	25	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
31	31
32		-//__Volume mapping passwords__//
33		-Passwords for network volumes are hidden on the machine after deployment.
34	34
35		-//__Create integration removal__//
36		-When removing an integration from Create, the Create phase is now correctly updated.
	28	+== **Bug Fixes** ==
37	37
38		-//__Legacy statistics__//
39		-Legacy pages are now correctly hidden when running on the current runtime architecture.
	30	+//__Runtime metrics processing__//
	31	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
40	40
41		-//__Unused properties__//
42		-Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
	33	+//__Deployment plan__//
	34	+We solved a bug where a deployment step in the deployment plan could randomly get stuck.
43	43
44		-//__Enumeration values__//
45		-Enumeration values for event processors can now be edited in Create.
	36	+//__Store message merging__//
	37	+The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
46	46
47		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
	39	+//__View all store items__//
	40	+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.
48	48
49		-//__SFTP sessions__//
50		-SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
	42	+//__Out of memory behavior__//
	43	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
51	51
	45	+//__Max fetch size__//
	46	+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 the behavior.
	47	+
	48	+
52	52	== **Fancy Forum Answers** ==
53	53
54	54	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:
55	55
56		-* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
57		-* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
58		-* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
	53	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
59	59
60		-== **Key Takeaways** ==
	55	+== **Key takeaways** ==
61	61
62	62	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:
63	63
...	...	@@ -65,9 +65,10 @@
65	65	* If you have feedback or ideas for us, talk to the Platypus
66	66	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67	67	* Clear your browser cache (Ctrl + Shift + Del)
68		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
	63	+* Check out the release notes [here]
69	69	* Start thinking about how the license tracker can aid your development
70	70	* Start thinking about major, minor, and patch
	66	+* Upgrade to the latest build number
71	71	* Keep making great integrations
72	72
73	73	Let's stay in touch and till next time!
...	...	@@ -75,6 +75,7 @@
75	75	{{info}}
76	76	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77	77
	74	+~*~* Indicates a next-generation-architecture only feature.
78	78	{{/info}}
79	79	)))
80	80