Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 128.1
edited by Erik Bakker
on 2023/07/17 14:47
on 2023/07/17 14:47
Change comment:
There is no comment for this version
To version 574.10
edited by dfirdausy
on 2024/07/01 14:33
on 2024/07/01 14:33
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 -2 01-BeInformed1 +224 - Summer Sonata - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - Content
-
... ... @@ -1,70 +1,61 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Inthelastfewweeks, wehave workedhardon planning the upcomingQ and finishingupfeaturesofthelastQ. Moreonthat later.On topofthat wehave several smalleritemsas a resultofourhackathonefforts topresent toyou.6 +**Hi there, eMagiz developers!** Over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor. 6 6 7 -== **Announcement - Release Properties** == 8 -As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 8 +== **Feedback Items** == 9 +//__Integration requirements: retention duration and bytes// 10 +The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes. 9 9 10 -== ** Deploy Architecture - Apply To Environment improvements ** == 11 -As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button. 12 +//__Integration requirements: Help text__// 13 +Collapsing the help text of this pop-up page by clicking the "?" icon on the top right corner of the pop-up page will now correctly hide the help text pane. 14 + 15 +//__Debugger duration__// 16 +Wiretaps and debugging sessions will now collect messages for ten minutes, this used to be five. Note that the JMS server needs to be updated in order to also store the messages for ten minutes instead of five. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. 12 12 13 -//__Enhanced right-hand view within Deployment Plan context__// 14 -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. 18 +== **Bug Fixes** == 19 +//__SFTP sessions__// 20 +Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification. 15 15 16 - {{info}}Note that when the JMS containergetsrestarted connection errorsin the logs area normal thing to witness so keep youreyes peeled for the startup logging on JMS level to gainconfidence in the deployment.{{/info}}22 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]] 17 17 18 -//__Improved timeout settings when deploying__// 19 -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. 20 20 21 - {{info}}Note that this fix is part of a new runtime imagefor the current-generationruntimes.Thereleasenotes of this canbe found [[here>>doc:Main.ReleaseInformation.Runtime Images.WebHome||target="blank"]]{{/info}}25 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 22 22 23 -//__ Detailed HTTPStatisticsnow showuser info in specific additionalcases__//24 -T o solveabugforaspecificclientwe changedthe logictoshow theuserinfo(i.e.firstpartof theapikey)in aspecific implementationjust aswealready do inourstandardimplementations.27 +//__SMB outbound gateway__// 28 +The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. 25 25 26 -{{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}} 30 +//__TaskScheduler__// 31 +In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. 27 27 28 -//__ Improved loading speedof Manage Dashboard__//29 - This releaseimprovesthe loadingspeedwithwhich allthedashboardsinManageareshowntotheuser. Thiswillenhancetheuser experiencewithintheManagephase.33 +//__View XSLT__// 34 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases. 30 30 31 -== **Store Improvements** == 36 +//__Multipart/form-data HTTP request__// 37 +The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available. 32 32 33 -//__Importing in Design is improved__// 34 -We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create. 35 - 36 -== **Bug Fixes** == 37 - 38 -//__Deprecated reminder pop-up removed__// 39 -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. 40 - 41 -//__Improved selection area in Flow Designer__// 42 -When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow. 43 - 44 -//__Improved Kafka settings__// 45 -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. 46 - 47 -{{info}}We strongly 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}} 48 - 49 49 == **Fancy Forum Answers** == 50 50 51 51 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: 52 52 53 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]] 54 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]] 43 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 44 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 45 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 46 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 55 55 56 -== **Key takeaways** ==48 +== **Key Takeaways** == 57 57 58 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:50 +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: 59 59 60 60 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 61 61 * If you have feedback or ideas for us, talk to the Platypus 62 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 54 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 63 63 * Clear your browser cache (Ctrl + Shift + Del) 64 -* Check out the release notes [here] 56 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]] 65 65 * Start thinking about how the license tracker can aid your development 66 66 * Start thinking about major, minor, and patch 67 -* Upgrade to the latest build number 68 68 * Keep making great integrations 69 69 70 70 Let's stay in touch and till next time! ... ... @@ -72,6 +72,11 @@ 72 72 {{info}} 73 73 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 74 74 75 -~*~* Indicates a GEN3-only feature. 76 -{{/info}})))((({{toc/}}))){{/container}} 66 +{{/info}} 67 +))) 68 + 69 +((( 70 +{{toc/}} 71 +))) 77 77 {{/container}} 73 +{{/container}}