Changes for page 202 - New Equilibrium

Summary

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

Details

Page properties

Title

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

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -1,74 +1,77 @@
1	1	{{container}}
2		-{{container layoutStyle="columns"}}
3		-(((
	2	+{{container layoutStyle="columns"}}(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**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.
7	7
8		-== **Release Properties** ==
	7	+== **3rd generation runtime bolstering** ==
9	9
10		-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:
	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.
11	11
12		-* 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
13		-* 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.
14		-* 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.
15		-* A, for most, 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.
	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		-{{info}}
18		-For more information, please check out the following microlearnings:
	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.
19	19
20		-* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
21		-* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
22		-* [[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"]]
	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		-Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
25		-{{/info}}
	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		-== ** Manage - Graphs improvements ~*~* ** ==
	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		-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.
	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		-[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
	29	+== **Exportable Release Audit** ~* ==
32	32
33		-== **Feedback Items** ==
	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.
34	34
35		-//__Improved editability when testing in eMagiz without Edit rights in Create__//
36		-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.
	33	+[[image:Main.Images.Release Blog.WebHome@188-release-blog--exportable-release-audit.png]]
37	37
38		-//__Improved auditability on Deploy Architecture__//
39		-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).
	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	40
41		-//__Test your own exported store content__//
42		-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.
	41	+== **Feedback items ** ==
43	43
44		-{{info}}
45		-In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]
46		-{{/info}}
	43	+We have also solved other feedback items besides the flow designer's critical updates.
47	47
48		-//__Improved comparison of flows in the releases overview__//
49		-We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
	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.
50	50
51		-== **Bug Fixes** ==
	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.
52	52
53		-//__Improved validation on XPath header enricher__//
54		-To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
	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
55	55
56		-//__Cancel behavior on flow testing property overview fixed__//
57		-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.
58		-
59		-//__Cancel behavior on flow fragment level when exporting store content__//
60		-We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
61		-
62		-//__Adding numbers on containers in Deploy Architecture__//
63		-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.
64		-
65	65	== **Fancy Forum Answers** ==
66	66
67	67	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:
68	68
69		-* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
	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"]]
70	70
71		-== **Key Takeaways** ==
	74	+== **Key takeaways** ==
72	72
73	73	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:
74	74
...	...	@@ -76,7 +76,7 @@
76	76	* If you have feedback or ideas for us, talk to the Platypus
77	77	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
78	78	* Clear your browser cache (Ctrl + Shift + Del)
79		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.202 - New Equilibrium.WebHome||target="blank"]]
	82	+* Check out the release notes [here]
80	80	* Start thinking about how the license tracker can aid your development
81	81	* Start thinking about major, minor, and patch
82	82	* Upgrade to the latest build number
...	...	@@ -87,12 +87,6 @@
87	87	{{info}}
88	88	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
89	89
90		-~*~* Indicates a next-generation-architecture only feature.
91		-{{/info}}
92		-)))
93		-
94		-(((
95		-{{toc/}}
96		-)))
	93	+~*~* Indicates a GEN3-only feature.
	94	+{{/info}})))((({{toc/}}))){{/container}}
97	97	{{/container}}
98		-{{/container}}