Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 95.1
edited by Erik Bakker
on 2023/04/11 09:30
Change comment: There is no comment for this version
To version 128.1
edited by Erik Bakker
on 2023/07/17 14:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +201 - Be Informed
Content
... ... @@ -2,81 +2,56 @@
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 planning the upcoming Q and finishing up features of the last Q. More on that later. On top of that we have several smaller items as a result of our hackathon efforts to present to you.
6 6  
7 -== **API improvements** ==
7 +== **Announcement - Release Properties** ==
8 +As of the next release (202) we will introduce a completely new way of handling properties for all our clients. In the upcoming weeks we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance please contact us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
8 8  
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 +== ** Deploy Architecture - Apply To Environment improvements ** ==
11 +As of this release we will show you a list of all change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together in teams, what will change when pressing this button.
11 11  
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.
13 +//__Enhanced right-hand view within Deployment Plan context__//
14 +When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
14 14  
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.
16 +{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
17 17  
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.
18 +//__Improved timeout settings when deploying__//
19 +To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
20 20  
21 -== **3rd generation improvements** ==
21 +{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
22 22  
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.
23 +//__Detailed HTTP Statistics now show user info in specific additional cases__//
24 +To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
25 25  
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 +{{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}}
28 28  
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 +//__Improved loading speed of Manage Dashboard__//
29 +This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
31 31  
32 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
31 +== **Store Improvements** ==
33 33  
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.
33 +//__Importing in Design is improved__//
34 +We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
36 36  
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.
36 +== **Bug Fixes** ==
39 39  
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}}
38 +//__Deprecated reminder pop-up removed__//
39 +We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
41 41  
42 -== **Feedback items ** ==
41 +//__Improved selection area in Flow Designer__//
42 +When working on a large flow you can now select specific areas easily while you are scrolled down further down the flow.
43 43  
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.
44 +//__Improved Kafka settings__//
45 +For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
46 46  
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.
47 +{{info}}We strongly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
49 49  
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.
52 -
53 -== **Bug fixes ** ==
54 -
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.
57 -
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.
60 -
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.
63 -
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.
66 -
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 -
73 73  == **Fancy Forum Answers** ==
74 74  
75 75  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:
76 76  
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"]]
53 +* [[HTTP URL must not be null>>https://my.emagiz.com/p/question/172825635703491908||target="blank"]]
54 +* [[removing the curled brackets in a JSON payload>>https://my.emagiz.com/p/question/172825635703479276||target="blank"]]
80 80  
81 81  == **Key takeaways** ==
82 82