Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-223 - TBD
	1	+203 - Fast Paced

Author

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

Content

...	...	@@ -1,68 +1,49 @@
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!**
7		-
8		-== **Feedback Items** ==
9		-//__SwaggerUI default__//
10		-Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown.
	5	+**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
11	11
12		-[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
	7	+== **Release Properties - Early Feedback** ==
	8	+The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
13	13
14		-//__Deprecated warnings__//
15		-We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10.
	10	+== **Feedback Items** ==
16	16
17		-//__Used message types__//
18		-It is now possible to filter the message types in Capture on whether they are used.
	12	+//__"All entries" are now cleaned up as part of the migration__//
	13	+To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
19	19
20		-[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]]
21		-
22		-//__Debugger duration__//
23		-Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be reset (or updated) in order to also store the messages for 10 minutes instead of 5. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
	15	+//__Trigger ID added to our alerting on the next-generation architecture__//
	16	+We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
24	24
	18	+//__Improved performance Manage Dashboards__//
	19	+We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture.
	20	+
25	25	== **Bug Fixes** ==
26		-//__SFTP sessions__//
27		-Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
28	28
29		-[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
	23	+//__Ensure no flow can be in a release twice__//
	24	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
30	30
	26	+//__Sped up adding a new operation to the API Gateway solution__//
	27	+We have fixed a bug that slowed down the addition of new operations to the API Gateway solution.
31	31
32		-[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
33		-
34		-//__SFTP sessions__//
35		-The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
36		-
37		-//__TaskScheduler__//
38		-In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
39		-
40		-//__View XSLT__//
41		-We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
42		-
43		-//__Multipart/form-data HTTP request__//
44		-The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite.
45		-
46	46	== **Fancy Forum Answers** ==
47	47
48	48	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:
49	49
50		-* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
51		-* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
52		-* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
53		-* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
	33	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
54	54
55		-== **Key Takeaways** ==
	35	+== **Key takeaways** ==
56	56
57		-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:
	37	+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:
58	58
59	59	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
60	60	* If you have feedback or ideas for us, talk to the Platypus
61		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	41	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
62	62	* Clear your browser cache (Ctrl + Shift + Del)
63		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
	43	+* Check out the release notes [here]
64	64	* Start thinking about how the license tracker can aid your development
65	65	* Start thinking about major, minor, and patch
	46	+* Upgrade to the latest build number
66	66	* Keep making great integrations
67	67
68	68	Let's stay in touch and till next time!
...	...	@@ -70,11 +70,6 @@
70	70	{{info}}
71	71	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
72	72
73		-{{/info}}
74		-)))
75		-
76		-(((
77		-{{toc/}}
78		-)))
	54	+~*~* Indicates a next-generation-architecture only feature.
	55	+{{/info}})))((({{toc/}}))){{/container}}
79	79	{{/container}}
80		-{{/container}}