Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 93.1
edited by Erik Bakker
on 2023/03/14 08:28
Change comment: There is no comment for this version
To version 132.1
edited by Erik Bakker
on 2023/08/01 13:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Big Leap
1 +202 - New Equilibrium
Content
... ... @@ -2,65 +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 around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
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** ==
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 -//__Better feedback in the error log when a corrupt stylesheet is encountered__//
10 -We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
10 +{{info}}For more information please check out the following microlearnings:
11 11  
12 -//__Better internal error handling to avoid unnecessary alerting and notifications__//
13 -We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
12 +* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
13 +* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
14 +* [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.eMagiz Store.novice-emagiz-store-merge-store-data-model.WebHome||target="blank"]]
14 14  
15 -//__Improved Manage Dashboard__//
16 -This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime 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}}
17 17  
18 -//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 -When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. The opposite happens when the slot wakeup is triggered. As a result, not only the cloud runtimes are started but also all on-premise runtimes.
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.
20 20  
21 -//__Improved process of deploy preparation__//
22 -With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
22 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
23 23  
24 -//__Improved migration of Streaming container__//
25 -When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
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.
26 26  
27 -//__Add History to Notifications in Manage__//
28 -To improve the auditability of our platform, we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way, it is always visible when the notifications were paused and who paused or unpaused the notifications.
27 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
29 29  
30 -//__Improved Manage phase for Event Streaming__//
31 -Based on the feedback on our first iteration of the Manage phase for Event Streaming, we have improved the graphs and the calculations that fill the graphs with values. On top of that, we have added help texts to clarify what each chart our table displays to you.
29 +== **Feedback Items** ==
32 32  
33 -//__Improved help text for network volumes__//
34 -With this release, we have improved the help text that explains network volumes and how to use them within our solution.
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.
35 35  
36 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
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.
37 37  
38 -== **Feedback items ** ==
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 39  
40 -//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41 -With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
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 42  
43 -//__User Roles are sorted alphabetically__//
44 -All user roles under User Management are now also sorted alphabetically.
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 45  
46 -//__Name of keystore for user management now includes the environment__//
47 -To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
46 +== **Bug Fixes** ==
48 48  
49 -== **Bug fixes ** ==
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 50  
51 -//__Consolidated upgrade process cloud template__//
52 -With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
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 53  
54 -//__Ensure users can deploy release on environments they have edit rights on__//
55 -Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
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 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 +
57 57  == **Fancy Forum Answers** ==
58 58  
59 59  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:
60 60  
61 -* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
62 -* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
63 -* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||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"]]
64 64  
65 65  == **Key takeaways** ==
66 66