Skip to Content

Changes for page 207 - Aligned State

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -201 - Be Informed
1 +203 - Fast Paced
Content
... ... @@ -2,59 +2,32 @@
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 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.
5 +**Hi there, eMagiz developers!** We have processed some early feedback on the release properties in the last few weeks. On top of that, we have improved the scalability of our complete solution and solved various smaller feedback items.
6 6  
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]].
7 +== **Release Properties - Early Feedback** ==
8 +The community well received the release property functionality. However, there was still room for improvement based on some of the early feedback from the community. Some of these early feedback items have been addressed in this release. As a result, we have updated the layout of a property's edit screen and our checks on nested properties to avoid missing properties.
9 9  
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.
12 -
13 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
14 -
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.
17 -
18 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
19 -
20 20  == **Feedback Items** ==
21 21  
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.
12 +//__"All entries" are now cleaned up as part of the migration__//
13 +To avoid problems when removing integrations after migrating toward the next-generation architecture, we now clean up the "all-entries" as part of the migration towards the next-generation architecture.
24 24  
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.
15 +//__Trigger ID added to our alerting on the next-generation architecture__//
16 +We added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and more manageable.
27 27  
28 -//__Additional help texts on Design Architecture__//
29 -We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
30 -
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.
33 -
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.
36 -
37 37  == **Bug Fixes** ==
38 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.
20 +//__Ensure no flow can be in a release twice__//
21 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
41 41  
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.
23 +//__Ensure no flow can be in a release twice__//
24 +We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions, we fixed this.
44 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 considered 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 -
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
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"]]
30 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
58 58  
59 59  == **Key takeaways** ==
60 60  
... ... @@ -75,6 +75,6 @@
75 75  {{info}}
76 76  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  
78 -~*~* Indicates a GEN3-only feature.
51 +~*~* Indicates a next-generation-architecture only feature.
79 79  {{/info}})))((({{toc/}}))){{/container}}
80 80  {{/container}}