Changes for page 201 - Be Informed
Last modified by Carlijn Kokkeler on 2024/04/18 13:13
From version 123.1
edited by Erik Bakker
on 2023/06/08 08:11
on 2023/06/08 08:11
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 (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -1 99-Home Improvements1 +201 - Be Informed - Content
-
... ... @@ -2,43 +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 improvingvariousaspectsofourhome.Amongotherswehaveimprovedthe logging,alerting, andsecurityofour next-generationarchitecture. On top of that we haveimprovedthe innerworkingsoftheeand thecertificate managementforhoseofususing theEventStreamingpattern.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 - //__Enhancedoverview oftheHTTPStatistics__//10 -As of now all resourcesthathavebeen calledatleast oncesincedeploying themwillnowshow upintheleft-bottomgraphofthe HTTP Statistics. This willmakeiteasier toseewhetheraparticularoperationwas calledwithinatimeframe.Ontopofthat it makes comparingdataon variousoperations easier. In here youcan also filter on one (bypressingthe+ icon) ormore by clicking onthefilter icon.In caseyouwanttosort the table ina differentmanner you canclick on the name of the column on whichyouwantsort.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 -//__Reason why runtime cannot start is now in the vast majority of cases reported back__// 13 -In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup. 13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 14 14 15 -{{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}} 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 -//__Forced congestion control__// 18 -To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform. 18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 19 19 20 -//__Unused images are cleaned up__// 21 -This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan. 20 +== **Feedback Items** == 22 22 23 -== **Store Improvements** == 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. 24 24 25 -//__Improved importingbehaviorforspecificusecases__//26 - Before,itcouldhappen thatacertain placeholderthatcontainedan asteriskwereimportedincorrectly.Thisas nowbeenfixed tosurethat thecorrect importbehavioris experiencedbyusers.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. 27 27 28 -//__ Fixedbugin creatingamessage mappingontopof an imported system message__//29 - Itisnowpossbile tocreateamessagemappingtoanimportedsystemmessagefromthestore.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. 30 30 31 -== **Event Streaming - Certificate Management** == 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. 32 32 33 -//__ Expiredcertification notification__//34 - Asof now wehave functionality in placethat will inform you (and us) whena client certificatef an EventStreaminguseris going to expire within the upcoming three months.This way you can takeactionearlyon andreportback that theupdatewas succesfull sowe canrevoke the expiringclientcertificate accordingly.Ifyouwantspecific information on thisplease reach outto us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].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. 35 35 37 +== **Bug Fixes** == 38 + 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. 41 + 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. 44 + 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. 47 + 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. 50 + 36 36 == **Fancy Forum Answers** == 37 37 38 38 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: 39 39 40 -* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]] 41 -* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||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"]] 42 42 43 43 == **Key takeaways** == 44 44