Changes for page 222 - Flee Frustration

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-219 - Creation Carousel
	1	+202 - New Equilibrium

Author

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

Content

...	...	@@ -1,75 +1,79 @@
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!** This release, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, we have improved our functionality to enable users to seamlessly import OpenAPI specifications with URL paths of up to 300 characters in length. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
	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.
7	7
8		-== **Feedback Items** ==
	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:
9	9
10		-//__eMagiz Mendix connector__//
11		-We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
	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, 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.
12	12
13		-//__External machine agents__//
14		-We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents on the current generation architecture from the portal. With future releases of environment templates, your on-premise agents may also be updated.
	15	+{{info}}For more information, please check out the following microlearnings:
15	15
16		-//__Improved OpenAPI import__//
17		-The path length that eMagiz supports when importing OpenAPI specifications is now increased to a maximum of 300 characters.
	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"]]
18	18
19		-//__Flow test stack trace__//
20		-If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab.
	21	+Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	22	+{{/info}}
21	21
22		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
	24	+== ** Manage - 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.
23	23
24		-{{info}}With the release of Spring 6 in our previous release, some users reported that their filters have begun logging warnings about discarding messages even though the filter is configured to not throw an exception on rejection. For flows that process high numbers of messages (and potentially discard a lot of messages as well) this can significantly disturb the overview of the logs in the manage phase.
	27	+[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
25	25
26		-To mitigate this, you can change the filter that throws the warning so it specifically refers to a discard channel. Given the chosen configuration, we advice to use the nullChannel option. This will silently drop the message without registering a warning in the log. In case you find the warning in the log a nice addition, we suggest to add an explicit discard channel leading to a logging outbound channel adapter. This log component can then be configured to throw a warning.
	29	+== **Feedback Items** ==
27	27
28		-In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}}
	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	29
30		-== **Bug Fixes** ==
31		-//__Error handling__//
32		-When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
	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).
33	33
34		-//__Volume mapping passwords__//
35		-Passwords for network volumes are now securely hidden in the runtime’s machine after deploying a new release.
	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.
36	36
37		-//__Create integration removal__//
38		-When removing an integration from Create, the Create phase is now correctly updated.
	40	+{{info}}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"]]{{/info}}
39	39
40		-//__Legacy statistics__//
41		-Legacy pages are now correctly hidden when running on the current runtime architecture.
	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.
42	42
43		-//__Unused properties__//
44		-Users should not be able to edit or delete eMagiz properties, and so these eMagiz properties will now not be shown in the 'Unused property overview' anymore.
	45	+== **Bug Fixes** ==
45	45
46		-//__Enumeration values__//
47		-Users are now able to add and edit enumeration values while editing event processor flows in the Create phase.
	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.
48	48
49		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
	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.
50	50
51		-//__SFTP sessions__//
52		-SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
	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.
53	53
	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.
	58	+
54	54	== **Fancy Forum Answers** ==
55	55
56	56	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:
57	57
58		-* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
59		-* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
60		-* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
	63	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
61	61
62		-== **Key Takeaways** ==
	65	+== **Key takeaways** ==
63	63
64		-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:
	67	+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:
65	65
66	66	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
67	67	* If you have feedback or ideas for us, talk to the Platypus
68		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	71	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
69	69	* Clear your browser cache (Ctrl + Shift + Del)
70		-* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
	73	+* Check out the release notes [here]
71	71	* Start thinking about how the license tracker can aid your development
72	72	* Start thinking about major, minor, and patch
	76	+* Upgrade to the latest build number
73	73	* Keep making great integrations
74	74
75	75	Let's stay in touch and till next time!
...	...	@@ -77,11 +77,6 @@
77	77	{{info}}
78	78	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
79	79
80		-{{/info}}
81		-)))
82		-
83		-(((
84		-{{toc/}}
85		-)))
	84	+~*~* Indicates a next-generation-architecture only feature.
	85	+{{/info}})))((({{toc/}}))){{/container}}
86	86	{{/container}}
87		-{{/container}}