Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-213 - Joyful Journeys
	1	+219 - Creation Carousel

Content

...	...	@@ -3,78 +3,59 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done.
	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.
7	7
8		-== **Pop-up Improvements** ==
	8	+== **Feedback Items** ==
9	9
10		-//__Property releases__//
11		-When a new property release is created, this property release can now not only be viewed but also release properties can be deleted.
	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		-[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
	13	+//__Improved OpenAPI import__//
	14	+The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
14	14
15		-//__Runtime deletion__//
16		-When deleting a runtime, the error message is more descriptive. The error message will now include the names of the flows that run on the container.
	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.
17	17
18		-//__Wiretap & debug error messages__//
19		-The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
	19	+[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
20	20
21		-//__Action messages__//
22		-The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
	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.
23	23
24		-== **Formatting & Alignments** ==
	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.
25	25
26		-//__Input fields__//
27		-Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
	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}}
28	28
29		-//__UI improvements__//
30		-UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
31	31
32		-//__Component changes reversion__//
33		-In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
	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.
34	34
35		-//__State generation statistics__//
36		-The state generation graphs will now show the correct number of cache hits and misses.
	32	+//__Volume mapping passwords__//
	33	+Passwords for network volumes are hidden on the machine after deployment.
37	37
38		-//__Queue browser timestamps__//
39		-All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
	35	+//__Create integration removal__//
	36	+When removing an integration from Create, the Create phase is now correctly updated.
40	40
41		-//__Addition and deletion of internal recipients__//
42		-Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
	38	+//__Legacy statistics__//
	39	+Legacy pages are now correctly hidden when running on the current runtime architecture.
43	43
44		-== **Feedback Items** ==
	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.
45	45
46		-//__Update flows__//
47		-In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. This is particularly useful when changing a resouce used across multiple flows such as topic message definitions in event processors.
	44	+//__Enumeration values__//
	45	+Enumeration values for event processors can now be edited in Create.
48	48
49		-//__Q&A forum search__//
50		-The option to search by pressing the Enter key has been added to the Q&A forum.
	47	+[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
51	51
52		-//__Memory settings__//
53		-It is now possible to change the memory settings of a newly added container before pressing "Apply to environment".
54		-//__Runtime validation__//
55		-Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
	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.
56	56
57		-//__Runtime overview image versions__//
58		-Insight into intended and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
59		-
60		-== **Bug Fixes** ==
61		-
62		-//__Removal of onramp__//
63		-We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
64		-
65		-//__Runtime statistics details__//
66		-We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
67		-
68		-//__Deployment prechecks__//
69		-During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture.
70		-
71	71	== **Fancy Forum Answers** ==
72	72
73	73	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:
74	74
75		-* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
76		-* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
77		-* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
	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"]]
78	78
79	79	== **Key Takeaways** ==
80	80
...	...	@@ -84,7 +84,7 @@
84	84	* If you have feedback or ideas for us, talk to the Platypus
85	85	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
86	86	* Clear your browser cache (Ctrl + Shift + Del)
87		-* Check out the release notes [here]
	68	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
88	88	* Start thinking about how the license tracker can aid your development
89	89	* Start thinking about major, minor, and patch
90	90	* Keep making great integrations