Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 00-UnchartedTerritories1 +223 - TBD - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. SametKaya1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,66 +1,56 @@ 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!** In the last few weeks, we have worked hard on a lot of things that are unfortunately not quite ready to be released. As a result the output 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 +**Hi there, eMagiz developers!** 7 + 8 +== **Feedback Items** == 9 +//__SwaggerUI default__// 10 +Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown. 6 6 7 - == **Nextgenerationimprovements andbugfixes** ==12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 8 8 9 -//__ Enhanced right-hand view withinDeploymentPlancontext__//10 -W henexecuting your deploymentplan we will showspecific log entriesof theinfo category that indicatethat a container(i.e. runtime) hasstartedupcorrectly. On topof that weshowthewarningsanderrorsinthis overview.14 +//__Deprecated warnings__// 15 +We have continued to resolve deprecated warnings as part of our preparation to upgrade to Mendix version 10. 11 11 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}} 17 +//__Used message types__// 18 +It is now possible to filter the message types in Capture on whether they are used. 13 13 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. 20 +[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]] 21 + 22 +//__Debugger duration__// 23 +Wiretaps and debugging sessions will now collect messages for 10 minutes, this used to be 5. Note that the JMS server needs to be reset (or updated) in order to also store the messages for 10 minutes instead of 5. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. 16 16 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}} 18 - 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. 21 - 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 32 == **Bug Fixes** == 26 +//__SFTP sessions__// 27 +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. 33 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. 29 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]] 36 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 further down the flow. 39 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. 32 +[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]] 42 42 43 -{{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}} 44 - 45 45 == **Fancy Forum Answers** == 46 46 47 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: 48 48 49 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]] 50 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]] 38 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 39 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 40 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 41 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 51 51 52 -== **Key takeaways** ==43 +== **Key Takeaways** == 53 53 54 -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:45 +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: 55 55 56 56 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 57 57 * If you have feedback or ideas for us, talk to the Platypus 58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 49 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 59 59 * Clear your browser cache (Ctrl + Shift + Del) 60 -* Check out the release notes [here] 51 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] 61 61 * Start thinking about how the license tracker can aid your development 62 62 * Start thinking about major, minor, and patch 63 -* Upgrade to the latest build number 64 64 * Keep making great integrations 65 65 66 66 Let's stay in touch and till next time! ... ... @@ -68,6 +68,11 @@ 68 68 {{info}} 69 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]] 70 70 71 -~*~* Indicates a GEN3-only feature. 72 -{{/info}})))((({{toc/}}))){{/container}} 61 +{{/info}} 62 +))) 63 + 64 +((( 65 +{{toc/}} 66 +))) 73 73 {{/container}} 68 +{{/container}}