Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-190 - Fast Forward
	1	+219 - Creation Carousel

Author

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

Content

...	...	@@ -1,137 +1,72 @@
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!** It has been a while since our last deployment on the 9th of December. As a result, we have finished up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs and some minor enhancements. This release is characterized by the significant steps we took to release several major features on our 3rd generation runtime, including the queue browser and message redelivery functionality.
	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		-== **Queue Browser** ~*~* ==
	8	+== **Feedback Items** ==
8	8
9		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime{{/warning}}
	10	+//__eMagiz Mendix connector__//
	11	+We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
10	10
11		-To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called the "Queue browser." You can access this functionality via the "Explore" menu in Manage. Then, with the help of the queue browser, you can browse your queue as the name suggests.
	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	12
13		-To do so, we offer two options within this functionality. First, we have the Explore function, and we have the Wiretap function. When selecting a queue and opting for the Explore option, you get a live view of the current data in the queue. Then, when choosing the Wiretap functionality, you automatically wiretap your queue and are presented with copies (on a particular queue) of your actual message that passes through the queue from the moment you press the Wiretap button.
	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	14
15		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-overview.png]]
	19	+[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
16	16
17		-After selecting the queue and choosing the option, eMagiz will show you the list of messages (oldest first) that are currently on the queue (Explore option), or that passed the queue since the moment you activate the option (Wiretap option). For each message, you have various options at your disposal.
	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.
18	18
19		-* Delete the message from the queue (Explore option)
20		- ** This means throwing away live data, which can be helpful in a test or acceptance environment where you inadvertently put many messages on a queue.
21		-* Clear message from the wiretap queue (Wiretap option)
22		- ** Once you are done with the analysis of a specific message in the wiretap functionality, you can clear it from the overview so it does not clutter the view anymore
23		-* Refresh messages list (both options)
24		- ** By pressing this button, you can refresh the list of messages displayed to you. Note that the list is sorted in such a way that the oldest messages are shown first
25		-* Save as test message
26		- ** By pressing this button, you can save the message and use it in our flow testing functionality in Create. Note that we link the message to the corresponding flow if we can. Should we not be able to do so, we link the message to your model so you can still use it in the flow testing functionality.
27		-* Download
28		- ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
	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.
29	29
30		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-explore-overview.png]]
	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}}
31	31
32		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--queue-browser-wiretap-overview.png]]
	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.
33	33
34		-{{info}}The following restrictions apply to this functionality:
35		- * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
36		- * The wiretap functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
37		- ** After five minutes the wiretap functionality will be shutdown automatically under water.
38		- ** To see new messages after the five minutes you will have to access the wiretap functionality again from scratch.{{/info}}
	31	+//__Volume mapping passwords__//
	32	+Passwords for network volumes are now securely hidden in the runtime’s machine after deploying a new release.
39	39
40		-== **Message Redelivery ** ~*~* ==
	34	+//__Create integration removal__//
	35	+When removing an integration from Create, the Create phase is now correctly updated.
41	41
42		-{{warning}}Note that this functionality only works when your JMS server is running on the 3rd generation runtime, and the functionality is enabled for your environment.{{/warning}}
	37	+//__Legacy statistics__//
	38	+Legacy pages are now correctly hidden when running on the current runtime architecture.
43	43
44		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-overview.png]]
	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.
45	45
46		-As with our current offering, we now offer our message redelivery functionality for our 3rd generation architecture. To enhance the user experience, we have placed this functionality under the "Explore" option in Manage. When selecting the message redelivery option, you will see all messages that currently need to be redelivered (as an error occurred).
	43	+//__Enumeration values__//
	44	+Enumeration values for event processors can now be edited in Create.
