Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-204 - Found It
	1	+201 - Be Informed

Content

...	...	@@ -2,39 +2,60 @@
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!** 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.
6	6
7		-== **Feedback Items** ==
	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]].
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	+== ** 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.
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 in order to connect to a Kafka cluster but have become obsolete once you migrate.
	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.
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}}
	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}}
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.
	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.
19	19
	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}}
	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.
	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}}
	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.
	30	+
	31	+== **Store Improvements** ==
	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.
	35	+
20	20	== **Bug Fixes** ==
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).
	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.
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.
	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.
27	27
	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.
	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}}
	48	+
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"]]
	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"]]
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:
	58	+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.
	75	+~*~* Indicates a GEN3-only feature.
55	55	{{/info}})))((({{toc/}}))){{/container}}
56	56	{{/container}}