Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-194 - Big Leap
	1	+204 - Found It

Content

...	...	@@ -2,70 +2,39 @@
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 couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
	5	+**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
6	6
7		-== **3rd generation improvements** ==
	7	+== **Feedback Items** ==
8	8
9		-//__Better feedback in error log when a corrupt stylesheet is encountered__//
10		-We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
	9	+//__Improved check on nested property placeholders__//
	10	+To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
11	11
12		-//__Better internal error handling to avoid unnecessary alerting and notifications__//
13		-We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
	12	+//__Removed outdated properties when deploying on the new generation architecture stack__//
	13	+We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before in order to connect to a Kafka cluster but have become obsolete once you migrate.
14	14
15		-//__Improved Manage Dashboard__//
16		-This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
	15	+{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
17	17
18		-//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19		-When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
	17	+//__Improved performance Manage Dashboards__//
	18	+We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
20	20
21		-//__Improved process of deploy preparation__//
22		-With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
	20	+== **Bug Fixes** ==
23	23
24		-//__Improved migration of Streaming container__//
25		-When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
	22	+//__Errors with long stack traces or long message histories will now also show in eMagiz__//
	23	+We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
26	26
27		-//__Add History to Notifications in Manage__//
28		-To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
	25	+//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
	26	+We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
29	29
30		-//__Improved Manage phase for Event Streaming__//
31		-Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
32		-
33		-//__Improved help text for network volumes__//
34		-With this release we have improved the help text that explains network volumes and how to use them within our solution.
35		-
36		-{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
37		-
38		-== **Feedback items ** ==
39		-
40		-//__Removed OData as option for an API Gateway operation__//
41		-With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
42		-
43		-//__Changes in API Gateway operation paths is automatically updated in Create__//
44		-When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
45		-
46		-{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
47		-
48		-== **Bug fixes ** ==
49		-
50		-//__Prevent endless loop in Deploy -> User Management__//
51		-With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
52		-
53		-{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
54		-
55		-//__Update error handling during migration to the 3rd generation runtime__//
56		-As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
57		-
58	58	== **Fancy Forum Answers** ==
59	59
60	60	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:
61	61
62		-* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
63		-* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
64		-* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
	32	+* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
	33	+* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
65	65
66	66	== **Key takeaways** ==
67	67
68		-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:
	37	+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:
69	69
70	70	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71	71	* If you have feedback or ideas for us, talk to the Platypus
...	...	@@ -82,6 +82,6 @@
82	82	{{info}}
83	83	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
84	84
85		-~*~* Indicates a GEN3-only feature.
	54	+~*~* Indicates a next-generation-architecture only feature.
86	86	{{/info}})))((({{toc/}}))){{/container}}
87	87	{{/container}}