Changes for page 190 - Fast Forward

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-189 - Private Eye
	1	+188 - Close Encounters

Content

...	...	@@ -2,71 +2,64 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
	5	+**Hi there, eMagiz developers!** This release is characterized mainly by our efforts to bolster our 3rd generation runtime and all the interactions with it. Furthermore, some small bug fixes and beta features will be released to the community.
6	6
7		-== **Private Store** ==
8		-On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
	7	+== **Store - Next phase** ==
9	9
10		-{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}}
	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.
11	11
12		-== **3rd generation runtime bolstering** ==
	11	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--current-store-offering.png]]
13	13
14		-This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
	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	15
16		-//__SOAP and REST web services migration including splitting them__//
17		-With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal.
	15	+== **New eMagiz Mendix Connector** ==
18	18
19		-//__Changing SSL settings for 3rd generation runtime models works__//
20		-As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime.
	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.
21	21
22		-//__Improved migration for JMS flows__//
23		-This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
	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}}
24	24
25		-{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}}
	21	+== **Flow version restore** ~* ==
26	26
27		-//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28		-As of this release, you cannot add debug components anymore on a flow that is already migrated to the 3rd generation runtime. This is because this functionality will not work in the 3rd generation runtime and would break your flow.
	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	29
30		-//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31		-We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
	25	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--flow-version-restore.png]]
32	32
	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	33	== **Feedback items ** ==
34	34
35	35	We have also solved other feedback items besides the flow designer's critical updates.
36	36
37		-//__Improved naming convention on Store related pages__//
38		-We have improved various display names to ensure that it is clear from the naming that store content can be implemented in all integration patterns.
	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.
39	39
40		-//__Press "Enter" to search on multiple pages__//
41		-In our Daemon Switch release, we added functionality that allowed you to press **Enter** to search on the property overview page. This release has added this functionality to many more pages across the portal. The complete list is as follows.
	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.
42	42
43		-* Deploy → Deployment Plan
44		-* Deploy → Properties → History
45		-* Deploy → User Management → Roles
46		-* Manage → Error Messages → Error Messages
47		-* Manage → Error Messages → Flows with Error Messages
48		-* Manage → Error Messages → Exceptions of Error Messages
49		-* Manage → Log Entries
50		-* Manage → Alerts
51		-* Manage → Triggers
52		-* Manage → Tags – Cant find (only Gen2)
53		-* Manage → Notifications
54		-* Manage → Notification Settings
55		-* Manage → Data Usage → History
56		-* Manage → Code mappings → All tabs
	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.
57	57
58		-== **Bug fixes ** ==
	46	+[[image:Main.Images.Release Blog.WebHome@187-release-blog--alert-visualized-in-create-overview.png]]
59	59
60		-//__Loading problems of Deployment plan execution overview__//
61		-We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases.
	48	+{{info}}Note that you need to open flows that are currently triggering alerts to show the alert on the Create overview{{/info}}
62	62
	50	+== **Bug Fixes** ==
	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	+
63	63	== **Fancy Forum Answers** ==
64	64
65	65	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:
66	66
67		-* [[Synchronous file pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]
68		-* [[Receiving e-mail via IMAP or POP3 - Set up>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]
69		-* [[Best way of Receiving and Sending Mail>>https://my.emagiz.com/p/question/172825635703210149||target="blank"]]
	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"]]
70	70
71	71	== **Key takeaways** ==
72	72