Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-189 - Private Eye
	1	+219 - Creation Carousel

Author

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

Content

...	...	@@ -1,87 +1,75 @@
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!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
	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	6
7		-== **Private Store** ==
8		-On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
	8	+== **Feedback Items** ==
9	9
10		-{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
	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		-== **3rd generation runtime bolstering** ==
	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	13
14		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
	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	15
16		-//__SOAP and REST web services migration, including splitting them__//
17		-With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
	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	18
19		-//__Changing SSL settings for 3rd generation runtime models works__//
20		-As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
	22	+[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
21	21
22		-//__Improved migration for JMS flows__//
23		-This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
	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.
24	24
25		-{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
	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.
26	26
27		-//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28		-As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
	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}}
29	29
30		-//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31		-We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
	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.
32	32
33		-//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
34		-With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
	34	+//__Volume mapping passwords__//
	35	+Passwords for network volumes are now securely hidden in the runtime’s machine after deploying a new release.
35	35
36		-//__Added "Reset" functionality__//
37		-With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
	37	+//__Create integration removal__//
	38	+When removing an integration from Create, the Create phase is now correctly updated.
38	38
39		-== **Feedback items ** ==
	40	+//__Legacy statistics__//
	41	+Legacy pages are now correctly hidden when running on the current runtime architecture.
40	40
41		-We have also solved other feedback items besides the flow designer's critical updates.
	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.
42	42
43		-//__Improved naming convention on Store related pages__//
44		-We have improved various display names using the merge functionality within our store offering.
	46	+//__Enumeration values__//
	47	+Users are now able to add and edit enumeration values while editing event processor flows in the Create phase.
45	45
46		-//__Update security protocols for our internal architecture__//
47		-Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
	49	+[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
48	48
49		-//__Improved read-only description for "if exists" constructions in Transformations__//
50		-To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
	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.
51	51
52		-
53		-== **Bug fixes ** ==
54		-
55		-//__Decent validation feedback when not filling in the property value__//
56		-We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
57		-
58		-//__Incorrect resource locations__//
59		-We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
60		-
61		-//__Apply to environment in User Management performance improvement__//
62		-We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
63		-
64	64	== **Fancy Forum Answers** ==
65	65
66	66	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:
67	67
68		-* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
69		-* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
70		-* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
71		-* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
	58	+* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
	59	+* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
	60	+* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
72	72
73		-== **Key takeaways** ==
	62	+== **Key Takeaways** ==
74	74
75		-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:
	64	+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:
76	76
77	77	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78	78	* If you have feedback or ideas for us, talk to the Platypus
79		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	68	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80	80	* Clear your browser cache (Ctrl + Shift + Del)
81		-* Check out the release notes [here]
	70	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
82	82	* Start thinking about how the license tracker can aid your development
83	83	* Start thinking about major, minor, and patch
84		-* Upgrade to the latest build number
85	85	* Keep making great integrations
86	86
87	87	Let's stay in touch and till next time!
...	...	@@ -89,6 +89,11 @@
89	89	{{info}}
90	90	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91	91
92		-~*~* Indicates a GEN3-only feature.
93		-{{/info}})))((({{toc/}}))){{/container}}
	80	+{{/info}}
	81	+)))
	82	+
	83	+(((
	84	+{{toc/}}
	85	+)))
94	94	{{/container}}
	87	+{{/container}}