Changes for page 207 - Aligned State
Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 107.1
edited by Erik Bakker
on 2023/04/25 16:36
on 2023/04/25 16:36
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 -1 96-TheLast Post1 +201 - Be Informed - Content
-
... ... @@ -2,63 +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 work hard on i mprovingournextgeneration architectureand introducedthe"live" modewithinourflow testingfunctionality.Furthermorethereareloadsofsmallerfeedbackitems and bugsthathave beenresolved withthisrelease.So withoutfurtheradolet usdiveintoall we haveto offer.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 -== **"Live" mode on flow testing** == 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]]. 8 8 9 -With this release we bring an improved version of the flow testing functionality. As of now you will have the option to switch between "live" and "mock" mode will running a flow test. The "mock" mode is the mode you are used to from us. In this mode all external communication is mocked by the system and only the functional process can be tested. 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. 10 10 11 - By switching to "live"mode you can not only test the functional process but also thecommunication to the externalsystem. You can doso byenteringthe "edit" mode of the flow test and toggleetween "mock" and "live"mode. When doing soeMagiz willshow you thefollowingop-up stressing the consequences of youractions.13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 12 12 13 -[[image:Main.Images.Release Blog.WebHome@196-release-blog--live-flow-testing-pop-up.png]] 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. 14 14 15 - Once confirmed you willseethat the userinterfacenow indicates thatthe endpoint is in "live"mode.18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 16 16 17 - [[image:Main.Images.ReleaseBlog.WebHome@196-release-blog--live-flow-testing-result.png]]20 +== **Feedback Items** == 18 18 19 -== **3rd generation 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 of several operations. 20 20 21 -//__ EventStreaming statisticscompletion__//22 - In thisrelease,wehave updated theretrievalofdata toensurethat for all models, all environments andall topicsthisdatacanbe shownto theusersotheycan properlymonitor theenvironment.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. 23 23 24 -//__ Deployments onnextgenerationarchitecture__//25 - This releasefixesseveralsmaller bugsandaddsseveralimprovements to thedeployment processofthenextgenerationarchitecture.28 +//__Additional help texts on Design Architecture__// 29 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview. 26 26 27 -//__ Cleanqueuesoption__//28 - Thisreleaseintroducesanoptionfor**admins**to cleanqueuesthatremainedafteramigrationtowards the next generationruntimearchitecture. Thiswill makeheoverviewofwhichqueuesare"problematic"amuchmore realisticoverview.31 +//__Improved Audit Trail on several places__// 32 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time. 29 29 30 -== **Feedback items ** == 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. 31 31 32 -//__On-premise containers are started upon slot wakeup__// 33 -With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning. 37 +== **Bug Fixes** == 34 34 35 -//__ Resourcepathisshowntotheuser__//36 - Youcan now, withoutownloading,seetheresourcepath ofaresourcebyviewingthemetadataoftheresource.You candoso by pressingthe "eye"icon to viewthisformation.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. 37 37 38 -//__ Flowdesignerimprovements__//39 -W ith this releasevarious improvementshavebeen made to the flow designer. Among others we have improved theoverview of whatan"unused resource"is. You nowavethe optionto define certainresourcesthat areused but cannot beauto-detected by eMagiz to bean"used"resourceto avoidconfusion.42 +//__Improved validation feedback in migrating to the next-generation architecture__// 43 +We have improved the validation feedback when migrating to the next-generation architecture. 40 40 41 -//__ Improvedcapabilitiesofa companycontact__//42 - Withthis releasewe haveimprovedthe capabilitiesof acompany contact. Asofnowyoucanalsoadd userstomodelsbelongingosubcompaniesbelow yourthecompanytowhich you arethe companycontact.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 considered with view rights and not only when having edit rights. 43 43 44 -== **Bug fixes ** == 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. 45 45 46 -//__Optional API parameters are handled correctly__// 47 -Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box. 48 - 49 -//__Without CDM rights nothing related to any data model can be edited anymore__// 50 -With this release, we have made sure that nothing related to any data model can be edited without having the proper rights. 51 - 52 -//__Improved sorting of Design and Deploy archticture__// 53 -With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views. 54 - 55 55 == **Fancy Forum Answers** == 56 56 57 57 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: 58 58 59 -* [[ jsonPathinSpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]60 -* [[ ConnectingtoAzureSQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]61 -* [[ Changes to JSON apikeep breaking mymodel validation,although they areirrelevanttome>>https://my.emagiz.com/p/question/172825635703415225||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"]] 62 62 63 63 == **Key takeaways** == 64 64