Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 06-SituationalDeployment1 +219 - Creation Carousel - Content
-
... ... @@ -1,76 +1,59 @@ 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 lastfew weeks, we havedonemuch workfor theDeployphase.On topofthat, we haveworkedon several storefunctionalities.Nextto this,we haveseveralsmaller feedbackitems from ourhackathon effortsthatarenowreleasedto you.6 +**Hi there, eMagiz developers!** This release, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published. 6 6 7 -== ** Deployment Plan** ==8 +== **Feedback Items** == 8 8 9 -//__ Improved deployment planto makethe process better andmorepredictable__//10 - Thealgorithm for genarating a default deployment plan isimprovedtokeep jms downtimeand alertingtoaminimum.Nexttothis, thestart/stop/restartmachine deploymentsteps arenow alsoexecutedcorrectly foraws andon-premises machines.10 +//__eMagiz Mendix connector__// 11 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 11 11 12 -//__ Editingreleaseproperties__//13 - With thisrelease, itwillbepossibletochangethedescriptionofapropertybyediting the property.13 +//__Improved OpenAPI import__// 14 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 14 14 15 -//__ JMSmemorysettingcheck__//16 - Achange inmemorysettings triggersredeploymentofthe containernow.16 +//__Flow test stack trace__// 17 +If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab. 17 17 18 -//__Properties tab__// 19 -We have removed the deprecated tab Properties in the Deploy phase. 19 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]] 20 20 21 -//__Cleanup old images__// 22 -When a release is removed, the related unused images in the on-premises machines will be removed as well. 21 +{{info}}TBD{{/info}} 23 23 24 -//__Performance improvements for loading releases__// 25 -Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before. 26 26 27 -== **Store Improvements** == 24 +== **Bug Fixes** == 25 +//__Error handling__// 26 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this. 28 28 29 -//__ Message definition elementsorder__//30 - We fixedan issue that theordersof message definition’selements werechangedafterimported.28 +//__Volume mapping passwords__// 29 +Passwords for network volumes are hidden on the machine after deployment. 31 31 32 -== **Feedback Items** == 31 +//__Create integration removal__// 32 +When removing an integration from Create, the Create phase is now correctly updated. 33 33 34 -//__ Alertingmanualpause__//35 - A few releasesago wechanged the behaviorof alertinginthe deployment plan. Noweach time when a deployment plan is executed the alerting will be automaticallyre-enabled whenthe deployercloses thedeploymentplan or closes theweb browser. Themajorityofthe users arehappy with thenew behavior, butthere are someuse cases that you donotwant start the alerting immediately.With this release, if alertinghas been paused manually, this will notbeactivated automatically aftera release deployment.34 +//__Legacy statistics__// 35 +Legacy pages are now correctly hidden when running on the current runtime architecture. 36 36 37 -//__ Orderingof graphsin Manage__//38 - Thegraphsin Manage are noworderedaccordingtoimportance.This meansthat runtimestatisticsare sorted by "ProcessCPU usage"(highestfirst), queuestatisticsaresortedby "Messagesinqueue" (highestfirst), and HTTPstatistics aresorted by"Unsuccessfulrequests" (highestfirst).37 +//__Unused properties__// 38 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore. 39 39 40 -//__ UTC times in Grafanapanels__//41 - All Grafanapanels now show UTC times,which are normallyused ineMagiz, insteadof local(browser)timezones. This way, itiseasierto match graphs with loggingevents oralerts.40 +//__Enumeration values__// 41 +Enumeration values for event processors can now be edited in Create. 42 42 43 -//__Update flow designer version__// 44 -The framework used in the flow designer has been updated to the latest version. 43 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 45 45 46 -//__ Carwash track TLSversionsin logging__//47 - Anewloggingfeaturewillbereleased, enablingus tomakebetterchoicesindeprecatingoldencryption standards.45 +//__SFTP sessions__// 46 +SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released. 48 48 49 -//__Moving channels in the flow designer__// 50 -Moving already attached channels in the flow designer has been made sligthly easier. 51 - 52 -//__Topic sizes description change__// 53 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved. 54 - 55 -//__Password change notification__// 56 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action. 57 - 58 -//__Password comparison__// 59 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database. 60 - 61 - 62 -== **Bug Fixes** == 63 - 64 -//__Flow designer styling__// 65 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities. 66 - 67 67 == **Fancy Forum Answers** == 68 68 69 69 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: 70 70 71 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 52 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 53 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 54 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 72 72 73 -== **Key takeaways** ==56 +== **Key Takeaways** == 74 74 75 75 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: 76 76 ... ... @@ -78,10 +78,9 @@ 78 78 * If you have feedback or ideas for us, talk to the Platypus 79 79 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 80 80 * Clear your browser cache (Ctrl + Shift + Del) 81 -* Check out the release notes [here] 64 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 82 82 * Start thinking about how the license tracker can aid your development 83 83 * Start thinking about major, minor, and patch 84 -* Upgrade to the latest build number 85 85 * Keep making great integrations 86 86 87 87 Let's stay in touch and till next time! ... ... @@ -89,6 +89,11 @@ 89 89 {{info}} 90 90 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 91 91 92 -~*~* Indicates a next-generation-architecture only feature. 93 -{{/info}})))((({{toc/}}))){{/container}} 74 +{{/info}} 75 +))) 76 + 77 +((( 78 +{{toc/}} 79 +))) 94 94 {{/container}} 81 +{{/container}}