Skip to Content

Changes for page 201 - Be Informed

Last modified by Carlijn Kokkeler on 2024/04/18 13:13
From version 129.1
edited by Erik Bakker
on 2023/07/17 15:10
Change comment: There is no comment for this version
To version 130.1
edited by Erik Bakker
on 2023/07/17 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,18 +2,18 @@
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 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.
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 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 +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 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 +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.
12 12  
13 13  [[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
14 14  
15 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 +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.
17 17  
18 18  [[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
19 19  
... ... @@ -20,16 +20,16 @@
20 20  == **Feedback Items** ==
21 21  
22 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 +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.
24 24  
25 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 +Currently, 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 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 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
30 30  
31 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 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
33 33  
34 34  //__Removed the erroneous alert on message mapping when having a passthrough API__//
35 35  This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
... ... @@ -37,13 +37,13 @@
37 37  == **Bug Fixes** ==
38 38  
39 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.
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 41  
42 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.
43 +We have improved the validation feedback when migrating to the next-generation architecture.
44 44  
45 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.
46 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
47 47  
48 48  //__Refresh behavior within the deployment plan is fixed__//
49 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.