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	+201 - Be Informed

Author

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

Content

...	...	@@ -1,72 +1,73 @@
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 planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you.
7	7
8		-== **Feedback Items** ==
	7	+== **Announcement - Release Properties** ==
	8	+As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
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	+== ** Deploy Architecture - Apply To Environment improvements ** ==
	11	+As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button.
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.
	13	+[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
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	+== ** Breadcrumb navigation in eMagiz ** ==
	16	+With this release we introduce the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed, and have impact, in the Create phase when you are checking out your transformation or system message on flow level. Apart from there the navigation is implemented consistently across the portal for a unified look and feel.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
	18	+[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
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.
	20	+== **Feedback Items** ==
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.
	22	+//__Improved layout of catalog page in Design__//
	23	+We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview when having several operations.
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}}
	25	+//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
	26	+As of now the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
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.
	28	+//__Additional help texts on Design Architecture__//
	29	+We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview.
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.
	31	+//__Improved Audit Trail on several places__//
	32	+In several places in the portal we have improved the audit trail to better specify who changed what at which point in time.
33	33
34		-//__Create integration removal__//
35		-When removing an integration from Create, the Create phase is now correctly updated.
	34	+//__Removed the erroneous alert on message mapping when having a passthrough API__//
	35	+This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
36	36
37		-//__Legacy statistics__//
38		-Legacy pages are now correctly hidden when running on the current runtime architecture.
	37	+== **Bug Fixes** ==
39	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.
	39	+//__Avoid clicking on other components while deleting another__//
	40	+To avoid unexpected behavior we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
42	42
43		-//__Enumeration values__//
44		-Enumeration values for event processors can now be edited in Create.
	42	+//__Improved validation feedback in migrating to the next-generation architecture__//
	43	+We have improved several things with regards to the validation feedback when migrating to the next-generation architecture.
45	45
46		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
	45	+//__Make sure that user credentials can be viewed with view rights__//
	46	+This release makes sure that the user credentials in Deploy can be viewed with view rights and not only when having edit rights.
47	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.
	48	+//__Refresh behavior within the deployment plan is fixed__//
	49	+This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
50	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"]]
	55	+* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
	56	+* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
	57	+* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
58	58
59		-== **Key Takeaways** ==
	59	+== **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:
	61	+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.
	65	+* 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"]]
	67	+* 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
	70	+* 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		-)))
	78	+~*~* Indicates a GEN3-only feature.
	79	+{{/info}})))((({{toc/}}))){{/container}}
83	83	{{/container}}
84		-{{/container}}