Wiki source code of 208 - Controlled State
Version 250.8 by Danniar Firdausy on 2023/11/07 10:37
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{container}} |
| 2 | {{container layoutStyle="columns"}}((( | ||
| 3 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 4 | |||
| |
246.1 | 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. This overview covers a visibility towards the statistics for Retrieve Latency, Cache Size, Successful and Failed Retrieves. 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. |
| |
206.1 | 6 | |
| |
248.1 | 7 | {{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}} |
| |
206.1 | 8 | |
| |
203.1 | 9 | == **State Generation~*~*** == |
| |
172.1 | 10 | |
| |
242.1 | 11 | //__New Page__// |
| 12 | The following page has been added: | ||
| |
249.1 | 13 | * State generation statistics: Contains the statistics for state generation implementation in your model. This page can be found under Manage->Monitoring, right under the Topic statistics navigation menu. 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. |
| |
227.1 | 14 | |
| |
249.2 | 15 | {{info}}The graphs are configured with the same behaviour as graphs in the other statistics pages, meaning that you can also change the time range, zoom in zoom out to the time frame, etc.{{/info}} |
| |
187.1 | 16 | |
| |
154.1 | 17 | == **Feedback Items** == |
| |
149.1 | 18 | |
| |
250.1 | 19 | //__Improved Information on Removing a Release Version__// |
| 20 | 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. | ||
| |
151.1 | 21 | |
| |
250.2 | 22 | //__Wider and Expandable Fields for XPath Expressions__// |
| |
250.1 | 23 | 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 | |||
| |
250.2 | 25 | //__Old Images Cleanup Mechanism__// |
| 26 | 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. | ||
| |
250.1 | 27 | |
| |
250.3 | 28 | //__Consistent Toggle Switches__// |
| |
250.5 | 29 | We are now implementing eMagiz Design System module in our platform and, in this release, we have updated all instances of the toggle switch to have a more consistent performance and look & feel throughout the platform. |
| |
250.4 | 30 | |
| 31 | //__Search Phrase__// | ||
| 32 | 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”). | ||
| |
242.1 | 33 | |
| |
250.5 | 34 | //__Improved Image Building Performance__// |
| 35 | 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. | ||
| 36 | |||
| 37 | //__Default "errorChannel" on Gen3 Migration__// | ||
| |
250.7 | 38 | During a migration of a model to Gen3, 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. |
| 39 | |||
| 40 | There are cases where flows do not have a custom error handling. In this release, we During Gen3 Migration of a model. | ||
| |
250.5 | 41 | |
| |
124.1 | 42 | == **Bug Fixes** == |
| |
197.1 | 43 | |
| |
250.8 | 44 | //__Wrong 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 instead are deployed. This problem was caused by auto-healing that triggered during a new deployment. | ||
| |
122.1 | 46 | |
| |
242.1 | 47 | //__Topic and event-processor names__// |
| 48 | The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable. | ||
| |
148.1 | 49 | |
| |
1.1 | 50 | == **Fancy Forum Answers** == |
| 51 | |||
| |
30.1 | 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: |
| |
1.1 | 53 | |
| |
199.1 | 54 | * [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] |
| 55 | * [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] | ||
| 56 | * [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] | ||
| |
221.1 | 57 | * [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] |
| |
1.1 | 58 | |
| |
177.1 | 59 | |
| |
1.1 | 60 | == **Key takeaways** == |
| 61 | |||
| |
149.1 | 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: |
| |
1.1 | 63 | |
| |
30.1 | 64 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] |
| |
1.1 | 65 | * If you have feedback or ideas for us, talk to the Platypus |
| |
151.1 | 66 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. |
| |
1.1 | 67 | * Clear your browser cache (Ctrl + Shift + Del) |
| 68 | * Check out the release notes [here] | ||
| 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}} | ||
| |
30.1 | 77 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] |
| |
1.1 | 78 | |
| |
141.1 | 79 | ~*~* Indicates a next-generation-architecture only feature. |
| |
1.1 | 80 | {{/info}})))((({{toc/}}))){{/container}} |
| 81 | {{/container}} |