Changes for page 198 - Great Migration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+197 - Pay Attention

Content

...	...	@@ -2,72 +2,69 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some smalller fixes and beta features will be released to the community.
	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	6
7		-== **3rd generation runtime bolstering** ==
	7	+== **Event streaming alerting** ==
8	8
9		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy improvements we made to the 3rd generation runtime and the interaction with it.
	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.
10	10
11		-//__Migration of JMS backup configuration improved__//
	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.
12	12
13		-//__Prechecks on Upgrade option made available for 3rd generation runtime__//
	13	+The two "dynamic" alerts we have added mimic the alerting on queue level we already offer to the community.
14	14
15		-//__Autogenerated exits can be deployed at once__//
	15	+[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
16	16
17		-//__Code mapping functionality available on 3rd generation runtime__//
	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		-//__Improved the performance of deploying or activating a release__//
	19	+[[image:Main.Images.Release Blog.WebHome@196-release-blog--alert-config-example.png]]
20	20
21		-//__Failing runtimes won't be restarted indefinetly anymore__//
	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.
22	22
23		-== **Exportable Release Audit** ~* ==
	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"]].
24	24
25		-On top of that, we will also launch a new Beta feature to the community that allows you to export an audit document of your (Production) release.
	25	+== **3rd generation improvements** ==
26	26
27		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
	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.
28	28
29		-{{warning}}Note that the following restrictions apply when exporting an audit document:
30		- * Changes made on definition and transformation level are **not** restored
31		- * You will **not** be able to restore to any flow version that was created before October 17th, 2022
32		- * You will **not** be able to restore your flow to the original version created by eMagiz. You can use the reset function if you want this state back
33		- * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
	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.
34	34
	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.
	35	+
35	35	== **Feedback items ** ==
36	36
37		-We have also solved other feedback items besides the flow designer's critical updates.
	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.
38	38
39		-//__Data Sink Refactor__//
40		-We have made some infrastructural changes to how data sink messages are stored and can be retrieved from the portal. Should there be changes needed on your end we will contact your seperately.
	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.
41	41
42		-//__Improved naming convention on Store related pages__//
43		-We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
	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.
44	44
45		-//__Press "Enter" to search on multiple pages__//
46		-In our Daemon Switch release we added functionality that allowed you to press **Enter** to search on the property overview page. With this release we have added this functionality to many more pages across the portal. The complete list is as follows
	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.
47	47
48		-* Deploy → Deployment Plan
49		-* Deploy → Properties → History
50		-* Deploy → User Management → Roles
51		-* Manage → Error Messages → Error Messages
52		-* Manage → Error Messages → Flows with Error Messages
53		-* Manage → Error Messages → Exceptions of Error Messages
54		-* Manage → Log Entries
55		-* Manage → Alerts
56		-* Manage → Triggers
57		-* Manage → Tags – Cant find (only Gen2)
58		-* Manage → Notifications
59		-* Manage → Notification Settings
60		-* Manage → Data Usage → History
61		-* Manage → Code mappings → All tabs
	50	+== **Bug fixes ** ==
62	62
	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.
	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.
	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.
	60	+
63	63	== **Fancy Forum Answers** ==
64	64
65	65	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:
66	66
67		-* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
68		-* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
69		-* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
70		-* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
	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"]]
71	71
72	72	== **Key takeaways** ==
73	73