Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-187 - Integration Sponsor
	1	+200 - Uncharted Territories

Content

...	...	@@ -2,60 +2,52 @@
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!** In the last few weeks, we have worked hard on a lot of things that are unfortanetly not quite ready to be released. As a result the ouput of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
6	6
7		-== **Store - Next phase** ==
	7	+== **Next generation improvements and bug fixes** ==
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	+//__Enhanced right-hand view within Deployment Plan context__//
	10	+When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
10	10
11		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
	12	+{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
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}}
	14	+//__Improved timeout settings when deploying__//
	15	+To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
14	14
15		-== **New eMagiz Mendix Connector** ==
	17	+{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
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.
	19	+//__Detailed HTTP Statistics now show user info in specific additional cases__//
	20	+To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
18	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}}
	22	+{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
20	20
21		-== **Flow version restore** ~* ==
	24	+//__Improved loading speed of Manage Dashboard__//
	25	+This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
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.
	27	+== **Store Improvements** ==
24	24
25		-[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
	29	+//__Importing in Design is improved__//
	30	+We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
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}}
	32	+== **Bug Fixes** ==
32	32
33		-== **Feedback items ** ==
	34	+//__Deprecated reminder pop-up removed__//
	35	+We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
34	34
35		-We have also solved other feedback items besides the flow designer's critical updates.
	37	+//__Improved selection area in Flow Designer__//
	38	+When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow.
36	36
37		-//__Improved help texts Kafka component__//
38		-TBA
	40	+//__Improved Kafka settings_//
	41	+For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
39	39
40		-//__Improved warning message when Message redelivery cannot be properly executed__//
41		-TBA
	43	+{{info}}We stronly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
42	42
43		-//__See Flow Designer errors on the Create overview__//
44		-TBA
45		-
46		-== **Bug Fixes** ==
47		-
48		-//__Update Swagger File when changing order of entities in gateway message__//
49		-TBA
50		-
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"]]
	49	+* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
	50	+* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
59	59
60	60	== **Key takeaways** ==
61	61