Changes for page 204 - Found It
Last modified by Carlijn Kokkeler on 2024/04/18 13:12
From version 134.1
edited by Erik Bakker
on 2023/08/01 14:11
on 2023/08/01 14:11
Change comment:
There is no comment for this version
To version 130.1
edited by Erik Bakker
on 2023/07/17 15:13
on 2023/07/17 15:13
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 -20 2-NewEquilibrium1 +201 - Be Informed - Content
-
... ... @@ -2,43 +2,32 @@ 2 2 {{container layoutStyle="columns"}}((( 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 crossedour t'sanddotted our i's onthe release properties functionalitythatwill impacttheday todaylife of every user working withintheplatform. Thefocus of the release blog will consequently alsobe on thissubject. On top of that we have severaladditionalsmallerfeedbackitemcomingfromour hackathon efforts that are nowreleasedto you.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the previous Q. More on that later. On top of that, we have several smaller items as a result of our hackathon efforts to present to you. 6 6 7 -== **Release Properties** == 8 -As of th isrelease, we will introduce a new way of handling properties for all our clients.This changeintendstosolidifytherelationshipbetweenareleaseanda property value.Before, in the current generationarchitecture, timingof changingproperties was crucialtoavoidcostly mistakesonProduction.On topofthatit wasnotalways clearwhetheraproperty value wasindeed updated asit wasnotlinkedto somethingthatwasdeployed. Theseconsiderationslet us to change theproperty managementbehavior not onlyon ournext-generation architecturebutalso onour currentgenerationarchitecture. Havingsaidthat,thereareseveralkeychangescomparedto thecurrentwayofmanaging your properties.Mostnotablyamong theseare:7 +== **Announcement - Release Properties** == 8 +As of the next release (202), we will introduce a new way of handling properties for all our clients. In the upcoming weeks, we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 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. 10 +== ** Deploy Architecture - Apply To Environment improvements ** == 11 +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. 14 14 15 - {{info}}Formoreformation pleasecheckout thefollowingmicrolearnings:13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 16 16 17 -* [[Property Management>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new||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"]] 15 +== ** Breadcrumb navigation in eMagiz ** == 16 +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. 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}} 18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 23 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** == 30 30 31 -//__Improved editabilitywhentestingin eMagizwihoutEdit rightsCreate__//32 -W ithouthavingeditrights in the Createphase youcouldalreadydoaton thelevel of flowtestsin eMagiz.However,thereweresomeoversightswemissed during theimplementation.These havebeen fixed allowingthosewithouteditrightstonowalsochangethenameand descriptionof the test case.22 +//__Improved layout of catalog page in Design__// 23 +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. 33 33 34 -//__Improved audit abilityonDeployArchitecture__//35 - To improve theaudtiabilityonDeployArchitecture wenowalso logwhensomeone withAdminrights changesspecific functionsonthislevel(i.e. Fixed IP).25 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__// 26 +Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration. 36 36 37 -//__ Testyour own exportedwork__//38 -We have now madeitpossible to testyour ownexported worktotheStorebeforeitgets approved.This will increasethequalityof storeitems we have, andourpartners, have on offerwithin thestore.28 +//__Additional help texts on Design Architecture__// 29 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview. 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}} 41 - 42 42 //__Improved Audit Trail on several places__// 43 43 In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time. 44 44