Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-207 - Aligned State
	1	+198 - Great Migration

Author

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

Content

...	...	@@ -1,29 +1,27 @@
1		-In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
	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.207 - Aligned State .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	+=====New features=====
	6	+
	7	+
5	5	=====Minor changes=====
6	6
7		-* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8		-* Design - Performance: Performance improvements for the Flow Designer have been implemented.
9		-Create-Flowdesigner] When importing items from the store, flowfragments that are hidden in design will be listed under the versions in create.
10		-* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
11		-* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
12		-* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
13		-* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
14		-* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
15		-* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946)
16		-* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
17		-* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
18		-* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
	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.
19	19
20	20	====Bug fixes====
21	21
22		-* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
23		-* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
	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	24
	25	+====Remarks====
25	25
26		-
27		-=====Infra and image changes=====
28		-
29		-* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
	27	+* Infrastructure Upgrade: We have updated the underlying version of one of our applications to 9.24.2.