Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 132.1
edited by Erik Bakker
on 2023/08/01 13:50
on 2023/08/01 13:50
Change comment:
There is no comment for this version
To version 611.1
edited by Erik Bakker
on 2024/07/16 14:57
on 2024/07/16 14:57
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 -2 02 -New Equilibrium1 +225 - Pop-up Party - Content
-
... ... @@ -1,82 +1,97 @@ 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 th e lastfew weeks,we havecrossedourt'sand dottedouri's onthereleaseproperties functionality that will impactthedaytodaylifeofeveryuserworkingwithintheplatform.Thefocusofthereleaseblogwill consequentlyalso be onthissubject.Ontop of thatwehave severaladditionalsmallerfeedbackitem comingfrom our hackathonefforts thatarenowreleasedtoyou.6 +**Hi there, eMagiz developers!** In this release, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] 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 6 7 -== ** ReleaseProperties** ==8 -A s of this release, we will introduce a new way of handlingpropertiesfor all our clients. There are several keychanges comparedtothecurrentway of managingyour properties.8 +== **Feedback Items** == 9 +//__Alerting notification settings__// 9 9 10 -{{info}}For more information please check out the following microlearnings: 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. 11 11 12 -* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] 13 -* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]] 14 -* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]] 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 15 16 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 17 -{{/info}} 17 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]] 18 18 19 -== ** Deploy Architecture - Apply To Environment improvements ** == 20 -As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button. 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]] 21 21 22 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 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}} 23 23 24 -== ** Breadcrumb navigation in eMagiz ** == 25 -This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel. 26 26 27 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 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. 28 28 29 -== **Feedback Items** == 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]] 30 30 31 -//__ Improvedlayout ofcatalog page in Design__//32 - We have improvedthelayoutofthe API Catalog overviewinDesignfor our API Gatewayusers. Among others,we haveintroduced a scrollbartoget abetteroverviewof several operations.42 +//__Unused support objects__// 43 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'. 33 33 34 -//__Improved layout of "Edit integration" pop-up for API Gateway integrations__// 35 -Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration. 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. 36 36 37 -//__Additional help texts on Design Architecture__// 38 -We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview. 50 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]] 39 39 40 -//__Improved Audit Trail on several places__// 41 -In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time. 42 - 43 -//__Removed the erroneous alert on message mapping when having a passthrough API__// 44 -This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API. 45 - 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 + 46 46 == **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. 47 47 48 -//__ Avoid clicking on other componentswhile deletinganother__//49 - Toavoidunexpectedbehavior,wenowensure thatnothingcanbeselectedonceyouseethe "deletion"pop-upwhen you want toremove something in the flow designer.61 +//__Namespace update__// 62 +Editing a namespace used in a message definition automatically updates the message definition & transformations. 50 50 51 -//__ Improved validation feedback in migratingtothe next-generation architecture__//52 -We have improvedthevalidationfeedbackwhenmigrating to thenext-generation architecture.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. 53 53 54 -//__M akesure that user credentialscanbeviewedwith viewrights__//55 -Thi srelease makessure that the usercredentialsinDeploycanbe consideredwithviewrights andnotonlywhen havingeditrights.67 +//__SMB inbound channel adapter__// 68 +The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 56 56 57 -//__ Refresh behaviorwithin thedeployment plan is fixed__//58 -Th is releasechangestherefresh behaviorwithinthedeploymentplantoshow, oncemore,the"tobeinstalled" flowsbeforetheuserpresses Execute.70 +//__Heap memory__// 71 +The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 59 59 73 +//__Classpath conflicts__// 74 +We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available. 75 + 60 60 == **Fancy Forum Answers** == 61 61 62 62 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: 63 63 64 -* [[ ReplacingLegacy eMagiz-MendixConnector:MigrationPlan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]65 -* [[ Unknowncharacter(s)doesnotcreateerrormessage.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]66 -* [[ Splitgateway configurationforlocalGEN3gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]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"]] 67 67 68 -== **Key takeaways** ==84 +== **Key Takeaways** == 69 69 70 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:86 +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: 71 71 72 72 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 73 73 * If you have feedback or ideas for us, talk to the Platypus 74 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 90 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 75 75 * Clear your browser cache (Ctrl + Shift + Del) 76 -* Check out the release notes [here] 92 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]] 77 77 * Start thinking about how the license tracker can aid your development 78 78 * Start thinking about major, minor, and patch 79 -* 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,6 +84,11 @@ 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 -~*~* Indicates a GEN3-only feature. 88 -{{/info}})))((({{toc/}}))){{/container}} 102 +{{/info}} 103 +))) 104 + 105 +((( 106 +{{toc/}} 107 +))) 89 89 {{/container}} 109 +{{/container}}