Changes for page 206 - Situational Deployment

Summary

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

Details

Page properties

Title

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

Content

...	...	@@ -2,39 +2,75 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
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.
	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		-== **Feedback Items** ==
	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).
8	8
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.
	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}}
11	11
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.
	12	+== **3rd generation runtime bolstering** ==
14	14
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}}
	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.
16	16
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.
	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.
19	19
20		-== **Bug Fixes** ==
	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.
21	21
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).
	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		-//__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.
	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
	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.
	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	+== **Feedback items ** ==
	34	+
	35	+We have also solved other feedback items besides the flow designer's critical updates.
	36	+
	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.
	39	+
	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.
	42	+
	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
	57	+
	58	+== **Bug fixes ** ==
	59	+
	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	+
28	28	== **Fancy Forum Answers** ==
29	29
30	30	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:
31	31
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"]]
	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"]]
34	34
35	35	== **Key takeaways** ==
36	36
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:
	73	+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:
38	38
39	39	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
40	40	* If you have feedback or ideas for us, talk to the Platypus
...	...	@@ -51,6 +51,6 @@
51	51	{{info}}
52	52	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
53	53
54		-~*~* Indicates a next-generation-architecture only feature.
	90	+~*~* Indicates a GEN3-only feature.
55	55	{{/info}})))((({{toc/}}))){{/container}}
56	56	{{/container}}