Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-187 - Integration Sponsor
	1	+204 - Found It

Content

...	...	@@ -2,64 +2,39 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** With this release we 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 that will enable you to restore your flow to a previous version.
	5	+**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
6	6
7		-== **Store - Next phase** ==
	7	+== **Feedback Items** ==
8	8
9		-This release will introduce the next phase of the Store to our whole community. With this new functionality you can now import data model messages (i.e. CDM, API Gateway Data model or Event Streaming data model) and transformations. This way connecting to standardized systems such as Exact Online, Microsoft Graph, Salesforce and others will become even easier.
	9	+//__Improved check on nested property placeholders__//
	10	+To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
10	10
11		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
	12	+//__Removed outdated properties when deploying on the new generation architecture stack__//
	13	+We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before in order to connect to a Kafka cluster but have become obsolete once you migrate.
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	+{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
14	14
15		-== **New eMagiz Mendix Connector** ==
	17	+//__Improved performance Manage Dashboards__//
	18	+We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
16	16
17		-With this release we introduce a new version of the eMagiz Mendix Connector. This version (6.0.0) will work both with the current runtime architecture and the new runtime architecture making the migration from the current runtime architecture to the new runtime architecture easier. The new version of the eMagiz Mendix Connector can be found in the Mendix Marketplace and in the eMagiz portal.
18		-
19		-{{info}}Migrating the runtime from the eMagiz portal works the same as for any other runtime. The migration path to migrate can be found [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-emagiz-runtime-generation-3.WebHome||target="blank"]]{{/info}}
20		-
21		-== **Flow version restore** ~* ==
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.
24		-
25		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
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}}
32		-
33		-== **Feedback items ** ==
34		-
35		-We have also solved other feedback items besides the flow designer's critical updates.
36		-
37		-//__Improved help texts Kafka component__//
38		-TBA
39		-
40		-//__Improved warning message when Message redelivery cannot be properly executed__//
41		-TBA
42		-
43		-//__See Flow Designer errors on the Create overview__//
44		-TBA
45		-
46	46	== **Bug Fixes** ==
47	47
48		-//__Update Swagger File when changing order of entities in gateway message__//
49		-TBA
	22	+//__Errors with long stack traces or long message histories will now also show in eMagiz__//
	23	+We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
50	50
	25	+//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
	26	+We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
	27	+
51	51	== **Fancy Forum Answers** ==
52	52
53	53	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:
54	54
55		-* [[Get files using a command via the SFTP protocol>>https://my.emagiz.com/p/question/172825635703184726||target="blank"]]
56		-* [[Take into account API rate limits>>https://my.emagiz.com/p/question/172825635703184597||target="blank"]]
57		-* [[Flow test stuck on initializing>>https://my.emagiz.com/p/question/172825635703184786||target="blank"]]
58		-* [[HTML to XML>>https://my.emagiz.com/p/question/172825635703197357||target="blank"]]
	32	+* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
	33	+* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
59	59
60	60	== **Key takeaways** ==
61	61
62		-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:
	37	+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:
63	63
64	64	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
65	65	* If you have feedback or ideas for us, talk to the Platypus
...	...	@@ -76,6 +76,6 @@
76	76	{{info}}
77	77	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78	78
79		-~*~* Indicates a GEN3-only feature.
	54	+~*~* Indicates a next-generation-architecture only feature.
80	80	{{/info}})))((({{toc/}}))){{/container}}
81	81	{{/container}}