Changes for page 214 - System Symphony

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+213 - Joyful Journeys

Author

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

Content

...	...	@@ -1,73 +1,93 @@
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!** In the last few weeks, we have worked hard on improving our next-generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore, several smaller feedback items and bugs have been resolved with this release. So without further ado, let us dive into all we have to offer.
	6	+**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done.
6	6
7		-== **Event streaming alerting** ==
	8	+== **Pop-up Improvements** ==
8	8
9		-This release expands our alerting functionality into the event streaming pattern. As of now, one new "static" alert has been introduced for all clients (using event streaming), and two "dynamic" alerts have been introduced that you can configure yourself if there is a need for it.
	10	+//__Property releases__//
	11	+When a new property release is created, this property release can now be viewed and deleted.
10	10
11		-The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights into whether messages on it are deleted due to a size or time constraint. In cases where data is deleted, the topic was too full way before the messages should have been removed due to the retention hours constraint. This alert can indicate that messages might be deleted before consumer groups had the option to consume the messages.
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
12	12
13		-The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
	15	+//__Runtime deletion__//
	16	+When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
	18	+//__Wiretap & debug error messages__//
	19	+The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
16	16
17		-The first new "dynamic" alert allows you to raise an alert once the number of messages on one (or more topics) is less than a certain number per defined time unit. So, for example, you can configure an alert once the number of messages placed on a topic called "Exception" is less than 15 messages within 5 minutes.
	21	+//__Action messages__//
	22	+The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
	24	+== **Formatting & Alignments** ==
20	20
21		-The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups are more than X messages behind on one or more topics. The configuration of this is comparable to what we saw before.
	26	+//__Input fields__//
	27	+Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
22	22
23		-For more information on the generic way of working surrounding alerting, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
	29	+//__UI improvements__//
	30	+UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
24	24
25		-== **3rd generation improvements** ==
	32	+//__Component changes reversion__//
	33	+In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
26	26
27		-//__Increased grace period for shutdown__//
28		-In this release, we have increased a container's grace period to shut down before it is forcefully shut down. This should reduce the chance of unwanted failover behavior within your model.
	35	+//__State generation statistics__//
	36	+The state generation graphs will now show the correct number of cache hits and misses.
29	29
30		-//__Update at once or not__//
31		-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.
	38	+//__Queue browser timestamps__//
	39	+All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
32	32
33		-//__Improved user feedback while executing a deployment plan__//
34		-This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information about why this cannot be executed is shown to the user. This way, they can take this information and act upon it instead of assuming everything went well.
	41	+//__Addition and deletion of internal recipients__//
	42	+Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
35	35
36		-//__Improved auto-healing when running in a hybrid situation__//
37		-In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
	44	+== **Feedback Items** ==
38	38
39		-//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
40		-To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
	46	+//__Update flows__//
	47	+In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
41	41
42		-{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
	49	+//__Q&A forum search__//
	50	+The option to search by pressing the Enter key has been added to the Q&A forum.
43	43
44		-== **Feedback items ** ==
	52	+//__Memory settings__//
	53	+It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
45	45
46		-//__Make sure the message format can be viewed without "Start editing"__//
47		-With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
	55	+//__Runtime validation__//
	56	+Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
48	48
49		-//__Various styling improvements in the flow testing functionality__//
50		-Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
	58	+//__Runtime overview image versions__//
	59	+Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
51	51
	61	+== **Bug Fixes** ==
	62	+
	63	+//__Removal of onramp__//
	64	+We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
	65	+
	66	+//__Runtime statistics details__//
	67	+We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
	68	+
	69	+//__Deployment prechecks__//
	70	+During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
	71	+
52	52	== **Fancy Forum Answers** ==
53	53
54	54	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:
55	55
56		-* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
57		-* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
	76	+* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
	77	+* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
	78	+* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
58	58
59		-== **Key takeaways** ==
	80	+== **Key Takeaways** ==
60	60
61		-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:
	82	+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:
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.
	86	+* 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	67	* 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
70		-* Upgrade to the latest build number
71	71	* Keep making great integrations
72	72
73	73	Let's stay in touch and till next time!
...	...	@@ -75,6 +75,11 @@
75	75	{{info}}
76	76	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77	77
78		-~*~* Indicates a GEN3-only feature.
79		-{{/info}})))((({{toc/}}))){{/container}}
	98	+{{/info}}
	99	+)))
	100	+
	101	+(((
	102	+{{toc/}}
	103	+)))
80	80	{{/container}}
	105	+{{/container}}