Changes for page 208 - Controlled State
Last modified by CarlijnKokkeler on 2024/04/18 13:10
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 208 -ControlledState1 +185 - To determine - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.eMagiz - Content
-
... ... @@ -2,71 +2,52 @@ 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 donemuch worktoimprovethefunctionalityof ourstategenerationsolutionsothat youcanhave abetteroverviewof itsimplementationinyourenvironment.Thisoverview coversavisibilitytowardsthestatisticsforRetrieve Latency,Cache Size, SuccessfulandFailed Retrieves.Next to themonitoringfor the stategenerationimplementationin yourmodel, several feedbackitemsrevolvingaround user interfacingcomponents in ourplatformthatcanimprovetheuser experiencearealsoreleased.Lastly,someperformance improvementsand bug fixes havealsobeenimplemented.5 +**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one. 6 6 7 - {{warning}}Stategeneration functionalityisonly accessible formodels withanadd-on stategenerationlicense.{{/warning}}7 +==**Audit trail User Management**== 8 8 9 -== **State Generation~*~*** == 10 - 11 -//__New Page__// 12 -The following page has been added: 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. 14 - 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}} 16 - 17 -== **Feedback Items** == 18 - 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. 21 - 22 -//__Wider and Expandable Fields for XPath Expressions__// 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 - 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. 27 - 28 -//__Consistent Toggle Switches__// 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. 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”). 33 33 34 - //__ImprovedImageBuildingPerformance__//35 - We haveimplemented animprovement on thepreparingstep ofthe release at thebeginingofthe deployment,whichleadsto afasterdeployment process.10 +==**Next Generation Monitoring & Alerting engine**== 11 +In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now used State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations. In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach). We have already released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]] 36 36 37 -//__Default "errorChannel" on Gen3 Migration__// 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. 13 +=== **Improvements** === 41 41 42 -== **Bug Fixes** == 15 +* Performance Deployment plan 16 +When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release. 17 + 18 +* Flow Designer updates 19 +We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made. 20 + 21 + 22 + 23 + 24 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]] 43 43 44 - //__IncorrectDeployed Containers__//45 - Afix has been implementedtoaddress the issue where oldercontainerswere deployed while itwas shown that thenew ones instead are deployed. This problemwascausedby auto-healing that triggered during a new deployment.26 + 27 +== **Feedback items ** == 46 46 47 -//__Log Messages in Gen3 Models__// 48 -We have implemented an improvement in our infra components that is intended to reduce the occurance of log messages failed to be sent in Gen3 models. 29 +We have also solved other feedback items besides the key updates around functionality. 30 + 31 +//__Set runtime field as first selected field on property level__// 32 +With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well. 33 + 34 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]] 49 49 50 -//__Random Stuck in Deployment Plan Execution__// 51 -We addressed an issue where the execution of deployment plan would occasionally become stuck or halted unexpectedly. 52 52 53 53 == **Fancy Forum Answers** == 54 54 55 -As always, this isa 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 +As always, a gentle reminder to all 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 -* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]] 58 -* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]] 59 -* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]] 60 -* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]] 41 +* [[Start runtime via a delayed start in a Linux environment?>https://my.emagiz.com/p/question/172825635703146181||target="blank"]] 42 +* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]] 61 61 62 - 63 63 == **Key takeaways** == 64 64 65 -Thanks to all whohelpedbuildandthose who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:46 +Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 66 66 67 67 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 68 68 * If you have feedback or ideas for us, talk to the Platypus 69 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 50 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 70 70 * Clear your browser cache (Ctrl + Shift + Del) 71 71 * Check out the release notes [here] 72 72 * Start thinking about how the license tracker can aid your development ... ... @@ -73,12 +73,13 @@ 73 73 * Start thinking about major, minor, and patch 74 74 * Upgrade to the latest build number 75 75 * Keep making great integrations 57 +* Check out the new documentation portal. 76 76 77 77 Let's stay in touch and till next time! 78 78 79 79 {{info}} 80 -~* Indicates a Beta feature. If you would like to get access to this beta feature ,please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]62 +~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 81 81 82 -~*~* Indicates a next-generation-architecture only feature.64 +~*~* Indicates a GEN3-only feature. 83 83 {{/info}})))((({{toc/}}))){{/container}} 84 84 {{/container}}