Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-207 - Aligned State
	1	+208 - Controlled State

Author

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

Content

...	...	@@ -1,27 +1,23 @@
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	+In the last sprint cycle, we focused on providing users with a monitoring functionality for the state generation components. On top of that, we also made several improvements to the components interfacing the users to improve the user experience aspect of our platform. Moreover, we made some bug fixes and improvements on releases in Deploy and monitoring in Manage.
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.208 - Controlled State .WebHome||target="blank"]].
4	4
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		-* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
10		-* 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)
11		-* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
12		-* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
13		-* Manage - Data Sink: Data sink page has been moved to the “Explore” tab. (#946)
14		-* 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.
15		-* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
16		-* 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)
	7	+* Create - Flow Designer: Input fields for XPath expressions have been made wider and capable of expanding to facilitate longer inputs. (#822)
	8	+* Create - Flow Designer: Small styling changes and bug fixes have been implemented for edge cases during editing channels in the Flow Designer.
	9	+* Deploy - Releases: During removing a release, users will be informed about the environments and the runtimes in which the release under deletion is running. (#1060)
	10	+* Deploy - Releases: When a release is removed, the related unused images in the on-premises machines will be removed as well.
	11	+* Deploy - Deployment: The “preparing” step of the release at the beginning of the deployment is now faster due to the improved process of building the images.
	12	+* Manage - Monitoring: There is a new page called "State generation statistics" that is located right under the Topic statistics navigation menu, which is only shown and accessible for models that have the add-on license for state generation.
	13	+* Manage - Error messages & Log entries: Searching on entries in the next-generation architecture models now supports phrase matching, meaning that users can search entries based on phrases containing two or more words and entries with distances of 2 or incomplete search phrases.
	14	+* Manage - Alerting: In Alerts, the previous "Source" column is renamed to "Source trigger" and its value is derived from the type of trigger which generates alert.
	15	+* All - Toggles: We updated all instances of the toggle switch in the platform due to the latest eMagiz Design System module implementation in our platform.
	16	+* All - Error Channel: Added a migration step in Gen3 migration, we set the error channel to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
17	17
18	18	====Bug fixes====
19	19
20		-* 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)
21		-* Manage - Triggers: Besides checking error header, the error trigger is configured to check if an error message contains a term.
	20	+* Deploy - Deployment: We fixed an issue that the deployment plan got stuck or stopped randomly sometimes.
	21	+* Deploy - Deployment: We resolved an issue where sometimes older containers get deployed, while eMagiz shows the new containers are deployed.
	22	+* Manage - Monitoring: Improved message processing in infra components that should reduce the occurrence of log messages failing to be sent in Gen3 models.
22	22
23		-
24		-
25		-=====Infra and image changes=====
26		-
27		-* 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.