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,56 +2,71 @@
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 last 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 completely 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 contact 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 change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together 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		-//__Enhanced right-hand view within Deployment Plan context__//
14		-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.
	12	+== **3rd generation runtime bolstering** ==
15	15
16		-{{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}}
	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		-//__Improved timeout settings when deploying__//
19		-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.
	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.
20	20
21		-{{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}}
	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.
22	22
23		-//__Detailed HTTP Statistics now show user info in specific additional cases__//
24		-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.
	22	+//__Improved migration for JMS flows__//
	23	+This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
25	25
26		-{{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}}
	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}}
27	27
28		-//__Improved loading speed of Manage Dashboard__//
29		-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.
	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.
30	30
31		-== **Store Improvements** ==
	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.
32	32
33		-//__Importing in Design is improved__//
34		-We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
	33	+== **Feedback items ** ==
35	35
36		-== **Bug Fixes** ==
	35	+We have also solved other feedback items besides the flow designer's critical updates.
37	37
38		-//__Deprecated reminder pop-up removed__//
39		-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.
	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.
40	40
41		-//__Improved selection area in Flow Designer__//
42		-When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
	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.
43	43
44		-//__Improved Kafka settings__//
45		-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.
	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
46	46
47		-{{info}}We strongly 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}}
	58	+== **Bug fixes ** ==
48	48
	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.
	62	+
49	49	== **Fancy Forum Answers** ==
50	50
51	51	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:
52	52
53		-* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
54		-* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
	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"]]
55	55
56	56	== **Key takeaways** ==
57	57