Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 19-CreationCarousel1 +206 - Situational Deployment - Content
-
... ... @@ -1,59 +1,93 @@ 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!** Thisrelease,wehavea newversionof our eMagiz Mendixconnectoravailable, thatwill supportMendix version 10 and higher.Furthermore,thepathlength in OpenAPI spec importshasbeenincreasedtoa maximumof300 characters. Lastly, we havedonemanybug fixes, oneof which willensure thatSFTPsessions will be closed againaftercompletion.Forthisfix,anew[[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V304.WebHome||target="blank"]]hasbeenpublished.5 +**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you. 7 7 7 +== **Deployment Plan** == 8 + 9 +//__Improved deployment plan to make the process better and more predictable__// 10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines. 11 + 12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 14 + 15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 17 + 18 +//__Properties tab__// 19 +We have removed the deprecated tab Properties in the Deploy phase. 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. 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 + 27 +== **Store Improvements** == 28 + 29 +//__Message definition elements order__// 30 +We fixed an issue that the order of message definition elements was changed after being imported. 31 + 32 +//__Improting a store item with synchronous message definitions__// 33 +We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions. 34 + 35 +//__Importing store items containing static copies__// 36 +We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly. 37 + 8 8 == **Feedback Items** == 9 9 10 -//__e Magiz Mendixconnector__//11 - We releaseda newversion ofoureMagizMendixconnectorthat willsupportMendixversion10and higher.40 +//__Alerting manual pause__// 41 +A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment. 12 12 13 -//__ ImprovedOpenAPIimport__//14 -The pathlengthinOpenAPIspec imports has beenincreasedtoamaximumof300characters.43 +//__Ordering of graphs in Manage__// 44 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first). 15 15 16 -//__ Flowteststacktrace__//17 - Ifaflowtest createsalogline withlevel ‘Warning’or‘Error’andthereisa stacktracecreated,thenweshow thestacktraceinsidethelogmessage onaseparate tab.46 +//__UTC times in Grafana panels__// 47 +All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts. 18 18 19 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]] 49 +//__Update flow designer version__// 50 +The framework used in the flow designer has been updated to the latest version. 20 20 21 -{{info}}TBD{{/info}} 52 +//__Carwash track TLS versions in logging__// 53 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 22 22 55 +//__Moving channels in the flow designer__// 56 +Moving already attached channels in the flow designer has been made sligthly easier. 23 23 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. 58 +//__Topic sizes description change__// 59 +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. 27 27 28 -//__ Volumemappingpasswords__//29 - Passwordsfornetworkvolumes arehiddenon themachine afterdeployment.61 +//__Password change notification__// 62 +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. 30 30 31 -//__ Create integrationremoval__//32 -When removing anintegrationfromCreate,theCreatephase isnow correctlyupdated.64 +//__Password comparison__// 65 +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. 33 33 34 -//__ Legacystatistics__//35 - Legacy pages are nowcorrectlyhiddenwhenrunning onthecurrentruntime architecture.67 +//__Inactive user alerting__// 68 +Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 36 36 37 -//__ Unusedproperties__//38 - Usersare notableto editordeleteeMagizproperties,sonowtheywillalsonot beshowninthe'Unusedproperty overview' anymore.70 +//__Alphabetical sorting on user level in HTTP statistics__// 71 +Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 39 39 40 -//__Enumeration values__// 41 -Enumeration values for event processors can now be edited in Create. 73 +== **Bug Fixes** == 42 42 43 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 75 +//__Flow designer styling__// 76 +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. 44 44 45 -//__ SFTP sessions__//46 - SFTP session factoriesdid not closetheir connection after itwascomplete. This could causeconnectionstarvationontheSFTPserver, and wasespeciallynoticable whenusingtheSFTP SessionFactory without caching,as that factoryopensanewconnectionfor everycall. For this, anew[[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V304.WebHome||target="blank"]] has been released.78 +//__Partial search for messages__// 79 +It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim". 47 47 81 +//__Disk usage after cloud template update__// 82 +In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates. 83 + 48 48 == **Fancy Forum Answers** == 49 49 50 50 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: 51 51 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"]] 88 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 55 55 56 -== **Key Takeaways** ==90 +== **Key takeaways** == 57 57 58 58 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 ... ... @@ -61,9 +61,10 @@ 61 61 * If you have feedback or ideas for us, talk to the Platypus 62 62 * 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>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]98 +* Check out the release notes [here] 65 65 * Start thinking about how the license tracker can aid your development 66 66 * Start thinking about major, minor, and patch 101 +* Upgrade to the latest build number 67 67 * Keep making great integrations 68 68 69 69 Let's stay in touch and till next time! ... ... @@ -71,11 +71,6 @@ 71 71 {{info}} 72 72 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 73 73 74 -{{/info}} 75 -))) 76 - 77 -((( 78 -{{toc/}} 79 -))) 109 +~*~* Indicates a next-generation-architecture only feature. 110 +{{/info}})))((({{toc/}}))){{/container}} 80 80 {{/container}} 81 -{{/container}}