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 +223 - TBD - Content
-
... ... @@ -1,54 +1,49 @@ 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!** 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 - == **Deployment Plan** ==12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]] 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. 14 +== **Bug Fixes** == 15 +//__Cron triggers__// 16 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05. 11 11 12 -//__Editing release properties__// 13 -With this release, it will be possible to change the description of a property by editing the property. 18 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]] 14 14 15 -//__ JMS memorysetting check__//16 - Achange inmemory settingstriggers redeployment of thecontainernow.20 +//__Trigger activation__// 21 +Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed. 17 17 18 -//__Properties tab__// 19 -We have removed the deprecated tab Properties in the Deploy phase. 20 - 21 -//__Cleanup old images__// 22 - 23 -== **Store Improvements** == 24 - 23 +//__Multiple users deploying__// 24 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. 25 25 26 - == **FeedbackItems** ==26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]] 27 27 28 -//__ Alertingmanual pause__//29 - A fewreleases ago we changed the behavior of alertingin the deploymentplan. Now eachtimewhenadeploymentplan is executed thealerting will be automatically re-enabled whenthe deployer closesthe deploymentplan orcloses theweb browser. The majorityoftheusers arehappy with thenewbehavior,but therearesome use cases that you do not want start the alerting immediately.Withthis release, if alerting has been paused manually,this will not be activated automatically after a release deployment.28 +//__Invalid memory configurations__// 29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations. 30 30 31 -//__ Orderingof graphsinManage__//32 - The graphs in Manage arenow orderedaccordingtoimportance.This meansthat runtimestatisticsare sorted by"Process CPU usage" (highestfirst),queuestatistics aresorted by "Messagesin queue"(highestfirst), andHTTPstatistics are sortedby "Unsuccessfulrequests" (highest first).31 +//__Property value synchronization__// 32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly. 33 33 34 -//__ UTCtimes in Grafana panels__//35 - AllGrafana panelsnowshowUTCtimes, which arenormallyusedin eMagiz, instead oflocal (browser)timezones. This way, itiseasierto match graphswithloggingeventsor alerts.34 +//__JMS number__// 35 +The number on the JMS container correctly displays the amount of queues present in Design. 36 36 37 -//__Update flow designer version__// 38 -The framework used in the flow designer has been updated to the latest version. 37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]] 39 39 40 - 41 - 42 -== **Bug Fixes** == 43 - 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 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 43 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]] 44 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]] 50 50 51 -== **Key takeaways** ==46 +== **Key Takeaways** == 52 52 53 53 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: 54 54 ... ... @@ -56,10 +56,9 @@ 56 56 * If you have feedback or ideas for us, talk to the Platypus 57 57 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 58 58 * Clear your browser cache (Ctrl + Shift + Del) 59 -* Check out the release notes [here] 54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]] 60 60 * Start thinking about how the license tracker can aid your development 61 61 * Start thinking about major, minor, and patch 62 -* Upgrade to the latest build number 63 63 * Keep making great integrations 64 64 65 65 Let's stay in touch and till next time! ... ... @@ -67,6 +67,11 @@ 67 67 {{info}} 68 68 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 69 69 70 -~*~* Indicates a next-generation-architecture only feature. 71 -{{/info}})))((({{toc/}}))){{/container}} 64 +{{/info}} 65 +))) 66 + 67 +((( 68 +{{toc/}} 69 +))) 72 72 {{/container}} 71 +{{/container}}