Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-219 - Creation Carousel
	1	+199 - Home Improvements

Author

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

Content

...	...	@@ -1,72 +1,58 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
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.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
7	7
8		-== **Feedback Items** ==
	7	+== **Next generation improvements and bug fixes** ==
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.
	9	+//__Enhanced overview of the HTTP Statistics__//
	10	+As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
12	12
13		-//__Improved OpenAPI import__//
14		-The path length that eMagiz supports when importing OpenAPI specifications is now increased to a maximum of 300 characters.
	12	+//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
	13	+In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
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.
	15	+{{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}}
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
	17	+//__Forced congestion control__//
	18	+To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
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.
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.
	21	+//__Improved validation errors on the invalid configuration of HTTP outbound components__//
	22	+This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
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}}
	24	+//__Improved migration behavior__//
	25	+This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
	26	+A smoother migration of your JMS (and backup JMS) process.
	27	+Shortening of names that otherwise would be too long, additional feedback given to the user.
	28	+Feedback when the migration process is finished.
26	26
27		-== **Bug Fixes** ==
28		-//__Error handling__//
29		-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.
	30	+//__Additional checks when deploying__//
	31	+This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
30	30
31		-//__Volume mapping passwords__//
32		-Passwords for network volumes are now securely hidden in the runtime’s machine after deploying a new release.
	33	+== **Store Improvements** ==
33	33
34		-//__Create integration removal__//
35		-When removing an integration from Create, the Create phase is now correctly updated.
	35	+== **Event Streaming - Certificate Management** ==
36	36
37		-//__Legacy statistics__//
38		-Legacy pages are now correctly hidden when running on the current runtime architecture.
39		-
40		-//__Unused properties__//
41		-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.
42		-
43		-//__Enumeration values__//
44		-Enumeration values for event processors can now be edited in Create.
45		-
46		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
47		-
48		-//__SFTP sessions__//
49		-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.
50		-
51	51	== **Fancy Forum Answers** ==
52	52
53	53	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:
54	54
55		-* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
56		-* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
57		-* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
	41	+* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
	42	+* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
58	58
59		-== **Key Takeaways** ==
	44	+== **Key takeaways** ==
60	60
61		-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:
	46	+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	62
63	63	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64	64	* If you have feedback or ideas for us, talk to the Platypus
65		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	50	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66	66	* Clear your browser cache (Ctrl + Shift + Del)
67		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
	52	+* Check out the release notes [here]
68	68	* Start thinking about how the license tracker can aid your development
69	69	* Start thinking about major, minor, and patch
	55	+* Upgrade to the latest build number
70	70	* Keep making great integrations
71	71
72	72	Let's stay in touch and till next time!
...	...	@@ -74,11 +74,6 @@
74	74	{{info}}
75	75	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
76	76
77		-{{/info}}
78		-)))
79		-
80		-(((
81		-{{toc/}}
82		-)))
	63	+~*~* Indicates a GEN3-only feature.
	64	+{{/info}})))((({{toc/}}))){{/container}}
83	83	{{/container}}
84		-{{/container}}