Changes for page 202 - New Equilibrium
Last modified by Carlijn Kokkeler on 2024/04/18 13:13
From version 146.1
edited by Carlijn Kokkeler
on 2024/04/18 13:13
on 2024/04/18 13:13
Change comment:
There is no comment for this version
To version 131.1
edited by Erik Bakker
on 2023/08/01 13:48
on 2023/08/01 13:48
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,74 +1,71 @@ 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 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 itemsfrom our hackathon efforts that are now released to you.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. 7 7 8 8 == **Release Properties** == 8 +As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your properties. 9 9 10 - As of this release, we will introduce a new way ofhandling properties forallourclients.This change intends to solidify therelationshipbetween a releaseand a property value. Before, in thecurrent generation architecture, the timing of changing properties was crucial to avoid costly mistakesin Production.Ontop of that,it could have been clearer whether a property valuewasindeed updated as it was not linked to somethingdeployed. These considerations allow us to change the propertymanagement behavior in our next-generation architecture andour current-generation architecture. There are severalfundamental changes compared to the current way of managingyour properties. Most notable among these are:10 +{{info}}For more information please check out the following microlearnings: 11 11 12 -* 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 13 -* 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. 14 -* 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. 15 -* 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. 12 +* 13 +* 14 +* 16 16 17 -{{info}} 18 -For more information, please check out the following microlearnings: 19 - 20 -* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] 21 -* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]] 22 -* [[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"]] 23 - 24 24 Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 25 25 {{/info}} 26 26 27 -== ** Manage - Graphs improvements ~*~* ** == 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. 28 28 29 - As of this release, we will createa condensed viewof yourmetrics when zooming out in theManage phaseraphs. This will significantlyimprovethe performanceof the managed graphs as we retrieve and show less fine-grained information when zoomingout.22 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 30 30 31 -[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]] 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. 32 32 27 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 28 + 33 33 == **Feedback Items** == 34 34 35 -//__Improved editabilitywhentestingineMagiz withoutEdit rightsinCreate__//36 -W ithouteditingrights in theCreatephase,youcouldalreadydoaton thelevel of flowtestsin eMagiz.However,thereweresomeoversightsweshould have noticedduringthe implementation.Thesehavebeen fixed, allowingthosewithouteditrightstochange the test case's namenddescription.31 +//__Improved layout of catalog page in Design__// 32 +We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations. 37 37 38 -//__Improved audit abilityonDeployArchitecture__//39 - To improve theaudibilityofDeployArchitecture,wenowalso logwhensomeone withAdminrights changesspecific functionsonthislevel(i.e., Fixed IP).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. 40 40 41 -//__ Testyour own exported store content__//42 -We have now allowed testingof yourexported worktothestorebeforeitgets approved.This will increasethequalityof storeitems we have, andourpartners have on offerwithin thestore.37 +//__Additional help texts on Design Architecture__// 38 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview. 43 43 44 -{{info}} 45 -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"]] 46 -{{/info}} 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. 47 47 48 -//__ Improvedcomparisonfflows inthereleasesoverview__//49 - Wehave now madeit possibletoseethe differencesintheflow versionsbetweenthetworeleases for allthreepatterns.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. 50 50 51 51 == **Bug Fixes** == 52 52 53 -//__ Improvedvalidation onXPath headerenricher__//54 -To avoid unexpected behavior w henfillingin the XPathheaderenrichercomponent,wehaveimprovedthevalidation on thiscomponent.48 +//__Avoid clicking on other components while deleting another__// 49 +To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer. 55 55 56 -//__ Cancelbehavior on flowtestingpropertyoverviewfixed__//57 -We have ensured thatwhenyou press Cancelwheneditinga property neededina flowtest, theproperty placeholderwill nolongerdisappearfrom the list.51 +//__Improved validation feedback in migrating to the next-generation architecture__// 52 +We have improved the validation feedback when migrating to the next-generation architecture. 58 58 59 -//__ Cancelbehavioronflowfragmentlevelwhenexportingstore content__//60 - Wehave ensuredthatwhenyoupressCancelwhen exportingaflowfragment,theflowfragmentwillnolongerdisappearfrom thelist.54 +//__Make sure that user credentials can be viewed with view rights__// 55 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights. 61 61 62 -//__ Adding numberson containersinDeployArchitecture__//63 - Withthis release,wehavemadethe firststepingivingaclearoverviewofhowmany integrationsfora certainruntime(i.e.,container)arein youractive release.57 +//__Refresh behavior within the deployment plan is fixed__// 58 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. 64 64 65 65 == **Fancy Forum Answers** == 66 66 67 67 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: 68 68 69 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]] 64 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 65 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 66 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]] 70 70 71 -== **Key Takeaways** ==68 +== **Key takeaways** == 72 72 73 73 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: 74 74 ... ... @@ -76,7 +76,7 @@ 76 76 * If you have feedback or ideas for us, talk to the Platypus 77 77 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 78 78 * Clear your browser cache (Ctrl + Shift + Del) 79 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.202 - New Equilibrium.WebHome||target="blank"]]76 +* Check out the release notes [here] 80 80 * Start thinking about how the license tracker can aid your development 81 81 * Start thinking about major, minor, and patch 82 82 * Upgrade to the latest build number ... ... @@ -87,12 +87,6 @@ 87 87 {{info}} 88 88 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 89 89 90 -~*~* Indicates a next-generation-architecture only feature. 91 -{{/info}} 92 -))) 93 - 94 -((( 95 -{{toc/}} 96 -))) 87 +~*~* Indicates a GEN3-only feature. 88 +{{/info}})))((({{toc/}}))){{/container}} 97 97 {{/container}} 98 -{{/container}}