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	+220 - Patch Parade

Content

...	...	@@ -3,54 +3,36 @@
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, we have improved our functionality to enable users to seamlessly import OpenAPI specifications with URL paths of up to 300 characters in length. 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!**
7	7
8	8	== **Feedback Items** ==
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	+//__Integration pattern information__//
	11	+Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
12	12
13		-//__External machine agents__//
14		-We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents on the current generation architecture from the portal. With future releases of environment templates, your on-premise agents may also be updated.
	13	+[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
15	15
16		-//__Improved OpenAPI import__//
17		-The path length that eMagiz supports when importing OpenAPI specifications is now increased to a maximum of 300 characters.
	15	+//__Message queue history__//
	16	+All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
18	18
19		-//__Flow test stack trace__//
20		-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	+[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
21	21
22		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
	20	+//__Search boxes__//
	21	+Search boxes in the properties overview are now shown by default.
23	23
24		-{{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.
	23	+[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
25	25
26		-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.
	25	+//__Search boxes__//
	26	+It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
27	27
28		-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}}
	28	+[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
29	29
30	30	== **Bug Fixes** ==
31		-//__Error handling__//
32		-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	+//__Annotation styling__//
	32	+It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
33	33
34		-//__Volume mapping passwords__//
35		-Passwords for network volumes are now securely hidden in the runtime’s machine after deploying a new release.
	34	+[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
36	36
37		-//__Create integration removal__//
38		-When removing an integration from Create, the Create phase is now correctly updated.
39		-
40		-//__Legacy statistics__//
41		-Legacy pages are now correctly hidden when running on the current runtime architecture.
42		-
43		-//__Unused properties__//
44		-Users should not be able to edit or delete eMagiz properties, and so these eMagiz properties will now not be shown in the 'Unused property overview' anymore.
45		-
46		-//__Enumeration values__//
47		-Users are now able to add and edit enumeration values while editing event processor flows in the Create phase.
48		-
49		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
50		-
51		-//__SFTP sessions__//
52		-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.
53		-
54	54	== **Fancy Forum Answers** ==
55	55
56	56	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: