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	+210 - Deployment Delights

Content

...	...	@@ -3,62 +3,62 @@
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!** 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		-== **Feedback Items** ==
	8	+== **Alerts** ==
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.
	10	+//__Topic approaching max size alert__//
	11	+The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
12	12
13		-//__Improved OpenAPI import__//
14		-The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
	13	+//__Missing metrics alert__//
	14	+We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
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.
	16	+== **Feedback Items** ==
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
	18	+//__Improved release build process__//
	19	+When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
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.
	21	+//__Container version overview__//
	22	+Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
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.
	24	+[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
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}}
	26	+//_Improved deployment process_//
	27	+The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
26	26
	29	+//__Rebuilding of images__//
	30	+Changing the list of flows that should run on a container will now trigger the rebuilding of images.
27	27
28	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.
31	31
32		-//__Volume mapping passwords__//
33		-Passwords for network volumes are hidden on the machine after deployment.
	34	+//__Runtime metrics processing__//
	35	+The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
34	34
35		-//__Create integration removal__//
36		-When removing an integration from Create, the Create phase is now correctly updated.
	37	+//__Deployment plan__//
	38	+We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
37	37
38		-//__Legacy statistics__//
39		-Legacy pages are now correctly hidden when running on the current runtime architecture.
	40	+//__View all store items__//
	41	+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.
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.
	43	+//__Out of memory behavior__//
	44	+We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
43	43
44		-//__Enumeration values__//
45		-Enumeration values for event processors can now be edited in Create.
	46	+//__Max fetch size__//
	47	+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.
46	46
47		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
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.
51		-
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	+* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
	54	+* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
	55	+* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
	56	+* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
	57	+* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
59	59
60		-== **Key Takeaways** ==
61	61
	60	+== **Key takeaways** ==
	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
64	64	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
...	...	@@ -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"]]
	68	+* 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
	71	+* 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
	79	+~*~* Indicates a next-generation-architecture only feature.
78	78	{{/info}}
79	79	)))
80	80