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,68 +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 work toimprove thefunctionalityof ourstate-generationsolutionsothatyoucanhave abetteroverviewofits implementationinyour environment.Nextto 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 - 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 32 33 - //__Searchphrase__//34 - Weare now enablinguserstosearch forlogentries and error messagesbased onphrasescontainingtwo ormorewords,instead ofonlyone wordorthefullsentence.This also means that the usercansearchforentrieswithdistances of2orincompletesearchphrases(e.g.,“startinengine”tolookfor“starting servletengine”).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"]] 35 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. 13 +=== **Improvements** === 38 38 39 - //__Default"errorChannel"on next-generationarchitecture migration__//40 - Duringa migrationofamodeltothenext-generation architecture,wehaveintroduceda checknowforflowsthatdidnothave customerror handlingtosettheirerror channelto "errorChannel"after the migrationifthecustom errorhandling isset to false.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. 41 41 42 -== **Bug Fixes** == 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 were deployed. This problemwascausedby auto-healing that was triggered during a new deployment.26 + 27 +== **Feedback items ** == 46 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. 29 +We have also solved other feedback items besides the key updates around functionality. 49 49 50 -//__ Random stuckindeploymentplanexecution__//51 -W eaddressedanissuewhere the execution ofthedeploymentplanwouldoccasionallybecomestuckor haltedunexpectedly.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. 52 52 34 +[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]] 35 + 36 + 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 -* [[ (Very)largemessagesvia eMagiz>>https://my.emagiz.com/p/question/172825635703645419||target="blank"]]58 -* [[ Existingintegrationsendsmessage toonrampbut theydisappearbefore itreaches therouting>>https://my.emagiz.com/p/question/172825635703658192||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"]] 59 59 60 60 == **Key takeaways** == 61 61 62 -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: 63 63 64 64 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 65 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. 50 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 67 67 * Clear your browser cache (Ctrl + Shift + Del) 68 68 * Check out the release notes [here] 69 69 * Start thinking about how the license tracker can aid your development ... ... @@ -70,12 +70,13 @@ 70 70 * Start thinking about major, minor, and patch 71 71 * Upgrade to the latest build number 72 72 * Keep making great integrations 57 +* Check out the new documentation portal. 73 73 74 74 Let's stay in touch and till next time! 75 75 76 76 {{info}} 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]]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]] 78 78 79 -~*~* Indicates a next-generation-architecture only feature.64 +~*~* Indicates a GEN3-only feature. 80 80 {{/info}})))((({{toc/}}))){{/container}} 81 81 {{/container}}