Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-209 - Max Verstappen
	1	+219 - Creation Carousel

Content

...	...	@@ -3,62 +3,61 @@
3	3	(((
4	4	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5	5
6		-**Hi there, eMagiz developers!** We have improved the performance of our deployment plan, it should be finished much quicker now. Next to this, we have released new Docker Single Lane and Docker Double Lane cloud templates. Moreover, several feedback items have been processed and some bug fixes have been made. Lastly, as of this release, the next generation architecture will be our default.
	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, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 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.
7	7
8		-{{warning}}
9		-Please be aware that for this release, because of the duration of the deployment, we advise you to check your TEST and ACCP cloud slots status, since you might need to start them manually in case your model is using the automatic wake up functionality. For following releases we will set the automatic wake up time to 6:00 AM UTC instead of 5:00 AM UTC.
10		-{{/warning}}
	8	+== **Feedback Items** ==
11	11
12		-== **Quicker Deployment Plan Execution** ==
	10	+//__eMagiz Mendix connector__//
	11	+We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
13	13
14		-We sped up the process of preparing runtime images in executing the deployment plan. The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably. Moreover, we fixed an issue of the release preparation step taking longer than necessary which is caused by the machine deployment steps to be executed when they could have been skipped. So, the deployment plan will be finished much quicker now!
	13	+//__Improved OpenAPI import__//
	14	+The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
15	15
16		-== **Next Generation Architecture Default** ==
	16	+//__Flow test stack trace__//
	17	+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.
17	17
18		-With this release, the next generation architecture will become the default. From now on, new models will then use this generation as the default architecture.
	19	+[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
19	19
20		-[[image:Main.Images.Release Blog.WebHome@209-release-blog-next-gen-default.png]]
	21	+{{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.
21	21
22		-== **Cloud Template R11 Docker - Single Lane** ==
	23	+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.
23	23
24		-This release introduces a new cloud template for all our customers running in a single-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R11 Docker - Single Lane.WebHome||target="blank"]].
	25	+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}}
25	25
26		-== **Cloud Template R13 Docker - Double Lane** ==
27	27
28		-This release introduces a new cloud template for all our customers running in a double-lane setup on the next generation architecture. This cloud template introduces faster machine boot up and improved auto-healing. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Double Lane.WebHome||target="blank"]].
	28	+== **Bug Fixes** ==
	29	+//__Error handling__//
	30	+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.
29	29
30		-== **Feedback Items** ==
	32	+//__Volume mapping passwords__//
	33	+Passwords for network volumes are hidden on the machine after deployment.
31	31
32		-//__Unused properties overview__//
33		-In Deploy > Releases, it is now possible to see all unused properties of an environment. This can be viewed by clicking the three dots in the Create phase section. Here it is also possible to quickly delete all or a selection of those unused properties. Unused properties are properties that are:
	35	+//__Create integration removal__//
	36	+When removing an integration from Create, the Create phase is now correctly updated.
34	34
35		-* Not used by any runtime that is in the Create phase release.
36		-* Not required by a flow that is in the Create phase release.
37		-* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
	38	+//__Legacy statistics__//
	39	+Legacy pages are now correctly hidden when running on the current runtime architecture.
38	38
39		-[[image:Main.Images.Release Blog.WebHome@release-blog-209-unused-properties-overview.png]]
	41	+//__Unused properties__//
	42	+Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
40	40
41		-//__Queue explorer milliseconds__//
42		-The queue browser now displays milliseconds in the timestamps.
	44	+//__Enumeration values__//
	45	+Enumeration values for event processors can now be edited in Create.
43	43
44		-//__Static alerts queue consumers__//
45		-Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
	47	+[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
46	46
47		-== **Bug Fixes** ==
	49	+//__SFTP sessions__//
	50	+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.
48	48
49		-//__Flow Designer connection line__//
50		-In the Flow Designer an issue has been fixed, where, previously, the connection line for drawing channels did not work well after the user scrolls or zooms in/out on the canvas.
51		-
52		-//__Portal for migrated models__//
53		-We fixed a rare case where a runtime either (1) could not start, or (2) logging, errors, and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
54		-
55	55	== **Fancy Forum Answers** ==
56	56
57	57	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:
58	58
59		-* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
	56	+* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
	57	+* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
	58	+* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
60	60
61		-== **Key takeaways** ==
	60	+== **Key Takeaways** ==
62	62
63	63	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:
64	64
...	...	@@ -66,10 +66,9 @@
66	66	* If you have feedback or ideas for us, talk to the Platypus
67	67	* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
68	68	* Clear your browser cache (Ctrl + Shift + Del)
69		-* Check out the release notes [here]
	68	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
70	70	* Start thinking about how the license tracker can aid your development
71	71	* Start thinking about major, minor, and patch
72		-* 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,7 +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		-~*~* Indicates a next-generation-architecture only feature.
81	81	{{/info}}
82	82	)))
83	83