Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 56.1
edited by Erik Bakker
on 2022/12/06 14:58
on 2022/12/06 14:58
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 89-PrivateEye1 +201 - Be Informed - Content
-
... ... @@ -2,71 +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!** Ourrelease ofthePrivatestorefunctionality characterizesthis release.This functionality allows someusers to export content toaprivatestorethatisonlyaccessible within the companyandcouldbepublishedto thepublicstore ofeMagiz. On top of that,weresolvedsomeofthelimitationson the 3rd generationruntime. Furthermore,someminorfixesandbetafeatureswillbereleasedtothe community.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 -== ** PrivateStore** ==8 - Ontop ofour generaltore,inwhicheMagizcurrently publishesStore contentrelevanttoboth theDesignandCreatephasesofeMagiz,we haveaddedthe privateorefunctionality.Thisstoreworkspreciselythesameasthegeneral store.However,only usersbelongingto thesame companyas theexportercanimport thestorentent (afteritis approved).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]]. 9 9 10 -{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/warning}} 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 - == **3rdgenerationruntime bolstering** ==13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]] 13 13 14 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal. 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. 15 15 16 -//__SOAP and REST web services migration including splitting them__// 17 -With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime and at the same time you can directly split the all-entry to get rid of that construction alltogether. A specific migration path for this will be published in the documentation portal. 18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]] 18 18 19 -//__Changing SSL settings for 3rd generation runtime models works__// 20 -As with the current runtime architecture, you can now also change the SSL settings if needed for a model running in the 3rd generation runtime. 20 +== **Feedback Items** == 21 21 22 -//__Improved migrationfor JMSflows__//23 - This releasewill improve themigrationofJMSflowswhenmigratingto3rd generation runtime.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 -{{warning}}If you already migrated your JMS flow you should execute a "Reset" action on JMS level to get these changes in your model{{/warning}} 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 -//__ Removedthe ability todd"Debug components"toa flow runningin the3rdgenerationruntime architecture__//28 - Asof this release,you cannot add debug components anymoreon a flow that is alreadymigratedto the3rd generationruntime. Thissbecause this functionality will notworkinthe3rd generationruntimedwouldbreakyourflow.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. 29 29 30 -//__ Deploymentplan isupdatedcorrectlywhencompletly migrated to the 3rd generationruntimearchitecture__//31 - Wehavefixeda bugthat generatedanincorrectdefaultdeploymentplanonceyou were fullymigrated tothe3rd generationruntime.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 -== **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. 34 34 35 - Wehave also solved other feedback items besides the flow designer'scritical updates.37 +== **Bug Fixes** == 36 36 37 -//__ ImprovednamingconventiononStorerelatedpages__//38 - Wehaveimprovedvariousdisplay namesto ensure thatitsclearfromthe namingthatstorecontentcanbeimplementedinallintegrationpatterns.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. 39 39 40 -//__ Press"Enter" tosearchon multiplepages__//41 - Inour DaemonSwitchrelease, weddedfunctionality thatallowed you to press**Enter** tosearch ontheproperty overview page. Thisreleasehas addedthis functionalitytomany morepages acrosstheportal.Theompletelist is as follows.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. 42 42 43 -* Deploy → Deployment Plan 44 -* Deploy → Properties → History 45 -* Deploy → User Management → Roles 46 -* Manage → Error Messages → Error Messages 47 -* Manage → Error Messages → Flows with Error Messages 48 -* Manage → Error Messages → Exceptions of Error Messages 49 -* Manage → Log Entries 50 -* Manage → Alerts 51 -* Manage → Triggers 52 -* Manage → Tags – Cant find (only Gen2) 53 -* Manage → Notifications 54 -* Manage → Notification Settings 55 -* Manage → Data Usage → History 56 -* Manage → Code mappings → All tabs 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. 57 57 58 -== **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. 59 59 60 -//__Loading problems of Deployment plan execution overview__// 61 -We have fixed a problem that could cause issues when trying to show the deployment plan execution overview after pressing the Deploy button in Deploy -> Releases. 62 - 63 63 == **Fancy Forum Answers** == 64 64 65 65 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: 66 66 67 -* [[ Synchronousfile pick-up>>https://my.emagiz.com/p/question/172825635703197660||target="blank"]]68 -* [[ Receivinge-mail viaIMAPorPOP3 - Setup>>https://my.emagiz.com/p/question/172825635703197881||target="blank"]]69 -* [[ Best way ofReceivingnd SendingMail>>https://my.emagiz.com/p/question/172825635703210149||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"]] 70 70 71 71 == **Key takeaways** == 72 72