Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-198 - Great Migration
	1	+203 - Fast Paced

Content

...	...	@@ -2,39 +2,32 @@
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 improving the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
6	6
7		-== **3rd generation improvements and bug fixes** ==
	7	+== **Release Properties - Early Feedback** ==
	8	+The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
8	8
9		-//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10		-Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.
	10	+== **Feedback Items** ==
11	11
12		-{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
	12	+//__"All entries" are now cleaned up as part of the migration__//
	13	+To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
13	13
14		-//__Improved efficiency in deploying a release__//
15		-This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
	15	+//__Trigger ID added to our alerting on the next-generation architecture__//
	16	+We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
16	16
17		-//__Removed specific dependencies between Deploy Architecture and Releases__//
18		-In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
	18	+== **Bug Fixes** ==
19	19
20		-//__Improved validation errors on the invalid configuration of HTTP outbound components__//
21		-This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
	20	+//__Ensure no flow can be in a release twice__//
	21	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
22	22
23		-//__Improved migration behavior__//
24		-This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
25		-A smoother migration of your JMS (and backup JMS) process.
26		-Shortening of names that otherwise would be too long, additional feedback given to the user.
27		-Feedback when the migration process is finished.
	23	+//__Ensure no flow can be in a release twice__//
	24	+We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
28	28
29		-//__Additional checks when deploying__//
30		-This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
31		-
32	32	== **Fancy Forum Answers** ==
33	33
34	34	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:
35	35
36		-* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
37		-* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
	30	+* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
38	38
39	39	== **Key takeaways** ==
40	40
...	...	@@ -55,6 +55,6 @@
55	55	{{info}}
56	56	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57	57
58		-~*~* Indicates a GEN3-only feature.
	51	+~*~* Indicates a next-generation-architecture only feature.
59	59	{{/info}})))((({{toc/}}))){{/container}}
60	60	{{/container}}