47	47
48		-As in the current functionality, you can select a specific message and retry (or delete) it. The same can be done for all messages at once. Following that, you can still see the linked error message as you could before.
	46	+[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
49	49
50		-On top of that, we have added some additional functionality.
	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.
51	51
52		-* Search option
53		- ** Original queue name
54		- ** Original message ID (which can be found as a header called jms_messageid in the error message view)
55		-* Save as test message
56		- ** By pressing this button, you can save the message and use it in our flow testing functionality in Create.
57		-* Download
58		- ** By pressing this button, you can download the message and use it outside of the tooling should that be needed.
59		-
60		-[[image:Main.Images.Release Blog.WebHome@190-release-blog--message-redelivery-detail-overview.png]]
61		-
62		-== **3rd generation runtime bolstering** ==
63		-
64		-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.
65		-
66		-//__Define memory settings for on-premise runtimes from Deploy Architecture__//
67		-With this release, you can now define the memory settings (and, therefore, the memory limits) of your on-premise runtimes in the same manner as cloud runtimes. In all cases, you can now define and change the memory settings via Deploy Architecture. In contrast to how these values are actualized for cloud runtimes, you need to create a new release and deploy it to actualize the changes on-premise.
68		-
69		-//__Empty runtime feedback when deploying a release (or setting the release as active)__//
70		-To prevent you are not being able to deploy a release to your environment due to a mismatch between what is in your release and Deploy Architecture, we have now added a feedback pop-up when deploying a release that notifies you for which runtimes there is a mismatch between your release and Deploy Architecture.
71		-
72		-//__Auto-fill namespaces for SOAP hosted webservices__//
73		-Based on your configuration in Design, eMagiz will now auto-fill the namespace when you host a SOAP web service. This avoids any potential problems in validating messages.
74		-
75		-//__Updated H2 database setting__//
76		-As of this release, we have improved the configuration of our H2 databases used within eMagiz. This new setting will ensure the runtime controls when the H2 database is shut down.
77		-
78		-{{warning}}If you already migrated your runtime, you should execute a "Reset" action on the infra flow to get these changes in your model{{/warning}}
79		-
80		-//__Runtime settings option added to context menu on runtime level Deploy Architecture__//
81		-As a replacement for the current HTTP settings context menu, we added a new menu item called runtime settings. On top of being able to configure your HTTP settings (which you need to define for a hosted web service), you now also can define whether the control bus needs to work for this runtime.
82		-
83		-//__Deploy Agent option added to context menu on machine level Deploy Architecture__//
84		-With this release, we have added a context menu item allowing users to deploy the agent needed to run your 3rd generation architecture on-premise. For more information on installing this, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-installguide.WebHome||target="blank"]]
85		-
86		-//__Performance improvement creating a release__//
87		-With this release, we have improved the performance of creating a release.
88		-
89		-== **Feedback items ** ==
90		-
91		-We have also solved other feedback items besides the flow designer's critical updates.
92		-
93		-//__Sensitive information stored in properties is masked __//
94		-We have made how we display sensitive information across the portal similar for various parts of the portal.
95		-
96		-//__Importing "Private" store content to which you do not have access__//
97		-We have improved the user feedback a user will get when trying to import a "Private" store item unavailable to the user.
98		-
99		-
100		-== **Bug fixes ** ==
101		-
102		-//__Fix the possibility that allowed you to break the system message when dealing with the "Order matters" functionality__//
103		-We have fixed the possibility you had that would break your system message upon validating it in Create when using the "Order matters" functionality.
104		-
105		-//__Synchronization of Event Streaming topic states__//
106		-We fixed synchronization issues that could occur when several changes were executed on a model that uses a fast amount of topics.
107		-
108		-//__Copy and paste default support objects__//
109		-With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
110		-
111		-//__Fix editability of properties when importing store items__//
112		-With this release, you can once again change property names upon importing a store item.
113		-
114	114	== **Fancy Forum Answers** ==
115	115
116	116	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:
117	117
118		-* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
119		-* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
120		-* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
121		-* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
	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"]]
122	122
123		-== **Key takeaways** ==
	59	+== **Key Takeaways** ==
124	124
125		-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:
	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:
126	126
127	127	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
128	128	* If you have feedback or ideas for us, talk to the Platypus
129		-* 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.
130	130	* Clear your browser cache (Ctrl + Shift + Del)
131		-* Check out the release notes [here]
	67	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
132	132	* Start thinking about how the license tracker can aid your development
133	133	* Start thinking about major, minor, and patch
134		-* Upgrade to the latest build number
135	135	* Keep making great integrations
136	136
137	137	Let's stay in touch and till next time!
...	...	@@ -139,6 +139,11 @@
139	139	{{info}}
140	140	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
141	141
142		-~*~* Indicates a GEN3-only feature.
143		-{{/info}})))((({{toc/}}))){{/container}}
	77	+{{/info}}
	78	+)))
	79	+
	80	+(((
	81	+{{toc/}}
	82	+)))
144	144	{{/container}}
	84	+{{/container}}