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,83 +1,95 @@
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 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, some more feedback items and bug fixes have been done.
6	6
7		-== **Event streaming alerting** ==
	8	+== **Pop-up Improvements** ==
	9	+//__Property releases__//
	10	+When a new property release is created, this property release can now be viewed and deleted.
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.
	12	+[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
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.
	14	+//__Runtime deletion__//
	15	+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.
12	12
13		-The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
	17	+//__Wiretap & debug error messages__//
	18	+The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
	20	+//__Action messages__//
	21	+The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
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.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@196-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 is more than X number of messages behind on one or more topics. The configuration of this is comparable as 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.WebHome||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		-//__Event Streaming statistics completion__//
28		-In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
	35	+//__State generation statistics__//
	36	+The state generation graphs will now show the correct number of cache hits and misses.
29	29
30		-//__Deployments on next generation architecture__//
31		-This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
	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		-//__Clean queues option__//
34		-This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
	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		-== **Feedback items ** ==
37	37
38		-//__On-premise containers are started upon slot wakeup__//
39		-With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
	45	+== **Feedback Items** ==
40	40
41		-//__Resource path is shown to the user__//
42		-You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
	47	+//__Update flows__//
	48	+In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
43	43
44		-//__Flow designer improvements__//
45		-With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
	50	+//__Q&A forum search__//
	51	+The option to search by pressing the Enter key has been added to the Q&A forum.
46	46
47		-//__Improved capabilities of a company contact__//
48		-With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
	53	+//__Memory settings__//
	54	+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.
49	49
50		-== **Bug fixes ** ==
	56	+//__Runtime validation__//
	57	+Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
51	51
52		-//__Optional API parameters are handled correctly__//
53		-Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
	59	+//__Runtime overview image versions__//
	60	+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.
54	54
55		-//__Without CDM rights nothing related to any data model can be edited anymore__//
56		-With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
	62	+== **Bug Fixes** ==
57	57
58		-//__Improved sorting of Design and Deploy archticture__//
59		-With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
	64	+//__Removal of onramp__//
	65	+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).
60	60
	67	+//__Runtime statistics details__//
	68	+We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
	69	+
	70	+//__Deployment prechecks__//
	71	+During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
	72	+
	73	+
61	61	== **Fancy Forum Answers** ==
62	62
63	63	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:
64	64
65		-* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
66		-* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
67		-* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||target="blank"]]
	78	+* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
	79	+* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
	80	+* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
68	68
69		-== **Key takeaways** ==
	82	+== **Key Takeaways** ==
70	70
71		-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:
	84	+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:
72	72
73	73	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74	74	* If you have feedback or ideas for us, talk to the Platypus
75		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	88	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
76	76	* Clear your browser cache (Ctrl + Shift + Del)
77	77	* Check out the release notes [here]
78	78	* Start thinking about how the license tracker can aid your development
79	79	* Start thinking about major, minor, and patch
80		-* Upgrade to the latest build number
81	81	* Keep making great integrations
82	82
83	83	Let's stay in touch and till next time!
...	...	@@ -85,6 +85,11 @@
85	85	{{info}}
86	86	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
87	87
88		-~*~* Indicates a GEN3-only feature.
89		-{{/info}})))((({{toc/}}))){{/container}}
	100	+{{/info}}
	101	+)))
	102	+
	103	+(((
	104	+{{toc/}}
	105	+)))
90	90	{{/container}}
	107	+{{/container}}