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	+188 - Close Encounters

Author

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

Content

...	...	@@ -1,72 +1,91 @@
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!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all its interactions. Furthermore, some minor fixes and beta features will be released to the community.
7	7
8		-== **Feedback Items** ==
	7	+== **3rd generation runtime bolstering** ==
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	+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.
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.
	11	+//__Migration of JMS backup configuration improved__//
	12	+With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
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.
	14	+//__Prechecks on Upgrade option made available for 3rd generation runtime__//
	15	+As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
	17	+//__Autogenerated exits can be deployed at once__//
	18	+This release has fixed a bug that prevented you from deploying an exit flow correctly.
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	+//__Code mapping functionality available on 3rd generation runtime__//
	21	+As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
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.
	23	+//__Improved the performance when activating a release__//
	24	+With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
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}}
	26	+//__Failing runtimes won't be restarted indefinitely anymore__//
	27	+We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
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.
	29	+== **Exportable Release Audit** ~* ==
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	+On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
33	33
34		-//__Create integration removal__//
35		-When removing an integration from Create, the Create phase is now correctly updated.
	33	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
36	36
37		-//__Legacy statistics__//
38		-Legacy pages are now correctly hidden when running on the current runtime architecture.
	35	+{{warning}}Note that the following restrictions apply when exporting an audit document:
	36	+ * Changes made on definition and transformation level are **not** restored
	37	+ * You will **not** be able to restore to any flow version that was created before October 17th, 2022
	38	+ * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
	39	+ * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
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.
	41	+== **Feedback items ** ==
42	42
43		-//__Enumeration values__//
44		-Users are now able to add and edit enumeration values while editing event processor flows in the Create phase.
	43	+We have also solved other feedback items besides the flow designer's critical updates.
45	45
46		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
	45	+//__Data Sink Refactor__//
	46	+We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end, we will contact you separately.
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	+//__Improved naming convention on Store related pages__//
	49	+We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
50	50
	51	+//__Press "Enter" to search on multiple pages__//
	52	+In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
	53	+
	54	+* Deploy → Deployment Plan
	55	+* Deploy → Properties → History
	56	+* Deploy → User Management → Roles
	57	+* Manage → Error Messages → Error Messages
	58	+* Manage → Error Messages → Flows with Error Messages
	59	+* Manage → Error Messages → Exceptions of Error Messages
	60	+* Manage → Log Entries
	61	+* Manage → Alerts
	62	+* Manage → Triggers
	63	+* Manage → Tags – Cant find (only Gen2)
	64	+* Manage → Notifications
	65	+* Manage → Notification Settings
	66	+* Manage → Data Usage → History
	67	+* Manage → Code mappings → All tabs
	68	+
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"]]
	73	+* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
	74	+* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
	75	+* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
58	58
59		-== **Key Takeaways** ==
	77	+== **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:
	79	+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.
	83	+* 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"]]
	85	+* 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
	88	+* 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		-)))
	96	+~*~* Indicates a GEN3-only feature.
	97	+{{/info}})))((({{toc/}}))){{/container}}
83	83	{{/container}}
84		-{{/container}}