Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 610.1
edited by Erik Bakker
on 2024/07/16 14:55
on 2024/07/16 14:55
Change comment:
There is no comment for this version
To version 140.1
edited by Erik Bakker
on 2023/08/01 14:29
on 2023/08/01 14:29
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -22 5-Pop-upParty1 +202 - New Equilibrium - Content
-
... ... @@ -1,97 +1,79 @@ 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!** In th is release,anew[[runtimeimage>>doc:Main.ReleaseInformation.Runtime Images.V311.WebHome||target="blank"]]willbe available,includingchangesto ourinfinispancachemanager,SMB inboundchannel adapter,andheapmemoryconfiguration.Moreover, we havemadeprogress on our alertingimprovement plans andhaveimprovedandadded several pop-upscreens.Find out allwereleasedbelow!5 +**Hi there, eMagiz developers!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day-to-day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that, we have several smaller feedback items from our hackathon efforts that are now released to you. 7 7 8 -== ** FeedbackItems** ==9 - //__Alerting notification settings__//7 +== **Release Properties** == 8 +As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are: 10 10 11 -//__Process containers__// 12 -If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern. 10 +* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases 11 +* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration. 12 +* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers. 13 +* A, for most, a new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment. 13 13 14 -//__Design settings__// 15 -When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment. 15 +{{info}}For more information, please check out the following microlearnings: 16 16 17 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]] 17 +* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] 18 +* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]] 19 +* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]] 18 18 19 -//__Untested images__// 20 - 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. 21 - 22 -[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]] 23 - 24 -{{warning}} 25 -The following restrictions apply to this functionality: 26 - 27 -* When accepting the risk you accept the risk for the **whole** model. 28 -* If any release based on the same runtime image is already activated on Acceptance you will **not** be warned.{{/warning}} 21 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 22 +{{/info}} 29 29 24 +== ** Manage - Graphs improvements ~*~* ** == 25 +As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out. 30 30 31 -//__Infinispan Cache Manager__// 32 -We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 33 - 34 -//__Infinispan Cache Manager error message__// 35 -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>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 27 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]] 36 36 37 -//__Flow bump__// 38 -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. 39 - 40 -[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]] 29 +== **Feedback Items** == 41 41 42 -//__ Unused supportobjects__//43 - Support objects arenow shown in twosections,namely'Support objects'and'Unused supportobjects'.31 +//__Improved editability when testing in eMagiz without Edit rights in Create__// 32 +Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description. 44 44 45 -[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]] 46 - 47 -//__Deleting routes__// 48 -For clarity purposes, a confirmation pop-up will be shown when deleting routes. 34 +//__Improved auditability on Deploy Architecture__// 35 +To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP). 49 49 50 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]] 37 +//__Test your own exported store content__// 38 +We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store. 51 51 52 -//__Debug queue__// 53 -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. 54 - 55 -[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]] 56 - 57 -== **Bug Fixes** == 58 -//__Internal server error__// 59 -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. 40 +{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}} 60 60 61 -//__ Namespaceupdate__//62 - Editinga namespaceusedina messagedefinitionautomaticallyupdates themessagedefinition&transformations.42 +//__Improved comparison of flows in the releases overview__// 43 +We have now made it possible to see the differences in the flow versions between the two releases for all three patterns. 63 63 64 -//__Error pop-up__// 65 -We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows. 45 +== **Bug Fixes** == 66 66 67 -//__ SMBinboundchanneladapter__//68 -T heSMB inboundchannel adapterfailed toretrievefileswhenthe remote directorypointedtoapathwithmultipledirectoriesinit, unless they wereseperatedwith '}}' insteadof '{{/'. This has beenresolved,meaningthat remotedirectories that contain multiple folders in its path can(and should) contain'/' again. Forthis,a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.47 +//__Improved validation on XPath header enricher__// 48 +To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component. 69 69 70 -//__ Heapmemory__//71 - Theinitialcommitted heapmemoryofruntimeshasbeenloweredtobettermatchactualusage. Forthis,a new[[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V311.WebHome||target="blank"]]isavailable.50 +//__Cancel behavior on flow testing property overview fixed__// 51 +We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list. 72 72 73 -//__C lasspathconflicts__//74 -We updatedtransitiveruntimedependenciesto preventpotentialconflictson theclasspathforextended images. Forthis,a new[[runtimeimage>>doc:Main.ReleaseInformation.RuntimeImages.V311.WebHome||target="blank"]]isavailable.53 +//__Cancel behavior on flow fragment level when exporting store content__// 54 +We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list. 75 75 56 +//__Adding numbers on containers in Deploy Architecture__// 57 +With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release. 58 + 76 76 == **Fancy Forum Answers** == 77 77 78 78 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: 79 79 80 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 81 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 82 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 63 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 83 83 84 -== **Key Takeaways** ==65 +== **Key takeaways** == 85 85 86 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:67 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 87 87 88 88 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 89 89 * If you have feedback or ideas for us, talk to the Platypus 90 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 71 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 91 91 * Clear your browser cache (Ctrl + Shift + Del) 92 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]73 +* Check out the release notes [here] 93 93 * Start thinking about how the license tracker can aid your development 94 94 * Start thinking about major, minor, and patch 76 +* Upgrade to the latest build number 95 95 * Keep making great integrations 96 96 97 97 Let's stay in touch and till next time! ... ... @@ -99,11 +99,6 @@ 99 99 {{info}} 100 100 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 101 101 102 -{{/info}} 103 -))) 104 - 105 -((( 106 -{{toc/}} 107 -))) 84 +~*~* Indicates a GEN3-only feature. 85 +{{/info}})))((({{toc/}}))){{/container}} 108 108 {{/container}} 109 -{{/container}}