Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-201 - Be Informed
	1	+208 - Controlled State

Author

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

Content

...	...	@@ -2,64 +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 planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you.
	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		-== **Announcement - Release Properties** ==
8		-As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
	7	+{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
9	9
10		-== ** Deploy Architecture - Apply To Environment improvements ** ==
11		-As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button.
	9	+== **State Generation - Manage overview** ==
12	12
13		-//__Enhanced right-hand view within Deployment Plan context__//
14		-When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
	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.
15	15
16		-{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
	14	+[[image:Main.Images.Release Blog.WebHome@208-release-blog-1.jpg]]
17	17
18		-//__Improved timeout settings when deploying__//
19		-To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
	16	+== **Feedback Items** ==
20	20
21		-{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
	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		-//__Detailed HTTP Statistics now show user info in specific additional cases__//
24		-To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
	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.
25	25
26		-{{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}}
	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		-//__Improved loading speed of Manage Dashboard__//
29		-This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
	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		-== **Store Improvements** ==
32		-
33		-//__Importing in Design is improved__//
34		-We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
35		-
	30	+//__Consistent triggers naming__//
	31	+We noticed that Trigger types have a different name throughout the portal. Therefore, in this release, in Manage - Alerting page, we have renamed the "Source" column to "Source trigger" so then we have a consistent naming.
	32	+
	33	+//__Search phrase__//
	34	+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”).
	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	+
36	36	== **Bug Fixes** ==
37	37
38		-//__Deprecated reminder pop-up removed__//
39		-We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
	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.
40	40
41		-//__Improved selection area in Flow Designer__//
42		-When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
	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.
43	43
44		-//__Improved Kafka settings__//
45		-For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
	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.
46	46
47		-{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
48		-
49	49	== **Fancy Forum Answers** ==
50	50
51	51	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:
52	52
53		-* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
54		-* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||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"]]
55	55
56	56	== **Key takeaways** ==
57	57
58		-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:
59	59
60	60	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61	61	* If you have feedback or ideas for us, talk to the Platypus
62		-* 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.
63	63	* Clear your browser cache (Ctrl + Shift + Del)
64	64	* Check out the release notes [here]
65	65	* Start thinking about how the license tracker can aid your development
...	...	@@ -72,6 +72,6 @@
72	72	{{info}}
73	73	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74	74
75		-~*~* Indicates a GEN3-only feature.
	79	+~*~* Indicates a next-generation-architecture only feature.
76	76	{{/info}})))((({{toc/}}))){{/container}}
77	77	{{/container}}