Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 574.17
edited by dfirdausy
on 2024/07/01 15:06
on 2024/07/01 15:06
Change comment:
There is no comment for this version
To version 150.1
edited by Erik Bakker
on 2023/08/29 10:57
on 2023/08/29 10:57
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 +204 - Found It - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,60 +1,49 @@ 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 our platform and addressing communityfeedback.Specifically, we enhanceduserinterface elements on several pages,includingthedescriptionsofhelptexts,external linkswithinhelptexts, and theoveralllayout ofhelptext pages. Additionally, wemade improvementstoseveral pop-uppages.Wealsomade the user interfacemore user-friendly fordebugging integrationflows. Lastly, we resolved anissue forsome models when creatingan EventProcessor.5 +**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack. 7 7 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 -//__Property value page__// 16 -Pop-up pages with non-editable input fields containing long text are now displaying the entire content without any text being cut off at the edge of the page. 9 +//__Improved check on nested property placeholders__// 10 +To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing. 17 17 18 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 12 +//__Removed outdated properties when deploying on the new generation architecture stack__// 13 +We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before in order to connect to a Kafka cluster but have become obsolete once you migrate. 19 19 20 -== **Bug Fixes** == 21 -//__Adding tags__// 22 -In the Capture phase, clicking to add or remove a tag in the pop-up page for specifying integration requirements no longer displays a 'blocked' icon. 15 +{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}} 23 23 24 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 17 +//__Improved performance Manage Dashboards__// 18 +We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture. 25 25 26 -//__SMB outbound gateway__// 27 -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. 20 +== **Bug Fixes** == 28 28 29 -//__ TaskScheduler__//30 - Inrareoccurences,whenaTaskSchedulerwasused,adeadlocksituationcouldoccurduetothreadstarvation.The numberofthreads available totheTaskScheduler has beenincreasedtoresolvethisissue.For this,anew[[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V310.WebHome||target="blank"]]isavailable.22 +//__Errors with long stack traces or long message histories will now also show in eMagiz__// 23 +We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s). 31 31 32 -//__ ViewXSLT__//33 -We fixed a nissuewiththetransformationtooling,where itwasnotpossibletoviewanXSLTincertain cases.25 +//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__// 26 +We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration. 34 34 35 -//__Multipart/form-data HTTP request__// 36 -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. 37 - 38 38 == **Fancy Forum Answers** == 39 39 40 40 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: 41 41 42 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 43 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 44 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 45 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 32 +* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]] 33 +* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]] 46 46 47 -== **Key Takeaways** ==35 +== **Key takeaways** == 48 48 49 49 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: 50 50 51 51 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 52 52 * If you have feedback or ideas for us, talk to the Platypus 53 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 41 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 54 54 * Clear your browser cache (Ctrl + Shift + Del) 55 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]43 +* Check out the release notes [here] 56 56 * Start thinking about how the license tracker can aid your development 57 57 * Start thinking about major, minor, and patch 46 +* Upgrade to the latest build number 58 58 * Keep making great integrations 59 59 60 60 Let's stay in touch and till next time! ... ... @@ -62,11 +62,6 @@ 62 62 {{info}} 63 63 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 64 64 65 -{{/info}} 66 -))) 67 - 68 -((( 69 -{{toc/}} 70 -))) 54 +~*~* Indicates a next-generation-architecture only feature. 55 +{{/info}})))((({{toc/}}))){{/container}} 71 71 {{/container}} 72 -{{/container}}