Changes for page 224 - Summer Sonata

Summary

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

Details

Page properties

Title

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

Content

...	...	@@ -1,65 +1,69 @@
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!** We have done .....
7	7
8		-== **Feedback Items** ==
	7	+{{warning}}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. {{/warning}}
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.
	9	+== **Quicker Deployment Plan** ==
	10	+We fixed an issue which caused the release preparation step to take longer than necessary and caused the machine deployment steps to execute when they could be skipped. So, the deploynment plan will be finished much quicker now!
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.
	12	+== **Next Generation Architecture Default** ==
	13	+With this release, the next generation architecture will become the default. New models will use this generation as default.
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.
	15	+[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
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.
	17	+== **Cloud Template R11 Docker - Single Lane** ==
	18	+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"]].
21	21
22		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
	20	+== **Cloud Template R13 Docker - Double Lane** ==
	21	+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"]].
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.
	23	+== **Feedback Items** ==
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.
	25	+//__Unused properties overview__//
	26	+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:
	27	+* Not used by any runtime that is in the Create phase release.
	28	+* Not required by a flow that is in the Create phase release.
	29	+* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
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	+//__Send build requests asynchronously__//
	32	+The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
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	+//__Queue explorer milliseconds__//
	35	+The queue browser now displays milliseconds in the timestamps.
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	+//__Cancel and next buttons order__//
	38	+The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
36	36
37		-//__Create integration removal__//
38		-When removing an integration from Create, the Create phase is now correctly updated.
	40	+//__Unused images__//
	41	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
39	39
40		-//__Legacy statistics__//
41		-Legacy pages are now correctly hidden when running on the current runtime architecture.
	43	+//__Carwash logging__//
	44	+A new logging feature enabling us to make better choices in encryption standards will be released.
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.
	46	+//__Static alerts queue consumers__//
	47	+Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
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.
	49	+== **Bug Fixes** ==
48	48
49		-[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
	51	+//__Flow Designer connection line__//
	52	+In the Flow Designer an issue has been fixed where the connection line for drawing channels did work well when scrolling or zooming in/out on the canvas.
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.
	54	+//__Portal for migrated models__//
	55	+We fixed a rare case where a runtime could not start, or logging, errors and metrics could not be seen in the portal for a model that had just migrated to the next generation architecture.
53	53
	57	+//__Error channel inbounds__//
	58	+We added a migration step, where we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false. Before, the error channel would be set to “errorChannel” only for the first inbound in an entry flow.
	59	+
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"]]
	64	+* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
61	61
62		-== **Key Takeaways** ==
	66	+== **Key takeaways** ==
63	63
64	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:
65	65
...	...	@@ -67,9 +67,10 @@
67	67	* If you have feedback or ideas for us, talk to the Platypus
68	68	* 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"]]
	74	+* 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
	77	+* 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		-)))
	85	+~*~* Indicates a next-generation-architecture only feature.
	86	+{{/info}})))((({{toc/}}))){{/container}}
86	86	{{/container}}
87		-{{/container}}