Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-189 - Private Eye
	1	+200 - Uncharted Territories

Content

...	...	@@ -2,73 +2,52 @@
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 few weeks, we have worked hard on a lot of things that are unfortanetly not quite ready to be released. As a result the ouput of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
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	+== **Next generation improvements and bug fixes** ==
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	+//__Enhanced right-hand view within Deployment Plan context__//
	10	+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.
11	11
12		-== **3rd generation runtime bolstering** ==
	12	+{{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}}
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.
	14	+//__Improved timeout settings when deploying__//
	15	+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.
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. 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.
	17	+{{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}}
18	18
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.
	19	+//__Detailed HTTP Statistics now show user info in specific additional cases__//
	20	+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.
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.
	22	+{{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}}
24	24
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}}
	24	+//__Improved loading speed of Manage Dashboard__//
	25	+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.
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 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.
	27	+== **Store Improvements** ==
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.
	29	+//__Importing in Design is improved__//
	30	+We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
32	32
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.
	32	+== **Bug Fixes** ==
35	35
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.
	34	+//__Deprecated reminder pop-up removed__//
	35	+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.
38	38
39		-== **Feedback items ** ==
	37	+//__Improved selection area in Flow Designer__//
	38	+When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow.
40	40
41		-We have also solved other feedback items besides the flow designer's critical updates.
	40	+//__Improved Kafka settings_//
	41	+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.
42	42
43		-//__Improved naming convention on Store related pages__//
44		-We have improved various display names using the merge functionality within our store offering.
	43	+{{info}}We stronly 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}}
45	45
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.
48		-
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		-
64	64	== **Fancy Forum Answers** ==
65	65
66	66	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:
67	67
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"]]
	49	+* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
	50	+* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
72	72
73	73	== **Key takeaways** ==
74	74