Changes for page 270 - Round Round

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-198 - Great Migration
	1	+269 - Additional Acceleration

Content

...	...	@@ -1,24 +1,12 @@
1		-Another couple of weeks have passed, so it is time for a new release. We have focused in this period on improving the migration process towards the next-generation architecture as well as how the user experience and interaction with the next-generation architecture works.
	1	+This release includes additional accelerans for all integration developers out there. This includes improvements in the flow designer navigation and the missing properties functionality. Subsequently, we introduced a fix to improve the stability of our flow designer. Enjoy reading our latest updates on the platform.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
	3	+Please find out more on our [[Release blog>>doc:Main.Release Information.Release Blogs.269 - Additional Acceleration.WebHome||target="blank"]].
4	4
5		-=====Minor changes=====
	5	+==== Minor Changes ====
6	6
7		-* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
8		-* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
9		-* Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
10		-* Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
11		-* Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
12		-* Deploy - Architecture: You can apply your changes to environment without having an active release.
13		-* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
14		-(control tower, so Gen3 only)
15		-* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
	7	+* Create - Flow Designer: When part of an integration is opened for the first time, the entire flow is generated as initial version so that the user can navigate to the previous and next flow using the inbound and outbound components. (#1660)
	8	+* Deploy - Release - Missing Properties: To improve overall performance we update the missing properties list in such a way that we do not need to recalculate the full list every time a user makes a change in the list. Furthermore, various UI/UX improvements have been made throughout the process to optimize the user process. (#1796)
16	16
17		-====Bug fixes====
	10	+==== Bug fixes ====
18	18
19		-* General: Increased the performance of the eMagiz Control Tower, which should significantly reduce the occurence of the 'failed to send to elastic' log message in your models.
20		-* Deploy - Architecture: The docker commands now correctly propagate to the java process, making sure containers stop, start and restart as intended when running runtimes in a hybrid situation. Please check out the runtime [[release notes>>Main.Release Information.Runtime Images.WebHome||target="blank"]] for additional information.
21		-
22		-====Remarks====
23		-
24		-* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.
	12	+* Create - Flow Designer: A fix has been implemented to resolve an issue where an error popup would occasionally appear when opening the Flow Designer. (#1644)