Skip to Content

Changes for page 207 - Aligned State

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -195 - Easter Party
1 +202 - New Equilibrium
Content
... ... @@ -2,81 +2,65 @@
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 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 smaller feedback items from our hackathon efforts that are now released to you.
6 6  
7 -== **API improvements** ==
7 +== **Release Properties** ==
8 +As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, the timing of changing properties was crucial to avoid costly mistakes in Production. On top of that, it could have been clearer whether a property value was indeed updated as it was not linked to something deployed. These considerations allow us to change the property management behavior in our next-generation architecture and our current-generation architecture. There are several fundamental changes compared to the current way of managing your properties. Most notable among these are:
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 +* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
11 +* Property placeholders (i.e., the names of properties as given in Create) are now automatically created for you. As a result, you don't have to type them twice when working on an integration.
12 +* When adding or editing a property, you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double-lane setup or having a distributed landscape of containers.
13 +* A, for most, a new concept of a "property release" is introduced. With the help of this functionality, you can easily change a property on Production without having to create an entirely new release in Test and promote it to the Production environment.
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.
15 +{{info}}For more information, please check out the following microlearnings:
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.
17 +* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18 +* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
19 +* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
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.
21 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22 +{{/info}}
20 20  
21 -== **3rd generation improvements** ==
24 +== ** Manage - Next generation graphs improvements ** ==
25 +As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the managed graphs as we retrieve and show less fine-grained information when zooming out.
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.
27 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
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.
29 +== **Feedback Items** ==
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.
31 +//__Improved editability when testing in eMagiz without Edit rights in Create__//
32 +Without editing rights in the Create phase, you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we should have noticed during the implementation. These have been fixed, allowing those without edit rights to change the test case's name and description.
31 31  
32 -{{warning}}To make use of this bug fix, you need to be on the latest runtime image{{/warning}}
34 +//__Improved auditability on Deploy Architecture__//
35 +To improve the audibility of Deploy Architecture, we now also log when someone with Admin rights changes specific functions on this level (i.e., Fixed IP).
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.
37 +//__Test your own exported store content__//
38 +We have now allowed testing of your exported work to the store before it gets approved. This will increase the quality of store items we have, and our partners have on offer within the store.
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.
40 +{{info}}In case the concept of the store is new for you, please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
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}}
42 +//__Improved comparison of flows in the releases overview__//
43 +We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
41 41  
42 -== **Feedback items ** ==
45 +== **Bug Fixes** ==
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.
47 +//__Improved validation on XPath header enricher__//
48 +To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
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.
50 +//__Cancel behavior on flow testing property overview fixed__//
51 +We have ensured that when you press Cancel when editing a property needed in a flow test, the property placeholder will no longer disappear from the list.
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.
53 +//__Cancel behavior on flow fragment level when exporting store content__//
54 +We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
52 52  
53 -== **Bug fixes ** ==
56 +//__Adding numbers on containers in Deploy Architecture__//
57 +With this release, we have made the first step in giving a clear overview of how many integrations for a certain runtime (i.e., container) are in your active release.
54 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"]]
63 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
80 80  
81 81  == **Key takeaways** ==
82 82