Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Content

...	...	@@ -2,7 +2,7 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
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. 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.
	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. 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	7	{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
8	8
...	...	@@ -9,7 +9,7 @@
9	9	== **State Generation - Manage overview** ==
10	10
11	11	The following page has been added:
12		-* State generation statistics: Contains the statistics for state generation implementation in your model. The navigation to this page can be found under Manage->Monitoring page. 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.
	12	+* State generation statistics: Contains the statistics for state generation implementation in your model. The navigation to this page can be found under Manage->Monitoring page. This page provides you with graphs that explain the retrieve latency, cache size, and successful and failed retrieves, which are coming from flows using state generation components. **Note** that this menu will only show for models that have the add-on license for state generation.
13	13
14	14	[[image:Main.Images.Release Blog.WebHome@208-release-blog-1.jpg]]
15	15
...	...	@@ -16,36 +16,36 @@
16	16	== **Feedback Items** ==
17	17
18	18	//__Improved information on removing a release version__//
19		-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	+Users are now informed with more comprehensive information about why removing a release version that is still active on all environments (i.e., Test, Acceptance, and Production) fails. Users are now informed in which environment(s) and in which runtime(s) that the release version under deletion is still running.
20	20
21	21	//__Wider and expandable fields for XPath expressions__//
22	22	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.
23	23
24	24	//__Old images cleanup mechanism__//
25		-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.
	25	+We implemented a functionality that removes related unused images upon removal of a release version for on-premises machines. This prevents eMagiz from taking resources from the customer’s machine due to the unattended old images.
26	26
27	27	//__Consistent toggle switches__//
28	28	In this release, we have updated all instances of the toggle switch to have a more consistent performance and look & feel throughout the platform.
29	29
30	30	//__Search phrase__//
31		-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”).
	31	+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 the user can search for entries with distances of 2 or incomplete search phrases (e.g., “startin engine” to look for “starting servlet engine”).
32	32
33	33	//__Improved image building performance__//
34		-We have implemented an improvement on the preparing step of the release at the begining of the deployment, which leads to a faster deployment process.
	34	+We have implemented an improvement on the preparation step of the release at the beginning of the deployment, which leads to a faster deployment process.
35	35
36	36	//__Default "errorChannel" on next-generation architecture migration__//
37		-During a migration of a model to the next-generation architecture, we have introduced a check now for flows that did not have custom error handling to be set their error channel to "errorChannel" after the migration if the custom error handling is set to false.
	37	+During a migration of a model to the next-generation architecture, we have introduced a check now for flows that did not have custom error handling to set their error channel to "errorChannel" after the migration if the custom error handling is set to false.
38	38
39	39	== **Bug Fixes** ==
40	40
41	41	//__Incorrect deployed containers__//
42		-A fix has been implemented to address the issue where older containers were deployed while it was shown that the new ones instead are deployed. This problem was caused by auto-healing that triggered during a new deployment.
	42	+A fix has been implemented to address the issue where older containers were deployed while it was shown that the new ones were deployed. This problem was caused by auto-healing that was triggered during a new deployment.
43	43
44	44	//__Log messages in next-generation architecture models__//
45		-We have implemented an improvement in our infra components that is intended to reduce the occurance of log messages failed to be sent in the next-generation architecture models.
	45	+We have implemented an improvement in our infra components that is intended to reduce the occurrence of log messages failing to be sent in the next-generation architecture models.
46	46
47	47	//__Random stuck in deployment plan execution__//
48		-We addressed an issue where the execution of deployment plan would occasionally become stuck or halted unexpectedly.
	48	+We addressed an issue where the execution of the deployment plan would occasionally become stuck or halted unexpectedly.
49	49
50	50	== **Fancy Forum Answers** ==
51	51
...	...	@@ -52,7 +52,7 @@
52	52	As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
53	53
54	54	* [[(Very) large messages via eMagiz>>https://my.emagiz.com/p/question/172825635703645419||target="blank"]]
55		-* [[Existing integration sends message to onramp but they dissapear before it reaches the routing>>https://my.emagiz.com/p/question/172825635703658192||target="blank"]]
	55	+* [[Existing integration sends message to onramp but they disappear before it reaches the routing>>https://my.emagiz.com/p/question/172825635703658192||target="blank"]]
56	56
57	57	== **Key takeaways** ==
58	58