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,69 +1,96 @@
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 work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that 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 achieved.
6	6
7		-== **Event streaming alerting** ==
8	8
9		-With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is need for it.
	9	+== **Pop-up Improvements** ==
	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 whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication 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 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 total 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 message 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@196-release-blog--alert-config-example.png]]
20	20
21		-The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups is more than X number of messages behind on one or more topics. The configuration of this is comparable as we saw before.
	25	+== **Formatting & Alignments** ==
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"]].
	27	+//__Input fields__//
	28	+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.
24	24
25		-== **3rd generation improvements** ==
	30	+//__UI improvements__//
	31	+UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
26	26
27		-//__Increased grace period for shutdown__//
28		-In this release, we have increased the grace period a container gets to shutdown before it is forcefully shutdown. This should reduce the chance of unwanted failover behavior to pop-up within your model.
	33	+//__Component changes reversion__//
	34	+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.
29	29
30		-//__Update at once or not__//
31		-This release fixes 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.
	36	+//__State generation statistics__//
	37	+The state generation graphs will now show the correct number of cache hits and misses.
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 of 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.
	39	+//__Queue browser timestamps__//
	40	+All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
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.
	42	+//__Addition and deletion of internal recipients__//
	43	+Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
38	38
39		-== **Feedback items ** ==
40	40
41		-//__Make sure the message format can be viewed without "Start editing"__//
42		-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.
	46	+== **Feedback Items** ==
43	43
44		-//__Various styling improvements in the flow testing functionality__//
45		-Various smaller styling improvements have been added to the flow testing functionality to improve the overall user experience. For a complete list and more details please check out the release notes.
	48	+//__Update flows__//
	49	+In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
46	46
	51	+//__Q&A forum search__//
	52	+The option to search by pressing the Enter key has been added to the Q&A forum.
	53	+
	54	+//__Memory settings__//
	55	+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.
	56	+
	57	+//__Runtime validation__//
	58	+Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
	59	+
	60	+//__Runtime overview image versions__//
	61	+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.
	62	+
	63	+== **Bug Fixes** ==
	64	+
	65	+//__Removal of onramp__//
	66	+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).
	67	+
	68	+//__Runtime statistics details__//
	69	+We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
	70	+
	71	+//__Deployment prechecks__//
	72	+During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
	73	+
	74	+
47	47	== **Fancy Forum Answers** ==
48	48
49	49	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:
50	50
51		-* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
52		-* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
53		-* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
	79	+* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
	80	+* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
	81	+* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
54	54
55		-== **Key takeaways** ==
	83	+== **Key Takeaways** ==
56	56
57		-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:
	85	+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:
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.
	89	+* 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	63	* 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
66		-* Upgrade to the latest build number
67	67	* Keep making great integrations
68	68
69	69	Let's stay in touch and till next time!
...	...	@@ -71,6 +71,11 @@
71	71	{{info}}
72	72	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73	73
74		-~*~* Indicates a GEN3-only feature.
75		-{{/info}})))((({{toc/}}))){{/container}}
	101	+{{/info}}
	102	+)))
	103	+
	104	+(((
	105	+{{toc/}}
	106	+)))
76	76	{{/container}}
	108	+{{/container}}