Skip to Content

Changes for page 201 - Be Informed

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +201 - Be Informed
Content
... ... @@ -2,48 +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 improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
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 -//__Enhanced overview of the HTTP Statistics__//
10 -As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
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 -//__Improved rollup and storage of metrics when running an event streaming solution__//
24 -To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
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.
25 25  
26 -{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of July. From then on, all data before the 9th of June will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/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.
27 27  
28 -== **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.
29 29  
30 -//__Improved importing behavior for specific use cases__//
31 -Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
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 -//__Fixed bug in creating a message mapping on top of an imported system message__//
34 -It is now possbile to create a message mapping to an imported system message from the store.
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  
36 -== **Event Streaming - Certificate Management** ==
37 +== **Bug Fixes** ==
37 37  
38 -//__Expired certification notification__//
39 -As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
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 40  
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 +
41 41  == **Fancy Forum Answers** ==
42 42  
43 43  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:
44 44  
45 -* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
46 -* [[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"]]
47 47  
48 48  == **Key takeaways** ==
49 49