Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Content

...	...	@@ -4,32 +4,28 @@
4	4
5	5	**Hi there, eMagiz developers!** We have done much work to improve the functionality of our state generation solution so that you can have a better overview of its implementation in your environment. This overview covers a visibility towards the statistics for Retrieve Latency, Cache Size, Successful and Failed Retrieves. Next to the monitoring for the state generation implementation in your model, several feedback items revolving around user interfacing components in our platform that can improve the user experience are also released. Lastly, some performance improvements and bug fixes have also been implemented.
6	6
7		-{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
	7	+{{warning}}State generation functionality is only accessible for models with an add-on state generation license, and the monitoring for the state generation implementation can be found in the Manage phase, where you can find the Monitoring page.{{/warning}}
8	8
9	9	== **State Generation~*~*** ==
10	10
11	11	//__New Page__//
12	12	The following page has been added:
13		-* State generation statistics: Contains the statistics for state generation implementation in your model. This page can be found under Manage->Monitoring, right under the Topic statistics navigation menu. This page provides you with graphs that explains the Retrieve Latency, Cache Size, Successful and Failed Retrieves, which are coming from flows using state generation components. **Note** that this menu will only show for models that has the add-on license for state generation.
	13	+* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
14	14
15		-{{info}}The graphs are configured with the same behaviour as graphs in the other statistics pages, meaning that you can also change the time range, zoom in zoom out to the time frame, etc.{{/info}}
	15	+Added support for ... .
16	16
17		-== **Feedback Items** ==
	17	+{{info}}The components are ... .{{/info}}
18	18
19		-//__Improved Information on Removing a Release Version__//
20		-Users are now informed with a more comprehensive information of why removing a release version that is still active on all environments (i.e., Test, Acceptance, and Production) is failed. Users are now informed in which environment(s) that runs in which runtime(s) that the release version under deletion is still running.
	19	+== **Metrics Storage Duration** ==
	20	+We will ... .
21	21
22		-//__Wider and Expandable Fields for XPath Expressions__//
23		-Input fields for XPath expressions located in the Create phase are now made wider and also capable of expanding when the expression registered by the user is too long.
	22	+== **Feedback Items** ==
24	24
25		-//__Old Images Cleanup Mechanism__//
26		-We implemented a functionality that removes related unused images upon removal of a release version for on-premises machines. This prevents eMagiz to take resources of the customer’s machine due to the unattended old images.
	24	+//__Import from store__//
	25	+The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
27	27
28		-//__Consistent Toggle Switches__//
29		-We are now implementing eMagiz Design System module in our platform and, in this release, we updated all instances of the toggle switch to have a more consistent performance and look & feel.
30		-
31		-//__Search Phrase__//
32		-We are now enabling users to search for log entries and error messages based on phrases containing two or more words, instead of only one word or the full sentence. This also means that user can search for entries with distances of 2 or incomplete search phrase (e.g., “startin engine” to look for “starting servlet engine”).
	27	+//__Import from store__//
	28	+The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
33	33
34	34	== **Bug Fixes** ==
35	35