Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 118.1
edited by Erik Bakker
on 2023/05/22 15:07
Change comment: There is no comment for this version
To version 131.1
edited by Erik Bakker
on 2023/08/01 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -198 - Great Migration
1 +202 - New Equilibrium
Content
... ... @@ -2,39 +2,68 @@
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 the migration towards our next-generation architecture and the general behavior when running on the next-generation architecture. Furthermore, several improvements have been made to our infrastructure to ensure that all data flowing via this infrastructure now that more and more customers are migrating can be handled as well, if not better, as before.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
6 6  
7 -== **3rd generation improvements and bug fixes** ==
7 +== **Release Properties** ==
8 +As of this release, we will introduce a new way of handling properties for all our clients. There are several key changes compared to the current way of managing your properties.
8 8  
9 -//__"Stop" action when running a hybrid situation is not causing issues anymore__//
10 -Before, it could happen when running a double-lane setup in a hybrid situation (i.e., karaf, based runtimes on top of the next-generation architecture) that the stop action on said runtime would not stop the runtime but "kill" it. With this release, that behavior is changed.
10 +{{info}}For more information please check out the following microlearnings:
11 11  
12 -{{info}}Note that this fix is part of a new runtime image for the karaf-based runtimes. The impact of this can be read [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]{{/info}}
12 +*
13 +*
14 +*
13 13  
14 -//__Improved efficiency in deploying a release__//
15 -This release improves the efficiency of the "prepare release" step needed when deploying on the next-generation architecture.
16 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
17 +{{/info}}
16 16  
17 -//__Removed specific dependencies between Deploy Architecture and Releases__//
18 -In this release, we have removed several explicit dependencies that confused the functionality in the Deploy Architecture overview compared to the functionality linked to a release, specifically the deployment of a release.
19 +== ** Deploy Architecture - Apply To Environment improvements ** ==
20 +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.
19 19  
20 -//__Improved validation errors on the invalid configuration of HTTP outbound components__//
21 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
22 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
22 22  
23 -//__Improved migration behavior__//
24 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
25 -A smoother migration of your JMS (and backup JMS) process.
26 -Shortening of names that otherwise would be too long, additional feedback given to the user.
27 -Feedback when the migration process is finished.
24 +== ** Breadcrumb navigation in eMagiz ** ==
25 +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.
28 28  
29 -//__Additional checks when deploying__//
30 -This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
27 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
31 31  
29 +== **Feedback Items** ==
30 +
31 +//__Improved layout of catalog page in Design__//
32 +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.
33 +
34 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
35 +Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
36 +
37 +//__Additional help texts on Design Architecture__//
38 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
39 +
40 +//__Improved Audit Trail on several places__//
41 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
42 +
43 +//__Removed the erroneous alert on message mapping when having a passthrough API__//
44 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
45 +
46 +== **Bug Fixes** ==
47 +
48 +//__Avoid clicking on other components while deleting another__//
49 +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.
50 +
51 +//__Improved validation feedback in migrating to the next-generation architecture__//
52 +We have improved the validation feedback when migrating to the next-generation architecture.
53 +
54 +//__Make sure that user credentials can be viewed with view rights__//
55 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
56 +
57 +//__Refresh behavior within the deployment plan is fixed__//
58 +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 +
32 32  == **Fancy Forum Answers** ==
33 33  
34 34  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:
35 35  
36 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
37 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
64 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
65 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
66 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
38 38  
39 39  == **Key takeaways** ==
40 40