Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-189 - Private Eye
	1	+192 - Small Step

Content

...	...	@@ -2,71 +2,56 @@
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!** In the last couple of weeks, we worked hard on building several essential things that will be released later this Q. On top of that, we finished additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the other features, we have a new event streaming graph and general updates to our platform.
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	+== **Start/Stop Flows** ~*~* ==
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	+{{warning}}Note that depending on the alert, this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
11	11
12		-== **3rd generation runtime bolstering** ==
	11	+To enhance your options when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows." You can access this functionality via the "Deploy Architecture" overview in Deploy. On the runtime level, you can open the context menu and select the "Start/Stop Flows" option.
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	+[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
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	+After selecting the option, eMagiz will open a pop-up where you can stop and start the starting point of each flow deployed on that runtime. This effect is that the flow will process no new messages, but the flow will still process all remaining messages after stopping the flow. To prevent a flow, you select a flow and press the Stop button. To start it again, press Start.
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	+[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
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}}Only in "Start Editing" mode can you start and stop specific flows{{/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	+== **Manage overview Event Streaming** ~*~* ==
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	+To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaming statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, you can see metadata information on all your topics by clicking on the "Event streaming statistics" overview. Among others, you can see whether data is consumed, on which topic much data is produced, and whether consumers are lagging in consuming data.
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@192-release-blog--event-streaming-overview-manage.png]]
32	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.
	31	+//__Topic configuration calculation__//
	32	+With this release, we have simplified the configuration of settings on the topic level to enforce certain best practices within the portal and simultaneously make it easier to configure topics.
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.
	34	+//__Make preparation step in deployment plan visible__//
	35	+For deployment on the 3rd generation runtime to work, the portal needs some preparation work. We have now made this step explicit and part of the deployment plan.
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
	37	+{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
57	57
58		-== **Bug fixes ** ==
	39	+//__3rd generation runtime debugger feedback__//
	40	+We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
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.
	42	+//__No "Shift key" needed anymore to select multiple items in the flow designer__//
	43	+As of now, you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
62	62
	45	+//__User Management synchronization now happens in one step__//
	46	+With this release, we have updated the synchronization process between Design and Deploy concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized.
	47	+
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"]]
	52	+* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
	53	+* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
	54	+* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
70	70
71	71	== **Key takeaways** ==
72	72