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,83 +1,54 @@ 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 + 23 +== **Store Improvements** == 24 + 19 19 20 -//__Search boxes__// 21 -Search boxes in the properties overview are now shown by default. 26 +== **Feedback Items** == 22 22 23 -[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 28 +//__Alerting manual pause__// 29 +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. 24 24 25 -//__ Setasmapped__//26 - Itis nowpossible tochoosewhether to set/unsetallattributes ofan entityasmappedindesign.31 +//__Ordering of graphs in Manage__// 32 +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). 27 27 28 -[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 34 +//__UTC times in Grafana panels__// 35 +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. 29 29 30 -//__ SSLsettings__//31 - Changescan nowbedeployedonSSL level withoutcreating anew versionofaflowin Create.37 +//__Update flow designer version__// 38 +The framework used in the flow designer has been updated to the latest version. 32 32 33 -//__Machine deletion__// 34 -When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted. 35 35 36 -[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]] 37 - 38 -//__JMS header handling__// 39 -Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new runtime image(LINK) has been released. 40 - 41 + 41 41 == **Bug Fixes** == 42 -//__Annotation styling__// 43 -It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 44 44 45 -[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 46 46 47 -//__Filter rejection warnings__// 48 -A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 49 - 50 -[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 51 - 52 -//__Manage Explore__// 53 -An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 54 - 55 -//__Page refreshing__// 56 -Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 57 - 58 -//__Message redelivery__// 59 -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. 60 - 61 -//__Deployment plan__// 62 -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. 63 - 64 -//__Overview pages__// 65 -We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. 66 - 67 -//__Memory check__// 68 -Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines. 69 - 70 -//__Copy password__// 71 -The copy to clipboard button now copies the actual value of passwords instead of the masked value of them. 72 - 73 73 == **Fancy Forum Answers** == 74 74 75 75 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: 76 76 77 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]] 78 -* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]] 49 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 79 79 80 -== **Key Takeaways** ==51 +== **Key takeaways** == 81 81 82 82 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: 83 83 ... ... @@ -85,9 +85,10 @@ 85 85 * If you have feedback or ideas for us, talk to the Platypus 86 86 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 87 87 * Clear your browser cache (Ctrl + Shift + Del) 88 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]59 +* Check out the release notes [here] 89 89 * Start thinking about how the license tracker can aid your development 90 90 * Start thinking about major, minor, and patch 62 +* Upgrade to the latest build number 91 91 * Keep making great integrations 92 92 93 93 Let's stay in touch and till next time! ... ... @@ -95,11 +95,6 @@ 95 95 {{info}} 96 96 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 97 97 98 -{{/info}} 99 -))) 100 - 101 -((( 102 -{{toc/}} 103 -))) 70 +~*~* Indicates a next-generation-architecture only feature. 71 +{{/info}})))((({{toc/}}))){{/container}} 104 104 {{/container}} 105 -{{/container}}