Changes for page 225 - Pop-up Party

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-222 - Flee Frustration
	1	+198 - Great Migration

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.CarlijnKokkeler
	1	+XWiki.ebakker

Content

...	...	@@ -1,17 +1,23 @@
1		-In the last sprint cycle, we done several improvements for the Design and Deploy phases. Moreover, we have improved the Event Catalog overview for Catalog users. Our bug fixes concern the import of xsds, the deletion behaviour of containerse, and the generation of scope properties.
	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.222 - Flee Frustration||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		-====New features====
6		-* Design - Architecture: If a user makes changes in Design that will create or delete runtimes, or impact your model architecture, that user will be warned about this before it is put into effect in Design Architecture.
7		-* Create - Properties: Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
	5	+=====Minor changes=====
8	8
	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: When pressing "Apply to Environment" in Deploy -> Architecture there is no hard dependencies anymore on the (active) release when running in the next generation architecture. This makes it more clear and tangible what function is necessary for what goal.
	13	+* Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
	14	+* General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
	15	+
9	9	====Bug fixes====
10		-* Design - Architecture: The number on the JMS container correctly displays the amount of queues present in Design. (#1284)
11		-* Create - Flow Designer: Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. (#1053)
12		-* Deploy - Architecture: We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. (#1282)
13		-* Deploy - Deployment plan: Users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. (#1293)
14		-* Deploy - Releases: Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. (#1293)
15	15
	18	+* 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.
	19	+* 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.
16	16
	21	+====Remarks====
17	17
	23	+* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.