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 -22 5-Pop-up Party1 +212 - Failover Fiesta - Content
-
... ... @@ -3,81 +3,43 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In this release, a new runtime image (LINK) will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration.Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens.Find out all we released below!6 +**Hi there, eMagiz developers!** This release... 7 7 8 8 == **Feedback Items** == 9 -//__Alerting notification settings__// 10 -The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature. 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]] 10 +//__Failover setup__// 11 +New components have been created to support a failover setup. More information can be found [[here>>doc:Main.Release Information.Runtime Images.V2.1.0||target="blank"]] 13 13 14 -//__Process containers__// 15 -If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern. 13 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]] 16 16 17 -//__ Designsettings__//18 - WhenpressingApplysettingsinDesignSettings,aconfirmationscreenwillnowbe shownto presentthechanges thatwillbetakenintoeffect for each environment.15 +//__External recipients emailaddress__// 16 +The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users. 19 19 20 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]] 18 +//__Broker queue metrics dashboards__// 19 +It is now possible to select the MQTT broker in the queue metrics dashboards. 21 21 22 -//__Untested images__// 23 - A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before. 24 - 25 -[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]] 21 +//__Runtime image version__// 22 +The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment. 26 26 27 -//__Infinispan Cache Manager__// 28 -We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available. 29 - 30 -//__Infinispan Cache Manager error message__// 31 -We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available. 32 32 33 -//__Flow bump__// 34 -When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description. 35 - 36 -[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]] 37 - 38 -//__Unused support objects__// 39 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'. 40 - 41 -[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]] 42 - 43 -//__Deleting routes__// 44 -For clarity purposes, a confirmation pop-up will be shown when deleting routes. 45 - 46 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]] 47 - 48 -//__Debug queue__// 49 -The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it. 50 - 51 -[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]] 52 - 53 53 == **Bug Fixes** == 54 -//__Internal server error__// 55 -The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it. 56 56 57 -//__ Namespace update__//58 - Editinga namespace usedina messagedefinitionautomaticallyupdatesthemessagedefinition&transformations.27 +//__Message throughput__// 28 +The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases. 59 59 60 -//__ Errorpop-up__//61 - Wefixedan issue where apop-upwasshownwithanincorrect errorwhileeditingthemessagemapping of a synchronousflows.30 +//__Cloud template upgrade incorrect rollback__// 31 +An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks. 62 62 63 -//__ SMBinboundchanneladapter__//64 - The SMB inbound channel adapter failedtoretrieve files when theremotedirectory pointedto a pathwith multipledirectoriesin it, unless they were seperated with'}}' instead of '{{/'. This has been resolved, meaning that remotedirectoriesthat containmultiplefoldersin its path can (and should) contain'/'again.For this, a new runtimeimageLINK is available.33 +//__Next generation block__// 34 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 65 65 66 -//__Heap memory__// 67 -The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available. 68 - 69 -//__Classpath conflicts__// 70 -We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. 71 - 72 72 == **Fancy Forum Answers** == 73 73 74 74 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: 75 75 76 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 77 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 78 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 40 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]] 79 79 80 -== **Key Takeaways** ==42 +== **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,7 +85,7 @@ 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.224 - Summer Sonata.WebHome||target="blank"]]50 +* 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 91 91 * Keep making great integrations