Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-199 - Home Improvements
	1	+208 - Controlled State

Author

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

Content

...	...	@@ -2,51 +2,68 @@
2	2	{{container layoutStyle="columns"}}(((
3	3	[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4	4
5		-**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
	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		-== **Next generation improvements and bug fixes** ==
	7	+{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
8	8
9		-//__Enhanced overview of the HTTP Statistics__//
10		-As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
	9	+== **State Generation - Manage overview~*~*** ==
11	11
12		-//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13		-In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
	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 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.
14	14
15		-{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	14	+[[image:Main.Images.Release Blog.WebHome@208-release-blog-1.jpg]]
16	16
17		-//__Forced congestion control__//
18		-To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
	16	+== **Feedback Items** ==
19	19
20		-//__Unused images are cleaned up__//
21		-This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan.
	18	+//__Improved information on removing a release version__//
	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.
22	22
23		-== **Store Improvements** ==
	21	+//__Wider and expandable fields for XPath expressions__//
	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.
24	24
25		-//__Improved importing behavior for specific use cases__//
26		-Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
	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 from taking resources from the customer’s machine due to the unattended old images.
27	27
28		-//__Fixed bug in creating a message mapping on top of an imported system message__//
29		-It is now possbile to create a message mapping to an imported system message from the store.
	27	+//__Consistent toggle switches__//
	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.
30	30
31		-== **Event Streaming - Certificate Management** ==
	30	+//__Consistent triggers naming__//
	31	+We noticed that Trigger types have a different name throughout the portal. Therefore, in this release, on the Manage - Alerting page, we have renamed the "Source" column to "Source trigger" so that we have a consistent naming.
	32	+
	33	+//__Search phrase__//~*~*
	34	+We are now enabling users to search for log entries and error messages in the next-generation architecture models 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”).
	35	+
	36	+//__Improved image building performance__//
	37	+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.
	38	+
	39	+//__Default "errorChannel" on next-generation architecture migration__//~*~*
	40	+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.
	41	+
	42	+== **Bug Fixes** ==
32	32
33		-//__Expired certification notification__//
34		-As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	44	+//__Incorrect deployed containers__//
	45	+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.
35	35
	47	+//__Log messages in next-generation architecture models__//~*~*
	48	+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.
	49	+
	50	+//__Random stuck in deployment plan execution__//
	51	+We addressed an issue where the execution of the deployment plan would occasionally become stuck or halted unexpectedly.
	52	+
36	36	== **Fancy Forum Answers** ==
37	37
38	38	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:
39	39
40		-* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
41		-* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
	57	+* [[(Very) large messages via eMagiz>>https://my.emagiz.com/p/question/172825635703645419||target="blank"]]
	58	+* [[Existing integration sends message to onramp but they disappear before it reaches the routing>>https://my.emagiz.com/p/question/172825635703658192||target="blank"]]
42	42
43	43	== **Key takeaways** ==
44	44
45		-Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
	62	+Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
46	46
47	47	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
48	48	* If you have feedback or ideas for us, talk to the Platypus
49		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	66	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
50	50	* Clear your browser cache (Ctrl + Shift + Del)
51	51	* Check out the release notes [here]
52	52	* Start thinking about how the license tracker can aid your development
...	...	@@ -59,6 +59,6 @@
59	59	{{info}}
60	60	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61	61
62		-~*~* Indicates a GEN3-only feature.
	79	+~*~* Indicates a next-generation-architecture only feature.
63	63	{{/info}})))((({{toc/}}))){{/container}}
64	64	{{/container}}