Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 76.1
edited by Erik Bakker
on 2023/01/31 13:02
Change comment: There is no comment for this version
To version 96.1
edited by Erik Bakker
on 2023/04/11 10:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +195 - Easter Party
Content
... ... @@ -2,102 +2,81 @@
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 couple of weeks we had our quarterly "hackathon" in which we fixed a series of annoying bugs and introduced many small improvements. On top of that we also finished several additional features for our 3rd generation runtime that will make your life while running on the 3rd generation runtime easier and better manageable. Among the additional features we have the dynamic alerting and the debugger functionality.
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 -== **Dynamic Alerts** ~*~* ==
7 +== **API improvements** ==
8 8  
9 -{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
9 +//__Improved auto-generated error handling__//
10 +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.
10 10  
11 -To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
12 +//__Switch default message format__//
13 +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.
12 12  
13 -We offer alerting on five types.
15 +//__Re-using elements in gateway message__//
16 +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.
14 14  
15 -* Error message
16 -* Log message
17 -* Queue consumers
18 -* Messages in queue
19 -* Queue throughput
18 +//__Improved naming of API operations when adding integrations to Create__//
19 +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 20  
21 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
21 +== **3rd generation improvements** ==
22 22  
23 -These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
23 +//__Update of the static alerting engine__//
24 +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.
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
26 +//__Add "Data pipeline" functionality__//
27 +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.
26 26  
27 -Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
29 +//__Fix related to the debugger__//
30 +This release introduces a fix that allows users to debug a flow once the toggle "Send error messages to eMagiz" is activated.
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
32 +{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
30 30  
31 -== **Debugger ** ~*~* ~* ==
34 +//__Improved migration process__//
35 +This release introduced a fix that allows a user to migrate event processors with custom error handling without manual intervention.
32 32  
33 -{{warning}}Note that this functionality only works when the following criteria are met.
34 -* Your JMS server is running on the 3rd generation runtime
35 -* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
36 -* The beta image is activated
37 -* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
37 +//__Deployment plan change__//
38 +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.
38 38  
39 -As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
40 +{{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}}
40 40  
41 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
42 -
43 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
44 -
45 -Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
46 -
47 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
48 -
49 -{{info}}Note the following limitations when working with the debugger.
50 - * Your entire model needs to be migrated to the 3rd generation runtime
51 - * Only **one** flow **per** runtime can be debugged **per** environment
52 - * There is only **one** overview in which **all** debugged messages are shown
53 - * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
54 - * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
55 - ** After five minutes the debug functionality will be shutdown automatically under water.
56 - ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
57 -
58 -== **Volume mapping - Network Share** ==
59 -
60 -This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
61 -
62 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
63 -
64 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
65 -
66 66  == **Feedback items ** ==
67 67  
68 -We have also solved other feedback items besides the flow designer's critical updates.
44 +//__License Tracker improvements__//
45 +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.
69 69  
70 -//__Improved validation feedback on non-supported WSS4J interceptor __//
71 -We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
47 +//__Ability to view the message definition for a topic__//
48 +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.
72 72  
73 -//__Improve help text in flow testing on Java classes__//
74 -We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
50 +//__Restricted access for uploading custom certificates to endpoints__//
51 +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.
75 75  
76 -//__Improved readibility of notification when trying to delete a runtime__//
77 -When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
78 -
79 79  == **Bug fixes ** ==
80 80  
81 -//__Keep selection when copying properties__//
82 -We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
55 +//__Improved deletion behavior for enumerations__//
56 +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.
83 83  
84 -//__Check on security header improved for API Gateway__//
85 -We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
58 +//__Prevent "async" api operations__//
59 +With this release, we have removed the ability to select the "async" option when the default message format is API Management.
86 86  
87 -//__Copy and paste default support objects__//
88 -With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
61 +//__Importing a response definition broke the request definition__//
62 +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.
89 89  
90 -//__Fix editability of properties when importing store items__//
91 -With this release, you can once again change property names upon importing a store item.
64 +//__Removing a flow does not update the API "all-entry" anymore__//
65 +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.
92 92  
67 +//__Stop deployment plan when a property is missing__//
68 +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.
69 +
70 +//__Cap stack trace of error messages and log entries__//
71 +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.
72 +
93 93  == **Fancy Forum Answers** ==
94 94  
95 95  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:
96 96  
97 -* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
98 -* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
99 -* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
100 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
77 +* [[Entry stops polling occasionally since generation 3>>https://my.emagiz.com/p/question/172825635703376768||target="blank"]]
78 +* [[Invalid datetime>>https://my.emagiz.com/p/question/172825635703389326||target="blank"]]
79 +* [[Paging with a queue -16>>https://my.emagiz.com/p/question/172825635703389781||target="blank"]]
101 101  
102 102  == **Key takeaways** ==
103 103