Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-200 - Uncharted Territories
	1	+219 - Creation Carousel

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,66 +1,73 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}(((
	2	+{{container layoutStyle="columns"}}
	3	+(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on a lot of things that are unfortanetly not quite ready to be released. As a result the ouput of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
	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	6
7		-== **Next generation improvements and bug fixes** ==
	8	+== **Feedback Items** ==
8	8
9		-//__Enhanced right-hand view within Deployment Plan context__//
10		-When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
	10	+//__eMagiz Mendix connector__//
	11	+We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
11	11
12		-{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
	13	+//__Improved OpenAPI import__//
	14	+The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
13	13
14		-//__Improved timeout settings when deploying__//
15		-To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
	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	16
17		-{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	19	+[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
18	18
19		-//__Detailed HTTP Statistics now show user info in specific additional cases__//
20		-To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
	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	21
22		-{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	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.
23	23
24		-//__Improved loading speed of Manage Dashboard__//
25		-This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
	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	26
27		-== **Store Improvements** ==
28	28
29		-//__Importing in Design is improved__//
30		-We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
31		-
32	32	== **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.
33	33
34		-//__Deprecated reminder pop-up removed__//
35		-We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
	32	+//__Volume mapping passwords__//
	33	+Passwords for network volumes are hidden on the machine after deployment.
36	36
37		-//__Improved selection area in Flow Designer__//
38		-When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow.
	35	+//__Create integration removal__//
	36	+When removing an integration from Create, the Create phase is now correctly updated.
39	39
40		-//__Improved Kafka settings_//
41		-For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
	38	+//__Legacy statistics__//
	39	+Legacy pages are now correctly hidden when running on the current runtime architecture.
42	42
43		-{{info}}We stronly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
	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.
44	44
	44	+//__Enumeration values__//
	45	+Enumeration values for event processors can now be edited in Create.
	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	+
45	45	== **Fancy Forum Answers** ==
46	46
47	47	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:
48	48
49		-* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
50		-* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||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"]]
51	51
52		-== **Key takeaways** ==
	60	+== **Key Takeaways** ==
53	53
54		-Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	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:
55	55
56	56	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57	57	* If you have feedback or ideas for us, talk to the Platypus
58		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	66	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
59	59	* Clear your browser cache (Ctrl + Shift + Del)
60		-* Check out the release notes [here]
	68	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
61	61	* Start thinking about how the license tracker can aid your development
62	62	* Start thinking about major, minor, and patch
63		-* Upgrade to the latest build number
64	64	* Keep making great integrations
65	65
66	66	Let's stay in touch and till next time!
...	...	@@ -68,6 +68,11 @@
68	68	{{info}}
69	69	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
70	70
71		-~*~* Indicates a GEN3-only feature.
72		-{{/info}})))((({{toc/}}))){{/container}}
	78	+{{/info}}
	79	+)))
	80	+
	81	+(((
	82	+{{toc/}}
	83	+)))
73	73	{{/container}}
	85	+{{/container}}