Skip to Content

Changes for page 207 - Aligned State

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +199 - Home Improvements
Content
... ... @@ -2,83 +2,45 @@
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 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.
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.
6 6  
7 -== **Release properties** ==**
7 +== **Next generation improvements and bug fixes** ==
8 8  
9 -== **API improvements** ==
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 10  
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.
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 13  
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.
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}}
16 16  
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.
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.
19 19  
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.
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.
22 22  
23 -== **3rd generation improvements** ==
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.
24 24  
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.
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}}
27 27  
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.
28 +== **Store Improvements** ==
30 30  
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.
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.
33 33  
34 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
33 +== **Event Streaming - Certificate Management** ==
35 35  
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.
35 +//__Expired certification notification__//
36 +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]].
38 38  
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.
41 -
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}}
43 -
44 -== **Feedback items ** ==
45 -
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.
48 -
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.
51 -
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.
54 -
55 -== **Bug fixes ** ==
56 -
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 -
75 75  == **Fancy Forum Answers** ==
76 76  
77 77  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:
78 78  
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"]]
42 +* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
43 +* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
82 82  
83 83  == **Key takeaways** ==
84 84