Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 57.1
edited by Erik Bakker
on 2022/12/06 15:57
Change comment: There is no comment for this version
To version 95.1
edited by Erik Bakker
on 2023/04/11 09:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -189 - Private Eye
1 +195 - Easter Party
Content
... ... @@ -2,73 +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!** Our release of the Private store functionality characterizes this release. This functionality allows some users to export content to a private store that is only accessible within the company and could be published to the public store of eMagiz. On top of that, we resolved some of the limitations on the 3rd generation runtime. Furthermore, some minor fixes and beta features will be released to the community.
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 -== **Private Store** ==
8 -On top of our general store, in which eMagiz currently publishes Store content relevant to both the Design and Create phases of eMagiz, we have added the private store functionality. This store works precisely the same as the general store. However, only users belonging to the same company as the exporter can import the store content (after it is approved).
7 +== **API improvements** ==
9 9  
10 -{{warning}}Other users can see the store content but are not able to import the store content. They will be notified to them when they try to do so.{{/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.
11 11  
12 -== **3rd generation runtime bolstering** ==
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 13  
14 -This release will introduce various improvements for our 3rd generation runtime. Below you will find the most noteworthy enhancements we made to the 3rd generation runtime and its interaction with the portal.
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.
15 15  
16 -//__SOAP and REST web services migration, including splitting them__//
17 -With this release, we have released the migration process that will allow you to migrate SOAP and REST web services to the 3rd generation runtime. At the same time, you can directly split the all-entry to eliminate that construction. A specific migration path for this will be published in the documentation portal.
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 18  
19 -//__Changing SSL settings for 3rd generation runtime models works__//
20 -As with the current runtime architecture, you can change the SSL settings if needed for a model running in the 3rd generation runtime.
21 +== **3rd generation improvements** ==
21 21  
22 -//__Improved migration for JMS flows__//
23 -This release will improve the migration of JMS flows when migrating to the 3rd generation runtime.
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 -{{warning}}If you already migrated your JMS flow, you should execute a "Reset" action on the JMS level to get these changes in your model{{/warning}}
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 -//__Removed the ability to add "Debug components" to a flow running in the 3rd generation runtime architecture__//
28 -As of this release, you can no longer add debug components on a flow already migrated to the 3rd generation runtime. This functionality will not work in the 3rd generation runtime and would break your flow.
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.
29 29  
30 -//__Deployment plan is updated correctly when completly migrated to the 3rd generation runtime architecture__//
31 -We have fixed a bug that generated an incorrect default deployment plan once you were fully migrated to the 3rd generation runtime.
32 +{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
32 32  
33 -//__Correct property generation for Event Streaming flows using the 3rd generation runtime architecture__//
34 -With this release, the properties generated for Event Streaming flows running in the 3rd generation runtime are configured correctly to mimic the ones in the image.
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.
35 35  
36 -//__Added "Reset" functionality__//
37 -With this release, a new functionality has been added for 3rd generation runtimes that allows you to combine several steps into one action, called "Reset runtime." The effect of this action is the same as it currently is in the legacy runtime.
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  
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}}
41 +
39 39  == **Feedback items ** ==
40 40  
41 -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.
42 42  
43 -//__Improved naming convention on Store related pages__//
44 -We have improved various display names using the merge functionality within our store offering.
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.
45 45  
46 -//__Update security protocols for our internal architecture__//
47 -Parts of our internal infrastructure (i.e., docs.emagiz.com) have been updated to adhere to the latest security standards.
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.
48 48  
49 -//__Improved read-only description for "if exists" constructions in Transformations__//
50 -To make it clear what the "if exists" check does while not being in "Start Editing" mode, we have improved the description so users without edit rights or without wanting to enter the "Start Editing" mode can read and interpret what the check does.
53 +== **Bug fixes ** ==
51 51  
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.
52 52  
53 -== **Bug fixes ** ==
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.
54 54  
55 -//__Decent validation feedback when not filling in the property value__//
56 -We have fixed the validation feedback you get when not filling in the property value using the "Check properties" functionality.
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.
57 57  
58 -//__Incorrect resource locations__//
59 -We have fixed several instances where the resource location was not generated correctly in the 3rd generation runtime.
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.
60 60  
61 -//__Apply to environment in User Management performance improvement__//
62 -We have improved the performance of updating User Management on your environment. This way, the update functionality is more stable and faster.
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.
63 63  
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 +
64 64  == **Fancy Forum Answers** ==
65 65  
66 66  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:
67 67  
68 -* [[Is eMagiz able to read XSD attributes>>https://my.emagiz.com/p/question/172825635703236146||target="blank"]]
69 -* [[Does eMagiz use ActiveMQ?>>https://my.emagiz.com/p/question/172825635703235780||target="blank"]]
70 -* [[Tool for test messages to eMagiz Queues>>https://my.emagiz.com/p/question/172825635703236227||target="blank"]]
71 -* [[How to Remove Cloud Container>>https://my.emagiz.com/p/question/172825635703236460||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"]]
72 72  
73 73  == **Key takeaways** ==
74 74