Changes for page 201 - Be Informed
Last modified by Carlijn Kokkeler on 2024/04/18 13:13
From version 127.1
edited by Samet Kaya
on 2023/06/20 13:14
on 2023/06/20 13:14
Change comment:
There is no comment for this version
To version 129.1
edited by Erik Bakker
on 2023/07/17 15:10
on 2023/07/17 15:10
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 -20 0-UnchartedTerritories1 +201 - Be Informed - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. SametKaya1 +XWiki.ebakker - Content
-
... ... @@ -2,52 +2,59 @@ 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 worked hard on alot of thingsthat are unfortunatelynotquitereadytobereleased.As aresulttheoutputofthis releaseislimited.Havingsaidthat we stillbringsomekeyimprovementsintheDeployandManage phase thatwouldmakelifemucheasier.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 last 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 -== **Next generation improvements and bug fixes** == 7 +== **Announcement - Release Properties** == 8 +As of the next release (202) we will introduce a completely 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 contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 8 8 9 - //__Enhancedright-handview withinDeploymentPlancontext__//10 - Whenexecutingyourdeployment planwe will showspecific logentries oftheinfocategorythatindicatethatacontainer(i.e.runtime)has startedupcorrectly.Ontopofthatweshowthe warningsanderrorsverview.10 +== ** Deploy Architecture - Apply To Environment improvements ** == 11 +As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button. 11 11 12 - {{info}}Note that when the JMS containergetsrestarted connection errorsin the logs area normal thing to witness so keep youryespeeled for the startupgging on JMS level to gain confidence inthedeployment.{{/info}}13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 13 13 14 - //__Improved timeoutsettingswhen deploying__//15 - To avoidmismatchesbetweenvariousparts ofthe infrastructurewe have improvedthe timeoutconfiguration on certaindeploymentplan stepsto reducethechance thatthesemismatchesoccur.15 +== ** Breadcrumb navigation in eMagiz ** == 16 +With this release we introduce the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed, and have impact, in the Create phase when you are checking out your transformation or system message on flow level. Apart from there the navigation is implemented consistently across the portal for a unified look and feel. 16 16 17 - {{info}}Note that this fix is part of a new runtime imagefor the current-generationruntimes.Thereleasenotes of this canbe found [[here>>doc:Main.ReleaseInformation.RuntimeImages.WebHome||target="blank"]]{{/info}}18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 18 18 19 -//__Detailed HTTP Statistics now show user info in specific additional cases__// 20 -To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations. 20 +== **Feedback Items** == 21 21 22 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 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 when having several operations. 23 23 24 -//__Improved l oadingspeedofManageDashboard__//25 - Thisreleaseimprovesthe loadingspeed withwhichallthe dashboards inManageareshownto theuser. This will enhancetheuserexperiencewithintheManagephase.25 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__// 26 +As of now the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration. 26 26 27 -== **Store Improvements** == 28 +//__Additional help texts on Design Architecture__// 29 +We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview. 28 28 29 -//__Imp ortinginDesignisimproved__//30 - Wehavesolvedabugthatcouldcauseissues whenimporting somethinginDesignwhiletheaccompanyingintegrationwasnotyetinCreate.31 +//__Improved Audit Trail on several places__// 32 +In several places in the portal we have improved the audit trail to better specify who changed what at which point in time. 31 31 34 +//__Removed the erroneous alert on message mapping when having a passthrough API__// 35 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API. 36 + 32 32 == **Bug Fixes** == 33 33 34 -//__ Deprecatedreminderpop-upremoved__//35 - Wehaveremoveda reminderpop-upon apending cloudtemplateasit was deprecatedandcouldcause issueswhen usingitincommunicationwithothersystems.39 +//__Avoid clicking on other components while deleting another__// 40 +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. 36 36 37 -//__Improved selectionarea inFlowDesigner__//38 -Whe nworkingonaargeflowyou cannowselectspecificareaseasilywhileyou arescrolleddownfurtherdowntheflow.42 +//__Improved validation feedback in migrating to the next-generation architecture__// 43 +We have improved several things with regards to the validation feedback when migrating to the next-generation architecture. 39 39 40 -//__ ImprovedKafkasettings__//41 - For all flowsthat use aKafkarelatedcomponentwithintheflow designerwewillrun a migrationtoupdateeverysingleoneofthemto thenewbest practices andcreateanew flow versionforthem.45 +//__Make sure that user credentials can be viewed with view rights__// 46 +This release makes sure that the user credentials in Deploy can be viewed with view rights and not only when having edit rights. 42 42 43 -{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}} 48 +//__Refresh behavior within the deployment plan is fixed__// 49 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute. 44 44 45 45 == **Fancy Forum Answers** == 46 46 47 47 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: 48 48 49 -* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]] 50 -* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]] 55 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]] 56 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]] 57 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]] 51 51 52 52 == **Key takeaways** == 53 53