Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 143.1
edited by Erik Bakker
on 2023/08/07 09:56
on 2023/08/07 09:56
Change comment:
There is no comment for this version
To version 469.1
edited by CarlijnKokkeler
on 2024/04/23 11:34
on 2024/04/23 11:34
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 02-New Equilibrium1 +219 - Creation Carousel - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,79 +1,71 @@ 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 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.6 +**Hi there, eMagiz developers!** 6 6 7 -== ** ReleaseProperties** ==8 - Asof this release,we will introduce a newwayofhandlingpropertiesfor all our clients.This changeintendstosolidify therelationship betweena releaseand a property value.Before,inthecurrentgenerationarchitecture,thetimingofchangingpropertieswas crucialtoavoid costly mistakesin Production.Ontopofthat, it couldhavebeenclearer whethera property valuewasindeedupdated asit was not linkedto something deployed.Theseconsiderations allowusto changetheproperty managementbehaviorinournext-generationarchitectureandourcurrent-generationarchitecture.Thereareseveralfundamental changes comparedtothe current wayof managing yourproperties.Mostnotable among theseare:8 +== **Environment Template R13 Docker - Single Lane** == 9 +TBD This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R12 Docker - Single Lane.WebHome||target="blank"]]. 9 9 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, 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. 11 +== **Environment Template R15 Docker - Double Lane** == 12 +TBD This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R14 Docker - Double Lane.WebHome||target="blank"]]. 14 14 15 -{{info}}For more information, please check out the following microlearnings: 16 16 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"]] 20 20 21 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 22 -{{/info}} 23 - 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. 26 - 27 -[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]] 28 - 29 29 == **Feedback Items** == 17 +//__Machine agents__// 18 +We have added functionality that allows the user to (auto-) update their external (on-premise) machine agents from the portal. Please find out more HERE. 30 30 31 -//__ Improved editability when testing in eMagizwithout Editrights inCreate__//32 -W ithouteditingrights in theCreate phase, you could alreadydo a lot onthelevelofflowtests in eMagiz.However, there were some oversightswe should havenoticed duringthe implementation.These have been fixed, allowingthose without editrightstochangethetest case'sname anddescription.20 +//__eMagiz Mendix connector__// 21 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 33 33 34 -//__Improved auditability onDeploy Architecture__//35 -T o improve the audibilityof Deploy Architecture,wenowalso log when someonewith Adminrightschangesspecific functions onthislevel(i.e.,Fixed IP).23 +//__Improved OpenAPI import__// 24 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 36 36 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. 26 +== **Bug Fixes** == 27 +//__Error handling__// 28 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this. 39 39 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}} 30 +//__Volume mapping passwords__// 31 +Passwords for network volumes are hidden on the machine after deployment. 41 41 42 -//__ Improved comparisonof flowsinthereleasesoverview__//43 -W ehavenowmadeit possibleto see the differencesintheflow versionsbetweenthetworeleasesforall threepatterns.33 +//__Create integration removal__// 34 +When removing an integration from Create, the Create phase is correctly updated as well. 44 44 45 -== **Bug Fixes** == 36 +//__Legacy statistics__// 37 +Legacy pages are now correctly hidden when running on the current runtime architecture. 46 46 47 -//__ Improvedvalidation on XPath headerenricher__//48 - To avoidunexpectedbehavior whenfillingintheXPath headerenrichercomponent,we haveimprovedthe validationon this component.39 +//__Unused properties__// 40 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore. 49 49 50 -//__ Cancel behavior onflow testing property overview fixed__//51 - We have ensured thatwhenyoupressCancelwheneditingapropertyneededina flowtest,theproperty placeholderwillnolongerdisappear fromthelist.42 +//__Enumeration values__// 43 +Enumeration values for event processors can now be edited in Create. 52 52 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. 45 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 55 55 56 -//__ Addingnumberson containersin Deploy Architecture__//57 - Withthisrelease,wehavemade thefirst stepingivinga clear overviewofhowmanyintegrationsforacertainruntime(i.e.,container)are inyour activerelease.47 +//__SFTP sessions__// 48 +SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. Please find out more HERE. 58 58 59 59 == **Fancy Forum Answers** == 60 60 61 61 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: 62 62 63 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 54 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 55 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 56 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 64 64 65 -== **Key takeaways** ==58 +== **Key Takeaways** == 66 66 67 -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:60 +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: 68 68 69 69 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 70 70 * If you have feedback or ideas for us, talk to the Platypus 71 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 64 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 72 72 * Clear your browser cache (Ctrl + Shift + Del) 73 -* Check out the release notes [here] 66 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]] 74 74 * Start thinking about how the license tracker can aid your development 75 75 * Start thinking about major, minor, and patch 76 -* Upgrade to the latest build number 77 77 * Keep making great integrations 78 78 79 79 Let's stay in touch and till next time! ... ... @@ -81,6 +81,11 @@ 81 81 {{info}} 82 82 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 83 83 84 -~*~* Indicates a next-generation-architecture only feature. 85 -{{/info}})))((({{toc/}}))){{/container}} 76 +{{/info}} 77 +))) 78 + 79 +((( 80 +{{toc/}} 81 +))) 86 86 {{/container}} 83 +{{/container}}