Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 574.14
edited by dfirdausy
on 2024/07/01 14:45
on 2024/07/01 14:45
Change comment:
There is no comment for this version
To version 147.1
edited by Erik Bakker
on 2023/08/15 13:53
on 2023/08/15 13:53
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 24-Summer Sonata1 +203 - Fast Paced - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,63 +1,46 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Overthe past week,we focused on improving theusability of ourplatform and addressing community feedback.Specifically, we enhanceduserinterface elements on several pages,includingthedescriptionsofhelptexts,external linkswithinhelptexts, and theoveralllayout ofhelptext pages. Additionally, wemade improvementsto severalpop-up pages. Wealso madetheuserinterface moreuser-friendlyfor debugging integrationflows. Lastly,we resolved anissueforsome models when creatingan EventProcessor.5 +**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items. 7 7 7 +== **Release Properties - Early Feedback** == 8 +The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties. 9 + 8 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. 11 11 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 -//__abc__// 16 -abc. 12 +//__"All entries" are now cleaned up as part of the migration__// 13 +To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture. 17 17 18 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 15 +//__Trigger ID added to our alerting on the next-generation architecture__// 16 +We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable. 19 19 18 +//__Improved performance Manage Dashboards__// 19 +We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture. 20 + 20 20 == **Bug Fixes** == 21 -//__SFTP sessions__// 22 -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. 23 23 23 +//__Ensure no flow can be in a release twice__// 24 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this. 24 24 25 - 26 - 27 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 28 - 29 -//__SMB outbound gateway__// 30 -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. 31 - 32 -//__TaskScheduler__// 33 -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. 34 - 35 -//__View XSLT__// 36 -We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases. 37 - 38 -//__Multipart/form-data HTTP request__// 39 -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. 40 - 41 41 == **Fancy Forum Answers** == 42 42 43 43 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: 44 44 45 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 46 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 47 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 48 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 30 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 49 49 50 -== **Key Takeaways** ==32 +== **Key takeaways** == 51 51 52 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:34 +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: 53 53 54 54 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 55 55 * If you have feedback or ideas for us, talk to the Platypus 56 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 38 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 57 57 * Clear your browser cache (Ctrl + Shift + Del) 58 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]40 +* Check out the release notes [here] 59 59 * Start thinking about how the license tracker can aid your development 60 60 * Start thinking about major, minor, and patch 43 +* Upgrade to the latest build number 61 61 * Keep making great integrations 62 62 63 63 Let's stay in touch and till next time! ... ... @@ -65,11 +65,6 @@ 65 65 {{info}} 66 66 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 67 67 68 -{{/info}} 69 -))) 70 - 71 -((( 72 -{{toc/}} 73 -))) 51 +~*~* Indicates a next-generation-architecture only feature. 52 +{{/info}})))((({{toc/}}))){{/container}} 74 74 {{/container}} 75 -{{/container}}