Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-199 - Home Improvements
	1	+185 - To determine

Author

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

Content

...	...	@@ -2,48 +2,48 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
	5	+**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
6	6
7		-== **Next generation improvements and bug fixes** ==
	7	+==**Audit trail User Management**==
8	8
9		-//__Enhanced overview of the HTTP Statistics__//
10		-As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
	9	+
	10	+==**Next Generation Monitoring & Alerting engine**==
	11	+In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now used State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations. In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach). We have already released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]]
	12	+
	13	+=== **Improvements** ===
	14	+
	15	+* Performance Deployment plan
	16	+When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
	17	+
	18	+* Flow Designer updates
	19	+We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
	20	+
	21	+
	22	+
	23	+
	24	+[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
11	11
12		-//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13		-In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
	26	+
	27	+== **Feedback items ** ==
14	14
15		-{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	29	+We have also solved other feedback items besides the key updates around functionality.
16	16
17		-//__Forced congestion control__//
18		-To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
	31	+//__Set runtime field as first selected field on property level__//
	32	+With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well.
19	19
	34	+[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
	35	+
20	20
21		-//__Improved validation errors on the invalid configuration of HTTP outbound components__//
22		-This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
23		-
24		-//__Improved migration behavior__//
25		-This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
26		-A smoother migration of your JMS (and backup JMS) process.
27		-Shortening of names that otherwise would be too long, additional feedback given to the user.
28		-Feedback when the migration process is finished.
29		-
30		-//__Additional checks when deploying__//
31		-This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
32		-
33		-== **Store Improvements** ==
34		-
35		-== **Event Streaming - Certificate Management** ==
36		-
37	37	== **Fancy Forum Answers** ==
38	38
39		-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:
	39	+As always, a gentle reminder to all 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:
40	40
41		-* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
42		-* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
	41	+* [[Start runtime via a delayed start in a Linux environment?>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
	42	+* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
43	43
44	44	== **Key takeaways** ==
45	45
46		-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:
	46	+Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
47	47
48	48	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
49	49	* If you have feedback or ideas for us, talk to the Platypus
...	...	@@ -54,11 +54,12 @@
54	54	* Start thinking about major, minor, and patch
55	55	* Upgrade to the latest build number
56	56	* Keep making great integrations
	57	+* Check out the new documentation portal.
57	57
58	58	Let's stay in touch and till next time!
59	59
60	60	{{info}}
61		-~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
	62	+~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
62	62
63	63	~*~* Indicates a GEN3-only feature.
64	64	{{/info}})))((({{toc/}}))){{/container}}