Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

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

Content

...	...	@@ -2,76 +2,65 @@
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 its interactions. Furthermore, some minor fixes and beta features will be released to the community.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
6	6
7		-== **3rd generation runtime bolstering** ==
	7	+== **3rd generation improvements** ==
8	8
9		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
	9	+//__Better feedback in the 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.
10	10
11		-//__Migration of JMS backup configuration improved__//
12		-With this release, the configuration of the JMS backup configuration is improved to prevent potential connectivity issues after migrating to the 3rd generation runtime.
	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 alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
13	13
14		-//__Prechecks on Upgrade option made available for 3rd generation runtime__//
15		-As with the current runtime architecture, you can now also execute the prechecks before automatically upgrading to the latest cloud template on the 3rd generation runtime architecture.
	15	+//__Improved Manage Dashboard__//
	16	+This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
16	16
17		-//__Autogenerated exits can be deployed at once__//
18		-This release has fixed a bug that prevented you from deploying an exit flow correctly.
	18	+//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
	19	+When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. 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.
19	19
20		-//__Code mapping functionality available on 3rd generation runtime__//
21		-As of this release, code mapping functionality is also available for the 3rd generation runtime. This removes the restriction on migrating to the new 3rd generation runtime for our clients that use the code mapping functionality.
	21	+//__Improved process of deploy preparation__//
	22	+With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
22	22
23		-//__Failing runtimes won't be restarted indefinitely anymore__//
24		-We have put a cap on this behavior to prevent your logs from exploding due to a failing runtime being restarted indefinitely. As of this release, five attempts will be made to restart a failing runtime. If the runtime can not start correctly after these attempts, the runtime will be stopped.
	24	+//__Improved migration of Streaming container__//
	25	+When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
25	25
26		-== **Exportable Release Audit** ~* ==
	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.
27	27
28		-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.
	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 help texts to clarify what each chart our table displays to you.
29	29
30		-[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
	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.
31	31
32		-{{warning}}Note that the following restrictions apply when exporting an audit document:
33		- * Works **only** for releases that are promoted and made active on **Production**
34		- * You will **only** see changes made during the **current** calendar year
35		- * On the first of April all objects of the **last** calendar year will be **removed**.
36		- ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
	36	+{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate 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	37
38	38	== **Feedback items ** ==
39	39
40		-We have also solved other feedback items besides the flow designer's critical updates.
	40	+//__Generation of security logic API Gateway in case of API Key as security method is improved__//
	41	+With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
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.
	43	+//__User Roles are sorted alphabetically__//
	44	+All user roles under User Management are now also sorted alphabetically.
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. This release has added this functionality to many more pages across the portal. The complete list is as follows.
	46	+//__Name of keystore for user management now includes the environment__//
	47	+To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
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
62		-
63	63	== **Bug fixes ** ==
64	64
65		-//__Loading problems of Deployment plan execution overview__//
66		-We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
	51	+//__Consolidated upgrade process cloud template__//
	52	+With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
67	67
	54	+//__Ensure users can deploy release on environments they have edit rights on__//
	55	+Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
	56	+
68	68	== **Fancy Forum Answers** ==
69	69
70	70	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:
71	71
72		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
73		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
74		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
	61	+* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
	62	+* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
	63	+* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
75	75
76	76	== **Key takeaways** ==
77	77