Changes for page 210 - Deployment Delights

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-194 - Big Leap
	1	+188 - Close Encounters

Content

...	...	@@ -2,66 +2,72 @@
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!** 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.
6	6
7		-== **3rd generation improvements** ==
	7	+== **3rd generation runtime bolstering** ==
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	+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.
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.
	11	+//__Migration of JMS backup configuration improved__//
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.
	13	+//__Prechecks on Upgrade option made available for 3rd generation runtime__//
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.
	15	+//__Autogenerated exits can be deployed at once__//
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.
	17	+//__Code mapping functionality available on 3rd generation runtime__//
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.
	19	+//__Improved the performance of deploying or activating a release__//
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.
	21	+//__Failing runtimes won't be restarted indefinetly anymore__//
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.
	23	+== **Exportable Release Audit** ~* ==
32	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.
	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.
35	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.WebHome||target="blank"]] on the subject.{{/warning}}
	27	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
37	37
	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}}
	34	+
38	38	== **Feedback items ** ==
39	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.
	37	+We have also solved other feedback items besides the flow designer's critical updates.
42	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.
	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.
45	45
46		-{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
	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.
47	47
48		-== **Bug fixes ** ==
	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
49	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.
	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
52	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"]]
	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	65
66	66	== **Key takeaways** ==
67	67