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,47 @@ 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 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.6 +**Hi there, eMagiz developers!** 6 6 7 -== **Deployment Plan** == 8 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 orders of message definition’s elements were changed after imported. 31 - 32 32 == **Feedback Items** == 10 +//__Machine agents__// 11 +We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more here. 33 33 34 -//__ Alertingmanualpause__//35 - A fewreleases agowechangedthe behaviorof alerting in thedeploymentplan. Now eachtime when a deployment planis executedthealertingwill beautomatically re-enabledwhenthe deployerclosesthe deploymentplan or closes thewebbrowser. The majorityofthe usersare happy withthenew behavior, but there are someuse cases that you donotwant start the alerting immediately.With this release,ifalerting has been pausedmanually,thiswill not beactivated automatically aftera release deployment.13 +//__Custom webhook__// 14 +We removed a deprecated functionality that sends a custom webhook when upgrading the environment. Please find out more here. 36 36 37 -//__ Orderingof graphs inManage__//38 - Thegraphsin Manage arenowordered accordingtoimportance.Thismeans that runtimestatistics are sorted by "Process CPU usage" (highestfirst),queue statisticsaresortedby "Messages inqueue" (highestfirst), andHTTPstatistics are sortedby "Unsuccessful requests" (highest first).16 +//__eMagiz Mendix connector__// 17 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.4 39 39 40 -//__ UTC timesinGrafanapanels__//41 - AllGrafanapanels now show UTCtimes, whicharenormallyusedin eMagiz, instead of local(browser) time zones.Thisway,it iseasiertomatchgraphs withloggingeventsoralerts.19 +//__Improved OpenAPI import__// 20 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 42 42 43 -//__Update flow designer version__// 44 -The framework used in the flow designer has been updated to the latest version. 22 +== **Bug Fixes** == 23 +//__Error handling__// 24 +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. 45 45 46 -//__ Carwashtrack TLS versionsin logging__//47 - A newloggingfeaturewill be released,enablingus tomake betterchoices indeprecatingoldencryptionstandards.26 +//__Volume mapping passwords__// 27 +Passwords for network volumes are hidden on the machine after deployment. 48 48 49 -//__ Moving channelsintheflow designer__//50 - Moving alreadyattached channelsintheflowdesignerhasbeenmadesligthly easier.29 +//__Create integration removal__// 30 +When removing an integration from Create, the Create phase is correctly updated as well. 51 51 52 -//__ Topic sizesdescriptionchange__//53 - In thechangedescription(andHistory)whenalteringthe topicsize of atopic thenew and old value wereswitchedaround creatingconfusion, this has beenresolved.32 +//__Legacy statistics__// 33 +Legacy pages are now correctly hidden when running on the current runtime architecture. 54 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"]] 39 +* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]] 40 +* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]] 41 +* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]] 42 +* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]] 72 72 73 -== **Key takeaways** ==44 +== **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] 52 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.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}} 62 +{{/info}} 63 +))) 64 + 65 +((( 66 +{{toc/}} 67 +))) 94 94 {{/container}} 69 +{{/container}}