Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-188 - Close Encounters
	1	+204 - Found It

Content

...	...	@@ -2,78 +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!** 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!** 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 runtime bolstering** ==
	7	+== **Feedback Items** ==
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	+//__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.
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	+//__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 connecting to a Kafka cluster but have become obsolete once you migrate.
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	+{{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}}
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.
	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.
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.
	20	+== **Bug Fixes** ==
22	22
23		-//__Improved the performance when activating a release__//
24		-With this release, the performance of activating a release has improved considerably. This means less waiting time when activating a release.
	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).
25	25
26		-//__Failing runtimes won't be restarted indefinitely anymore__//
27		-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.
	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.
28	28
29		-== **Exportable Release Audit** ~* ==
30		-
31		-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.
32		-
33		-[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
34		-
35		-{{warning}}Note that the following restrictions apply when exporting an audit document:
36		- * Works **only** for releases that are promoted and made active on **Production**
37		- * You will **only** see changes made during the **current** calendar year
38		- * On the first of April all objects of the **last** calendar year will be **removed**.
39		- ** As a consequence you cannot download this information anymore **after** the first of April{{/warning}}
40		-
41		-== **Feedback items ** ==
42		-
43		-We have also solved other feedback items besides the flow designer's critical updates.
44		-
45		-//__Improved naming convention on Store related pages__//
46		-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		-
48		-//__Press "Enter" to search on multiple pages__//
49		-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.
50		-
51		-* Deploy → Deployment Plan
52		-* Deploy → Properties → History
53		-* Deploy → User Management → Roles
54		-* Manage → Error Messages → Error Messages
55		-* Manage → Error Messages → Flows with Error Messages
56		-* Manage → Error Messages → Exceptions of Error Messages
57		-* Manage → Log Entries
58		-* Manage → Alerts
59		-* Manage → Triggers
60		-* Manage → Tags – Cant find (only Gen2)
61		-* Manage → Notifications
62		-* Manage → Notification Settings
63		-* Manage → Data Usage → History
64		-* Manage → Code mappings → All tabs
65		-
66	66	== **Fancy Forum Answers** ==
67	67
68	68	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:
69	69
70		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
71		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
72		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||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"]]
73	73
74	74	== **Key takeaways** ==
75	75
76		-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:
77	77
78	78	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
79	79	* If you have feedback or ideas for us, talk to the Platypus
...	...	@@ -90,6 +90,6 @@
90	90	{{info}}
91	91	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
92	92
93		-~*~* Indicates a GEN3-only feature.
	54	+~*~* Indicates a next-generation-architecture only feature.
94	94	{{/info}})))((({{toc/}}))){{/container}}
95	95	{{/container}}