Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 136.1
edited by Erik Bakker
on 2023/08/01 14:12
on 2023/08/01 14:12
Change comment:
There is no comment for this version
To version 470.1
edited by CarlijnKokkeler
on 2024/04/23 12:06
on 2024/04/23 12:06
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,84 +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 additional smaller feedback item coming from our hackathon efforts that are now released to you.6 +**Hi there, eMagiz developers!** 6 6 7 -== ** ReleaseProperties** ==8 - As of this release,we will introduce a newway of handling propertiesforall our clients. This changeintends to solidify therelationship betweena releaseand a propertyvalue.Before,in thecurrentgenerationarchitecture, timing of changingpropertieswascrucialtoavoidcostlymistakesonProduction. Ontopofthat it was not always clear whether aproperty value was indeedupdated asitwas not linked to somethingthatwasdeployed. Theseconsiderationsletus to changethe property managementbehaviornot onlyonournext-generation architecturebutalso onour currentgenerationarchitecture. Having said that, thereareseveralkey changes comparedtothe current wayof managing yourproperties.Mostnotablyamong theseare: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 cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 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. This to avoid mistakes when filling them in. 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 a completely new release in Test and promote it to the Production environment. 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 cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R15 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 - Next generation 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 manage 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 eMagizwihout Editrights inCreate__//32 -W ithout havingeditrights in theCreate phaseyou could alreadydo a lot onthelevelofflowtests in eMagiz.However,there were someoversightswe missed duringthe implementation.These have been fixed allowingthose without editrightstonowalsochange the name anddescription of thetest case.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 audtiabilityon Deploy Architecturewenowalso 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 work__// 38 -We have now made it possible to test your own 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 -//__ ImprovedAuditTrailonseveralplaces__//43 - Inseveralplacesintheportal,wehaveimprovedthe audittrailtospecifybetter who changedwhatatwhich point in time.33 +//__Create integration removal__// 34 +When removing an integration from Create, the Create phase is correctly updated as well. 44 44 45 -//__ Removed the erroneousalerton message mapping when having a passthrough API__//46 - This releaseremovestheerroneousalertpeople reportedon"errors in messagemapping" fora passthrough API.36 +//__Legacy statistics__// 37 +Legacy pages are now correctly hidden when running on the current runtime architecture. 47 47 48 -== **Bug Fixes** == 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 -//__ Avoid clicking on other components while deletinganother__//51 - To avoid unexpected behavior, wenowensurethat nothingcan beselectedonceyouseethe "deletion"pop-up whenyouwantto removesomething intheflowdesigner.42 +//__Enumeration values__// 43 +Enumeration values for event processors can now be edited in Create. 52 52 53 -//__Improved validation feedback in migrating to the next-generation architecture__// 54 -We have improved the validation feedback when migrating to the next-generation architecture. 45 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 55 55 56 -//__ Makesurethat user credentialscan be viewed with view rights__//57 -T hisreleasemakes sure that theusercredentialsinDeploy canbeconsideredwithviewrightsandnot onlywhenhavingedit rights.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 -//__Refresh behavior within the deployment plan is fixed__// 60 -This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. 61 - 62 62 == **Fancy Forum Answers** == 63 63 64 64 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: 65 65 66 -* [[ Replacing LegacyeMagiz-MendixConnector:MigrationPlan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]67 -* [[ Unknown character(s)does notcreate errormessage.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]68 -* [[ Split gateway configurationforlocalGEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||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"]] 69 69 70 -== **Key takeaways** ==58 +== **Key Takeaways** == 71 71 72 -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: 73 73 74 74 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 75 75 * If you have feedback or ideas for us, talk to the Platypus 76 -* 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. 77 77 * Clear your browser cache (Ctrl + Shift + Del) 78 -* Check out the release notes [here] 66 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring.WebHome||target="blank"]] 79 79 * Start thinking about how the license tracker can aid your development 80 80 * Start thinking about major, minor, and patch 81 -* Upgrade to the latest build number 82 82 * Keep making great integrations 83 83 84 84 Let's stay in touch and till next time! ... ... @@ -86,6 +86,11 @@ 86 86 {{info}} 87 87 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 88 88 89 -~*~* Indicates a GEN3-only feature. 90 -{{/info}})))((({{toc/}}))){{/container}} 76 +{{/info}} 77 +))) 78 + 79 +((( 80 +{{toc/}} 81 +))) 91 91 {{/container}} 83 +{{/container}}