Changes for page 206 - Situational Deployment

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-201 - Be Informed
	1	+189 - Private Eye

Content

...	...	@@ -2,59 +2,73 @@
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 few weeks, we have worked hard on planning the upcoming Q and finishing up features of the previous Q. More on that later. On top of that, we have several smaller items as a result of our hackathon efforts to present to you.
	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.
6	6
7		-== **Announcement - Release Properties** ==
8		-As of the next release (202), we will introduce a new way of handling properties for all our clients. In the upcoming weeks, we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	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).
9	9
10		-== ** Deploy Architecture - Apply To Environment improvements ** ==
11		-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.
	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}}
12	12
13		-[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
	12	+== **3rd generation runtime bolstering** ==
14	14
15		-== ** Breadcrumb navigation in eMagiz ** ==
16		-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.
	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.
17	17
18		-[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
	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. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
19	19
20		-== **Feedback Items** ==
	19	+//__Changing SSL settings for 3rd generation runtime models works__//
	20	+As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
21	21
22		-//__Improved layout of catalog page in Design__//
23		-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.
	22	+//__Improved migration for JMS flows__//
	23	+This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
24	24
25		-//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
26		-Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
	25	+{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
27	27
28		-//__Additional help texts on Design Architecture__//
29		-We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
	27	+//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
	28	+As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
30	30
31		-//__Improved Audit Trail on several places__//
32		-In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
	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.
33	33
34		-//__Removed the erroneous alert on message mapping when having a passthrough API__//
35		-This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
	33	+//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
	34	+With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
36	36
37		-== **Bug Fixes** ==
	36	+//__Added "Reset" functionality__//
	37	+With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
38	38
39		-//__Avoid clicking on other components while deleting another__//
40		-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.
	39	+== **Feedback items ** ==
41	41
42		-//__Improved validation feedback in migrating to the next-generation architecture__//
43		-We have improved the validation feedback when migrating to the next-generation architecture.
	41	+We have also solved other feedback items besides the flow designer's critical updates.
44	44
45		-//__Make sure that user credentials can be viewed with view rights__//
46		-This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
	43	+//__Improved naming convention on Store related pages__//
	44	+We have improved various display names using the merge functionality within our store offering.
47	47
48		-//__Refresh behavior within the deployment plan is fixed__//
49		-This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
	46	+//__Update security protocols for our internal architecture__//
	47	+Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
50	50
	49	+//__Improved read-only description for "if exists" constructions in Transformations__//
	50	+To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
	51	+
	52	+
	53	+== **Bug fixes ** ==
	54	+
	55	+//__Decent validation feedback when not filling in the property value__//
	56	+We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
	57	+
	58	+//__Incorrect resource locations__//
	59	+We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
	60	+
	61	+//__Apply to environment in User Management performance improvement__//
	62	+We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
	63	+
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		-* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
56		-* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
57		-* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
	68	+* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
	69	+* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
	70	+* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
	71	+* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||target="blank"]]
58	58
59	59	== **Key takeaways** ==
60	60