Changes for page 212 - Failover Fiesta

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-189 - Private Eye
	1	+204 - Found It

Content

...	...	@@ -2,77 +2,39 @@
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!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
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	+== **Feedback Items** ==
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	+//__Improved check on nested property placeholders__//
	10	+To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
11	11
12		-== **3rd generation runtime bolstering** ==
	12	+//__Removed outdated properties when deploying on the new generation architecture stack__//
	13	+We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before connecting to a Kafka cluster but have become obsolete once you migrate.
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.
	15	+{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
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	+//__Improved performance Manage Dashboards__//
	18	+We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
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.
	20	+== **Bug Fixes** ==
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	+//__Errors with long stack traces or long message histories will now also show in eMagiz__//
	23	+We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
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}}
	25	+//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
	26	+We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
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.
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.
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.
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.
38		-
39		-== **Feedback items ** ==
40		-
41		-We have also solved other feedback items besides the flow designer's critical updates.
42		-
43		-//__Improved naming convention on Store related pages__//
44		-We have improved various display names using the merge functionality within our store offering.
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"]]
	32	+* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
	33	+* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
72	72
73	73	== **Key takeaways** ==
74	74
75		-Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	37	+Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
76	76
77	77	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78	78	* If you have feedback or ideas for us, talk to the Platypus
...	...	@@ -89,6 +89,6 @@
89	89	{{info}}
90	90	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91	91
92		-~*~* Indicates a GEN3-only feature.
	54	+~*~* Indicates a next-generation-architecture only feature.
93	93	{{/info}})))((({{toc/}}))){{/container}}
94	94	{{/container}}