Changes for page 208 - Controlled State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-205 - World Explorers
	1	+208 - Controlled State

Author

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

Content

...	...	@@ -2,59 +2,60 @@
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 processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
	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		-== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
	7	+{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
8	8
9		-As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
	9	+== **State Generation - Manage overview** ==
10	10
11		-== **Feedback Items** ==
	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.
12	12
13		-//__Improved Validation when migrating to the next-generation architecture__//
14		-To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
	14	+[[image:Main.Images.Release Blog.WebHome@208-release-blog-1.jpg]]
15	15
16		-{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
	16	+== **Feedback Items** ==
17	17
18		-//__Improved HTTP Statistics__//
19		-To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
	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.
20	20
21		-//__"Topic Full" alert restriction changed__//
22		-With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better.
	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.
23	23
24		-//__Improved performance Manage Dashboards__//
25		-We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
	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.
26	26
27		-//__Show values on the runtime level in Deploy Architecture__//
28		-We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
	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.
29	29
30		-{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
31		-* JMS - The number of queues in the active release.
32		-* Messaging Container - The number of messaging integrations in the active release.
33		-* Messaging Connector - The number of messaging integrations related to this system in the active release.
34		-* API Gateway Container - The number of operations in the active release.
35		-* Event Streaming Container - The number of event processors in the active release.
36		-
37		-There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
38		-
	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	+
39	39	== **Bug Fixes** ==
40	40
41		-//__Improved information Queue Statistics__//
42		-Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release.
	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.
43	43
44		-//__Gain the ability again to configure certificates in Deploy Architecture again__//
45		-In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
	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.
46	46
47		-//__Ensure that differing container configurations deploy the correct configuration__//
48		-When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
	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.
49	49
50		-//__Remove queurying options in Manage__//
51		-To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
52		-
53	53	== **Fancy Forum Answers** ==
54	54
55	55	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:
56	56
57		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||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"]]
58	58
59	59	== **Key takeaways** ==
60	60