Wiki source code of 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}(((
3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
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.
6
7 {{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
8
9 == **State Generation - Manage overview~*~*** ==
10
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.
13
14 [[image:Main.Images.Release Blog.WebHome@208-release-blog-1.jpg]]
15
16 == **Feedback Items** ==
17
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
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
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
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
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** ==
43
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.
46
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
53 == **Fancy Forum Answers** ==
54
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
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"]]
59
60 == **Key Takeaways** ==
61
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:
63
64 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
65 * If you have feedback or ideas for us, talk to the Platypus
66 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 * Clear your browser cache (Ctrl + Shift + Del)
68 * Check out the release notes [[here>>doc:Main.Release Information.Portal.208 - Controlled State.WebHome||target="blank"]]
69 * Start thinking about how the license tracker can aid your development
70 * Start thinking about major, minor, and patch
71 * Upgrade to the latest build number
72 * Keep making great integrations
73
74 Let's stay in touch and till next time!
75
76 {{info}}
77 ~*~* Indicates a next-generation-architecture only feature.
78 {{/info}})))((({{toc/}}))){{/container}}
79 {{/container}}