Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 146.1
edited by Erik Bakker
on 2023/08/15 12:16
on 2023/08/15 12:16
Change comment:
There is no comment for this version
To version 473.1
edited by CarlijnKokkeler
on 2024/04/23 12:21
on 2024/04/23 12:21
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 03-FastPaced1 +219 - Creation Carousel - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,49 +1,67 @@ 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!** Wehaveprocessedsome earlyfeedbackonthe releaseproperties in thelastfewweeks.On topofthat, we haveimprovedthe scalabilityofour completesolutionandsolved varioussmaller feedbackitems.6 +**Hi there, eMagiz developers!** This release, we introduce new environment templates for Docker single and double lane. The Moreover, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published. 6 6 7 -== ** ReleaseProperties-Early Feedback** ==8 -Th e communitywell receivedthereleasepropertyfunctionality.However,therewasstill roomfor improvementbased on someoftheearly feedback fromthecommunity.Some ofthese early feedback items havebeenaddressedin thisrelease.As aresult, wehaveupdatedthelayout of a property'seditscreenandourchecksonnestedpropertiestoavoidmissingproperties.8 +== **Environment Template R13 Docker - Single Lane** == 9 +This release introduces a new non-service affecting environment template for all our customers running in a single-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Single Lane.WebHome||target="blank"]]. 9 9 11 +== **Environment Template R15 Docker - Double Lane** == 12 +This release introduces a new non-service affecting environment template for all our customers running in a double-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R15 Docker - Double Lane.WebHome||target="blank"]]. 13 + 10 10 == **Feedback Items** == 11 11 12 -//__ "Allentries"arenowcleaned up as partof the migration__//13 - Toavoid problemswhenremovingintegrationsaftermigrating towardthenext-generationarchitecture,we now clean upthe "all-entries"aspartof themigrationtowardsthenext-generation architecture.16 +//__eMagiz Mendix connector__// 17 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 14 14 15 -//__ TriggerID added to ouralertingon thenext-generation architecture__//16 - We added a uniquetrigger ID to eachalert configuration to make theinterpretationfor oursupportdeskmuch easierandmoremanageable.19 +//__Improved OpenAPI import__// 20 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 17 17 18 -//__Improved performance Manage Dashboards__// 19 -We have improved the efficiency with which we retrieve the data that is shown in the Manage Dashboards for the next-generation architecture. 20 - 21 21 == **Bug Fixes** == 23 +//__Error handling__// 24 +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. 22 22 23 -//__ Ensure noflow can be in arelease twice__//24 - We have fixed a bug that couldcauseoneflowtoendup in the same releasewithtwo differentflow versions.Asthis will breakyour solution on various occasions, we fixedthis.26 +//__Volume mapping passwords__// 27 +Passwords for network volumes are hidden on the machine after deployment. 25 25 26 -//__ Ensureno flow can be ina releasetwice__//27 -W ehavefixedabugthatcould cause oneflow to end up in the samereleasewithtwo differentflow versions.Asthiswill breakyoursolutionon variousoccasions,wefixed this.29 +//__Create integration removal__// 30 +When removing an integration from Create, the Create phase is correctly updated as well. 28 28 32 +//__Legacy statistics__// 33 +Legacy pages are now correctly hidden when running on the current runtime architecture. 34 + 35 +//__Unused properties__// 36 +Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore. 37 + 38 +//__Enumeration values__// 39 +Enumeration values for event processors can now be edited in Create. 40 + 41 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 42 + 43 +//__SFTP sessions__// 44 +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. For this, a new [[image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released. 45 + 29 29 == **Fancy Forum Answers** == 30 30 31 31 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: 32 32 33 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 50 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]] 51 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]] 52 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]] 34 34 35 -== **Key takeaways** ==54 +== **Key Takeaways** == 36 36 37 -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:56 +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: 38 38 39 39 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 40 40 * If you have feedback or ideas for us, talk to the Platypus 41 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 60 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 42 42 * Clear your browser cache (Ctrl + Shift + Del) 43 -* Check out the release notes [here] 62 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]] 44 44 * Start thinking about how the license tracker can aid your development 45 45 * Start thinking about major, minor, and patch 46 -* Upgrade to the latest build number 47 47 * Keep making great integrations 48 48 49 49 Let's stay in touch and till next time! ... ... @@ -51,6 +51,11 @@ 51 51 {{info}} 52 52 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 53 53 54 -~*~* Indicates a next-generation-architecture only feature. 55 -{{/info}})))((({{toc/}}))){{/container}} 72 +{{/info}} 73 +))) 74 + 75 +((( 76 +{{toc/}} 77 +))) 56 56 {{/container}} 79 +{{/container}}