Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 2.1
edited by eMagiz
on 2022/10/12 10:50
on 2022/10/12 10:50
Change comment:
There is no comment for this version
To version 124.1
edited by Erik Bakker
on 2023/06/19 14:21
on 2023/06/19 14:21
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 185-Todetermine1 +200 - Uncharted Territories - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e Magiz1 +XWiki.ebakker - Content
-
... ... @@ -2,48 +2,56 @@ 2 2 {{container layoutStyle="columns"}}((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Wehavebeenhardatworkbolsteringourofferingconcerning the upcoming rollout ofurwarchitecturestack.Nexttothat, wehavemade severalsmallupdatesasthis releasecontaineda completerevampoftheManagephase.Please takeamomenttoreadthebelow carefully andwork with thenew flow designerassoonaspossibleto familiarizeyourselfwiththisone.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on a lot of things that are unfortanetly not quite ready to be released. As a result the ouput of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier. 6 6 7 -==** AudittrailUserManagement**==7 +== **Next generation improvements and bug fixes** == 8 8 9 - 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"]] 12 - 13 -=== **Improvements** === 14 - 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]] 9 +//__Enhanced right-hand view within Deployment Plan context__// 10 +When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview. 25 25 26 - 27 -== **Feedback items ** == 12 +{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}} 28 28 29 -We have also solved other feedback items besides the key updates around functionality. 14 +//__Improved timeout settings when deploying__// 15 +To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur. 30 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. 17 +{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 33 33 34 - [[image:Main.Images.ReleaseBlog.WebHome@184- FlowDesignerreleaseblog 3.png]]35 - 19 +//__Detailed HTTP Statistics now show user info in specific additional cases__// 20 +To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations. 36 36 22 +{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 23 + 24 +//__Improved loading speed of Manage Dashboard__// 25 +This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase. 26 + 27 +== **Store Improvements** == 28 + 29 +//__Importing in Design is improved__// 30 +We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create. 31 + 32 +== **Bug Fixes** == 33 + 34 +//__Deprecated reminder pop-up removed__// 35 +We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems. 36 + 37 +//__Improved selection area in Flow Designer__// 38 +When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow. 39 + 40 +//__Improved Kafka settings_// 41 +For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them. 42 + 43 +{{info}}We stronly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}} 44 + 37 37 == **Fancy Forum Answers** == 38 38 39 -As always, a gentle reminder to a ll 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:47 +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: 40 40 41 -* [[ Start runtimeviaadelayedstartinaLinuxenvironment?>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]42 -* [[ Failedtocreate sFTP session: Hetsysteemkan hetopgegevenpadvinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]49 +* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]] 50 +* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]] 43 43 44 44 == **Key takeaways** == 45 45 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:54 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 47 47 48 48 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 49 49 * If you have feedback or ideas for us, talk to the Platypus ... ... @@ -54,12 +54,11 @@ 54 54 * Start thinking about major, minor, and patch 55 55 * Upgrade to the latest build number 56 56 * Keep making great integrations 57 -* Check out the new documentation portal. 58 58 59 59 Let's stay in touch and till next time! 60 60 61 61 {{info}} 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]] 69 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 63 63 64 64 ~*~* Indicates a GEN3-only feature. 65 65 {{/info}})))((({{toc/}}))){{/container}}