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 20 -Patch Parade1 +206 - Situational Deployment - Content
-
... ... @@ -1,72 +1,64 @@ 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!** 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 8 -== ** Feedback Items** ==7 +== **Deployment Plan** == 9 9 10 -//__Int egrationpatterninformation__//11 - Integration patterninformationoftheselectedmessage typehasbeen addedto thepop-upthat isshowninCapture whencreatinga newintegration.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. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 14 14 15 -//__M essagequeue history__//16 -A llevents that relatetomessagequeues(delete message, delete all messagesor delete queue) are loggedin theManagephaseinsteadof theDeploy phase.15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 17 17 18 -[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]] 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. 19 19 20 - //__Searchboxes__//21 - Searchboxesin the properties overview are now shown by default.24 +== **Store Improvements** == 25 + 22 22 23 - [[image:Main.Images.ReleaseBlog.WebHome@release-220-search-boxes.png]]27 +== **Feedback Items** == 24 24 25 -//__ Setasmapped__//26 - It isnow possible to choosewhether toset/unsetallattributes ofan entity asmapped in design.29 +//__Alerting manual pause__// 30 +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. 27 27 28 -[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 32 +//__Ordering of graphs in Manage__// 33 +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). 29 29 30 -//__ SSLsettings__//31 - Changescan nowbedeployedonSSL levelwithoutcreatinganewversionofaflow inCreate.35 +//__UTC times in Grafana panels__// 36 +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. 32 32 33 -//__ Machine deletion__//34 - Whentrying todeletea machinethatstillhascontainerslinked to it, the userwillbepresentedwith a pop-upexplaining whythemachinecannotbedeleted.38 +//__Update flow designer version__// 39 +The framework used in the flow designer has been updated to the latest version. 35 35 36 -[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]] 41 +//__Carwash track TLS versions in logging__// 42 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 37 37 38 -== **Bug Fixes** == 39 -//__Annotation styling__// 40 -It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 44 +//__Moving channels in the flow designer__// 45 +Moving already attached channels in the flow designer has been made sligthly easier. 41 41 42 -[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 47 +//__Topic sizes description change__// 48 +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. 43 43 44 -//__Filter rejection warnings__// 45 -A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 50 +//__Topic sizes description change__// 51 + 52 +== **Bug Fixes** == 46 46 47 -[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 48 48 49 -//__Manage Explore__// 50 -An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 51 - 52 -//__Page refreshing__// 53 -Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 54 - 55 -//__Message redelivery__// 56 -An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page. 57 - 58 -//__Deployment plan__// 59 -We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps. 60 - 61 61 == **Fancy Forum Answers** == 62 62 63 63 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: 64 64 65 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 66 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 67 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 59 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 68 68 69 -== **Key Takeaways** ==61 +== **Key takeaways** == 70 70 71 71 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: 72 72 ... ... @@ -74,9 +74,10 @@ 74 74 * If you have feedback or ideas for us, talk to the Platypus 75 75 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 76 76 * Clear your browser cache (Ctrl + Shift + Del) 77 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]69 +* Check out the release notes [here] 78 78 * Start thinking about how the license tracker can aid your development 79 79 * Start thinking about major, minor, and patch 72 +* Upgrade to the latest build number 80 80 * Keep making great integrations 81 81 82 82 Let's stay in touch and till next time! ... ... @@ -84,11 +84,6 @@ 84 84 {{info}} 85 85 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 86 86 87 -{{/info}} 88 -))) 89 - 90 -((( 91 -{{toc/}} 92 -))) 80 +~*~* Indicates a next-generation-architecture only feature. 81 +{{/info}})))((({{toc/}}))){{/container}} 93 93 {{/container}} 94 -{{/container}}