Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-202 - New Equilibrium
	1	+188 - Close Encounters

Content

...	...	@@ -2,65 +2,77 @@
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 few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you.
	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.
6	6
7		-== **Release Properties** ==
8		-As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
	7	+== **3rd generation runtime bolstering** ==
9	9
10		-* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
11		-* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
12		-* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers.
13		-* A, for most, a new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment.
	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.
14	14
15		-{{info}}For more information, please check out the following microlearnings:
	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.
16	16
17		-* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18		-* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
19		-* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
	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.
20	20
21		-Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22		-{{/info}}
	17	+//__Autogenerated exits can be deployed at once__//
	18	+This release has fixed a bug that prevented you from deploying an exit flow correctly.
23	23
24		-== ** Manage - Next generation graphs improvements ** ==
25		-As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out.
	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.
26	26
27		-[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
	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.
28	28
29		-== **Feedback Items** ==
	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.
30	30
31		-//__Improved editability when testing in eMagiz without Edit rights in Create__//
32		-Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
	29	+== **Exportable Release Audit** ~* ==
33	33
34		-//__Improved auditability on Deploy Architecture__//
35		-To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
	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.
36	36
37		-//__Test your own exported store content__//
38		-We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store.
	33	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
39	39
40		-{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals. fundamental-magic-store.WebHome||target="blank"]]{{/info}}
	35	+{{warning}}Note that the following restrictions apply when exporting an audit document:
	36	+ * Changes made on definition and transformation level are **not** restored
	37	+ * You will **not** be able to restore to any flow version that was created before October 17th, 2022
	38	+ * 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
	39	+ * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
41	41
42		-//__Improved comparison of flows in the releases overview__//
43		-We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
	41	+== **Feedback items ** ==
44	44
45		-== **Bug Fixes** ==
	43	+We have also solved other feedback items besides the flow designer's critical updates.
46	46
47		-//__Improved validation on XPath header enricher__//
48		-To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
	45	+//__Data Sink Refactor__//
	46	+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 you separately.
49	49
50		-//__Cancel behavior on flow testing property overview fixed__//
51		-We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
	48	+//__Improved naming convention on Store related pages__//
	49	+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.
52	52
53		-//__Cancel behavior on flow fragment level when exporting store content__//
54		-We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
	51	+//__Press "Enter" to search on multiple pages__//
	52	+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.
55	55
56		-//__Adding numbers on containers in Deploy Architecture__//
57		-With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
	54	+* Deploy → Deployment Plan
	55	+* Deploy → Properties → History
	56	+* Deploy → User Management → Roles
	57	+* Manage → Error Messages → Error Messages
	58	+* Manage → Error Messages → Flows with Error Messages
	59	+* Manage → Error Messages → Exceptions of Error Messages
	60	+* Manage → Log Entries
	61	+* Manage → Alerts
	62	+* Manage → Triggers
	63	+* Manage → Tags – Cant find (only Gen2)
	64	+* Manage → Notifications
	65	+* Manage → Notification Settings
	66	+* Manage → Data Usage → History
	67	+* Manage → Code mappings → All tabs
58	58
59	59	== **Fancy Forum Answers** ==
60	60
61	61	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:
62	62
63		-* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
	73	+* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
	74	+* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
	75	+* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
64	64
65	65	== **Key takeaways** ==
66	66