Skip to Content

Changes for page 207 - Aligned State

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -202 - New Equilibrium
1 +195 - Easter Party
Content
... ... @@ -2,68 +2,83 @@
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 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.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have focused on wrapping up the previous quarter and starting the new one. When this happens, we go silent for a few weeks to plan for the upcoming quarter during our PI rituals. This time we added the famous "Hackathon" to the end of the PI week so we could start the Easter break with excellent spirit after solving several smaller feedback items and bugs reported by you. Several of those stories will be included in this and the upcoming release. On top of that, we introduce various improvements to our API Gateway pattern and our 3rd generation runtime architecture. Subsequently, we will release a new runtime image supporting the multiple improvements.
6 6  
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.
7 +== **Release properties** ==**
9 9  
10 -{{info}}For more information please check out the following microlearnings:
9 +== **API improvements** ==
11 11  
12 -*
13 -*
14 -*
11 +//__Improved auto-generated error handling__//
12 +When you create a new operation in your API gateway, eMagiz will now automatically generate the correct schemas, HTTP codes, and examples for this operation based on industry standards.
15 15  
16 -Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
17 -{{/info}}
14 +//__Switch default message format__//
15 +We have improved the logic when you switch the message format of your gateway message from XML to JSON or vice versa. As a result, the Swagger file will be changed accordingly. Once you update the relevant flow in Create and deploy the solution, the Swagger UI will automatically match the expected result.
18 18  
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.
17 +//__Re-using elements in gateway message__//
18 +This release improves how the examples and schemas in Swagger and the Flow Testing functionality are generated when certain elements repeatedly appear in different places within one specific gateway message.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
20 +//__Improved naming of API operations when adding integrations to Create__//
21 +Previously when you added API operations to the Create phase, the HTTP operation (i.e., POST, PUT, GET) was not visible to a user. As a result, it became tough for a user to discern between specific operations once multiple of them were used on one resource (i.e., Order, Invoice, Lead). To clarify this for the user, the display name defined in Design (instead of Capture) is now used within this overview for these operations.
23 23  
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.
23 +== **3rd generation improvements** ==
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
25 +//__Update of the static alerting engine__//
26 +In this release, we have updated the static alerting engine that determines when one of the static alerts, as defined by eMagiz, should be triggered (or not). This change will improve the performance of the solution and will ensure that the alerts are activated correctly.
28 28  
29 -== **Feedback Items** ==
28 +//__Add "Data pipeline" functionality__//
29 +This release introduces the "data pipeline" functionality to the 3rd generation runtime. This removes another blockage for models waiting on this before migrating to the 3rd generation runtime.
30 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.
31 +//__Fix related to the debugger__//
32 +This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
33 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.
34 +{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
36 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.
36 +//__Improved migration process__//
37 +This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
39 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.
39 +//__Deployment plan change__//
40 +In this release, the prepare release step will not start automatically anymore. This prevents the user from waiting for this action to be finished before they can continue deploying the solution to their environment.
42 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.
42 +{{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}}
45 45  
46 -== **Bug Fixes** ==
44 +== **Feedback items ** ==
47 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.
46 +//__License Tracker improvements__//
47 +With this release, we have added several new features available to purchase. On top of that, additional information on the license, such as adding notes and seeing the data sink packets, is now available.
50 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.
49 +//__Ability to view the message definition for a topic__//
50 +Currently, you can easily navigate to the message definition of a topic via the context menu in Design, even if there is no event processor linked to the topic.
53 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.
52 +//__Restricted access for uploading custom certificates to endpoints__//
53 +To improve our cloud offerings' general security and prevent users from uploading the wrong certificates, we have now restricted access to this view to ensure that only the administrator can execute this change. This allows for a discussion between the team implementing the solution and eMagiz before actions are taken.
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.
55 +== **Bug fixes ** ==
59 59  
57 +//__Improved deletion behavior for enumerations__//
58 +To prevent that eMagiz will incorrectly delete enumeration lists when you press a "Cancel" button, we have improved the deletion behavior when viewing enumerations in the Create phase of eMagiz.
59 +
60 +//__Prevent "async" api operations__//
61 +With this release, we have removed the ability to select the "async" option when the default message format is API Management.
62 +
63 +//__Importing a response definition broke the request definition__//
64 +Currently, importing a response definition breaks the request definition. With this release, we have changed this behavior, ensuring that only the response definition is changed when importing and not the request definition.
65 +
66 +//__Removing a flow does not update the API "all-entry" anymore__//
67 +When you removed a flow from Create, the API Gateway all-entry received a new version of the flow. With this release, we have changed this behavior so that this only happens when the flow you remove is an API-related flow and not when it is a messaging or event streaming flow.
68 +
69 +//__Stop deployment plan when a property is missing__//
70 +Currently, the execution of your deployment plan continues when eMagiz notices a missing property. As this is confusing for a user and not desirable, we have updated the logic to ensure that when this happens, the execution stops. This allows you to fill in the properties, and once filled in, you can continue with the remainder of the deployment plan.
71 +
72 +//__Cap stack trace of error messages and log entries__//
73 +To prevent that enormous stack traces of error messages and log entries need to be processed by various systems, we have now limited what is kept so only the relevant information is shown to the user.
74 +
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  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:
63 63  
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"]]
79 +* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
80 +* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
81 +* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
67 67  
68 68  == **Key takeaways** ==
69 69