Changes for page 216 - Hack Heaven

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-190 - Fast Forward
	1	+198 - Great Migration

Content

...	...	@@ -1,32 +1,27 @@
1		-The release finishes up a lot of new improvements to our 3rd generation runtime offering and fixed a variety of annoying bugs and some minor enhancements. Furthermore, we introduce several improvements in the interaction with the portal.
	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.
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.190 - Fast Forward.WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.198 - Great Migration.WebHome||target= "blank"]].
4	4
5	5	=====New features=====
6		-* A new runtime image for customer models running on the 3rd generation runtime. Please find out more on our [[Runtime Image release notes>>Main.Release Information.Runtime Images.V110.WebHome||target="blank"]].
7		-* Manage - Explore: The Queue browser is a new feature that enables you to explore the queues on your jms-server and view (and delete) the message on them. It is only available if you migrated your JMS server to the 3rd generation runtime.
8	8
9		-=====Major changes=====
10	10
11		-* Manage - Redelivery: You are able to explore the message redelivery functionality for the 3rd generation architecture and see more details about it. Beside that, you are also able to redeliver the message(s) in this page.
12		-
13	13	=====Minor changes=====
14	14
15		-* Design - System message: 'Request' and 'Response' entities are generated and set as root entities automatically for new SOAP web service integrations in 3rd generation runtimes.
16		-* Create - Flow designer: sensitive information stored in property values is masked. (#790)
17		-* Create - Flow Designer: when migrated from Gen2 to Gen3, the flow's JSON will be generated so user can use it to compare with the previous versions.
18		-* Create - Flow Designer: when importing store item from another partner, a error popup will be shown instead of default error message.
19		-* Deploy - Releases: The activate release functionality gained a performance improvement for gen 3 models.
20		-* Deploy - Architecture: Before apply to environment, we require a confirmation from you if those are some breaking changes that may cause issues in AWS. (#828)
21		-* Deploy - Architecture: We enabled setting memory limits for eMagiz runtimes running on Docker machines. (#571)
22		-* Deploy - Architecture: "HTTP settings" page changed to "Runtime settings", where you can enable/disable both HTTP and control bus per runtime.
23		-* Deploy - Releases - When activating a release you will be reminded of empty runtimes. Empty runtimes are runtimes without flows in the release. These runtimes should be removed from your architecture.
	10	+* Create - 3rd generation runtime migration: You will be notified by a pop-up when the migration is complete.
	11	+* Create - 3rd generation migration: Migrating a JMS server to the 3rd generation runtime will migrate backup JMS servers too.
	12	+* 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.
	13	+* 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.
	14	+* 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.
	15	+* Deploy - Architecture: You can apply your changes to environment without having an active release.
	16	+* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
	17	+(control tower, so Gen3 only)
	18	+* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
24	24
25	25	====Bug fixes====
26		-* Design-CDM: cannot break definition when setting cardinality to '*' if the parent entity has order matters set to 'No' (#508)
27		-* Create - Flow Designer: When copy and paste, support objects such as "property placeholder", "support.bus-connection-caching" and "support.bus-connection-plain" are not duplicated (#793)
28		-* Create - Flow Designer: when importing a store item, it is possible to overwrite the value of properties in setup step.
29		-* Deploy - Containers: We fix an issue that the container overview does not show the entry flows which should run on that container. (#863)
30		-* Deploy - Architecture: Apply to environment button synchronizes event streaming topic states correctly. (#814)
31		-* Deploy - Architecture: The deploy runtimes option is only visible for admin. New menu item "Deploy agent" is added and visible for all users to show the command which can be uses to deploy agent on premises machine.
32	32
	22	+* 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.
	23	+* 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.
	24	+
	25	+====Remarks====
	26	+
	27	+* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.