Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-192 - Small Step
	1	+202 - New Equilibrium

Content

...	...	@@ -2,56 +2,68 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** In the last couple of weeks we worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have a new event streaming graph and some updates to our platform in general.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
6	6
7		-== **Start/Stop Flows** ~*~* ==
	7	+== **Release Properties** ==
	8	+As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your properties.
8	8
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}}
	10	+{{info}}For more information please check out the following microlearnings:
10	10
11		-To enhance the options you have 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 runtime level you can open the context menu and select the option called "Start/Stop Flows".
	12	+* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
	13	+* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
	14	+* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
12	12
13		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
	16	+Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	17	+{{/info}}
14	14
15		-After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start.
	19	+== ** Deploy Architecture - Apply To Environment improvements ** ==
	20	+As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
16	16
17		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
	22	+[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
18	18
19		-{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
	24	+== ** Breadcrumb navigation in eMagiz ** ==
	25	+This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
20	20
21		-== **Manage overview Event Streaming** ~*~* ==
	27	+[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
22	22
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 streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data.
	29	+== **Feedback Items** ==
24	24
25		-[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
	31	+//__Improved layout of catalog page in Design__//
	32	+We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations.
26	26
27		-== **Feedback items ** ==
	34	+//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
	35	+Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
28	28
29		-We have also solved other feedback items besides the flow designer's critical updates.
	37	+//__Additional help texts on Design Architecture__//
	38	+We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
30	30
31		-//__Topic configuration calculation__//
32		-With this release we have simplified the configuration of settings on topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics.
	40	+//__Improved Audit Trail on several places__//
	41	+In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
33	33
34		-//__Make preparation step in deployment plan visible__//
35		-For a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan.
	43	+//__Removed the erroneous alert on message mapping when having a passthrough API__//
	44	+This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
36	36
37		-{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
	46	+== **Bug Fixes** ==
38	38
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.
	48	+//__Avoid clicking on other components while deleting another__//
	49	+To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
41	41
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.
	51	+//__Improved validation feedback in migrating to the next-generation architecture__//
	52	+We have improved the validation feedback when migrating to the next-generation architecture.
44	44
45		-//__User Management synchronization now happens in one step__//
46		-With this release we have updated the synchronization process between Design and Deploy with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized.
	54	+//__Make sure that user credentials can be viewed with view rights__//
	55	+This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
47	47
	57	+//__Refresh behavior within the deployment plan is fixed__//
	58	+This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
	59	+
48	48	== **Fancy Forum Answers** ==
49	49
50	50	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:
51	51
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"]]
	64	+* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
	65	+* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
	66	+* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
55	55
56	56	== **Key takeaways** ==
57	57