Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-187 - Integration Sponsor
	1	+209 - Max Verstappen

Author

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

Content

...	...	@@ -2,72 +2,79 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** This release will release several impactful features and enablers to our community. Among others, the next phase of the eMagiz Store will become publicly available. This means that you can now import data models and transformation on top of system messages in Design and accelerators in Create. Furthermore, we will launch a new Beta functionality through some of our clients, enabling you to restore your flow to a previous version.
	5	+**Hi there, eMagiz developers!** We have done .....
6	6
7		-== **Store - Next phase** ==
	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
	8	+6:00 AM UTC instead 5:00 AM UTC. {{/warning}}
8	8
9		-This release will introduce the next phase of the Store to our whole community. With this new functionality, you can import data model messages (i.e., CDM, API Gateway Data model, or Event Streaming data model) and transformations. Connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce, and others will become even more accessible.
	10	+== **Next Generation Architecture Default** ==
	11	+With this release, the next generation architecture will become the default. New models will use this generation as default.
10	10
11		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
	13	+[[image:Main.Images.Release Blog.WebHome@release-blog-next-gen-default.png]]
12	12
13		-{{info}}For more information on the Store please check out this [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.WebHome||target="blank"]]. As a reminder, you can find all documentation on all available Store content published by eMagiz [[here>>doc:Main.eMagiz Store.WebHome||target="blank"]].{{/info}}
	15	+== **Cloud Template R11 - Single Lane** ==
	16	+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
14	14
15		-== **New eMagiz Mendix Connector** ==
	18	+== **Cloud Template R13 - Double Lane** ==
16	16
17		-This release introduces a new version of the eMagiz Mendix Connector. This version (6.0.0) will work with the current runtime architecture and the new runtime architecture making the migration from the existing runtime architecture to the new runtime architecture easier. The latest version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and the eMagiz portal.
18	18
19		-{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
	21	+== **Feedback Items** ==
20	20
21		-== **Flow version restore** ~* ==
	23	+//__Unused properties overview__//
	24	+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:
	25	+* Not used by any runtime that is in the Create phase release.
	26	+* Not required by a flow that is in the Create phase release.
	27	+* If used as nested property, none of its parent properties (checks recursively) are in the Create phase release.
22	22
23		-On top of that, we will also launch a new Beta feature to the community that allows you to restore your flow to a previous version. This way, you can quickly undo changes made that were incorrect.
	29	+//__Send build requests asynchronously__//
	30	+The step in the deployment plan concerning the preparation of runtime images will now be executed more quickly and reliably.
24	24
25		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
	32	+//__Queue explorer milliseconds__//
	33	+The queue browser now displays milliseconds in the timestamps.
26	26
27		-{{warning}}Note that the following restrictions apply when restoring to a previous version:
28		- * Changes made on definition and transformation level are **not** restored
29		- * You will **not** be able to restore to any flow version that was created before October 17th, 2022
30		- * 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
31		- * Your restored flow version will **not** be automatically committed to Deploy{{/warning}}
	35	+//__Cancel and next buttons order__//
	36	+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.
32	32
33		-== **Feedback items ** ==
	38	+//__Unused images__//
	39	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
34	34
35		-We have also solved other feedback items besides the flow designer's critical updates.
	41	+//__Carwash logging__//
	42	+A new logging feature enabling us to make better choices in encryption standards will be released.
36	36
37		-//__Improved help texts Kafka component__//
38		-The help texts on various configuration options and the general help text on multiple Kafka components have been updated to clarify how they work and how you ought to configure them to achieve the best possible result when sending and receiving messages to and from topics within eMagiz.
	44	+//__Static alerts queue consumers__//
	45	+Alerting will now only generate alerts for queues that are created and managed by the eMagiz JMS server.
39	39
40		-//__Improved warning message when Message redelivery cannot be adequately executed__//
41		-We have improved the warning you get when you cannot retrieve the messages waiting to be redelivered. This helps clarify what is going wrong when a user sees this warning.
	47	+== **Bug Fixes** ==
42	42
43		-//__See Flow Designer errors on the Create overview__//
44		-To improve our offering surrounding the new Flow Designer functionality, we now show on the Create overview which of the flows you still have alerts due to a misconfiguration of the flow. This will help to identify ongoing work much more manageable.
	49	+//__Images rebuild__//
	50	+We fixed an issue which caused the release preparation step to take longer time than necessary and caused the machine deployment steps to execute when they could be skipped.
45	45
46		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
	52	+//__Flow Designer connection line__//
	53	+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.
47	47
48		-{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
	55	+//__Portal for migrated models__//
	56	+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.
49	49
50		-== **Bug Fixes** ==
	58	+//__Error channel inbounds__//
	59	+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.
51	51
52		-//__Update Swagger File when changing the order of entities in gateway message__//
53		-In our previous release, we improved how the Swagger file is generated when changing the order of attributes of your gateway message. To make this functionality work for entities, we have made several additional changes to the platform supporting this.
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		-* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
60		-* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
61		-* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
62		-* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
	65	+* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
	66	+* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
	67	+* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
	68	+* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
63	63
	70	+
64	64	== **Key takeaways** ==
65	65
66		-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:
	73	+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	67
68	68	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
69	69	* If you have feedback or ideas for us, talk to the Platypus
70		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	77	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
71	71	* Clear your browser cache (Ctrl + Shift + Del)
72	72	* Check out the release notes [here]
73	73	* Start thinking about how the license tracker can aid your development
...	...	@@ -80,6 +80,6 @@
80	80	{{info}}
81	81	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
82	82
83		-~*~* Indicates a GEN3-only feature.
	90	+~*~* Indicates a next-generation-architecture only feature.
84	84	{{/info}})))((({{toc/}}))){{/container}}
85	85	{{/container}}