Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 116.1
edited by Erik Bakker
on 2023/05/10 08:46
Change comment: There is no comment for this version
To version 143.1
edited by Erik Bakker
on 2023/08/07 09:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +202 - New Equilibrium
Content
... ... @@ -2,59 +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 worked hard on improving our next-generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore, several smaller feedback items and bugs have been resolved with this release. So without further ado, let us dive into all we have to offer.
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 -== **Event streaming alerting** ==
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 -This release expands our alerting functionality into the event streaming pattern. As of now, one new "static" alert has been introduced for all clients (using event streaming), and two "dynamic" alerts have been introduced that you can configure yourself if there is a need for it.
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, 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.
10 10  
11 -The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights into whether messages on it are deleted due to a size or time constraint. In cases where data is deleted, the topic was too full way before the messages should have been removed due to the retention hours constraint. This alert can indicate that messages might be deleted before consumer groups had the option to consume the messages.
15 +{{info}}For more information, please check out the following microlearnings:
12 12  
13 -The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
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"]]
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
21 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22 +{{/info}}
16 16  
17 -The first new "dynamic" alert allows you to raise an alert once the number of messages on one (or more topics) is less than a certain number per defined time unit. So, for example, you can configure an alert once the number of messages placed on a topic called "Exception" is less than 15 messages within 5 minutes.
24 +== ** Manage - 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.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
27 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
20 20  
21 -The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups are more than X messages behind on one or more topics. The configuration of this is comparable to what we saw before.
29 +== **Feedback Items** ==
22 22  
23 -For more information on the generic way of working surrounding alerting, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
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.
24 24  
25 -== **3rd generation improvements** ==
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).
26 26  
27 -//__Increased grace period for shutdown__//
28 -In this release, we have increased a container's grace period to shut down before it is forcefully shut down. This should reduce the chance of unwanted failover behavior within your model.
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.
29 29  
30 -//__Update at once or not__//
31 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
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}}
32 32  
33 -//__Improved user feedback while executing a deployment plan__//
34 -This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information about why this cannot be executed is shown to the user. This way, they can take this information and act upon it instead of assuming everything went well.
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.
35 35  
36 -//__Improved auto-healing when running in a hybrid situation__//
37 -In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
45 +== **Bug Fixes** ==
38 38  
39 -//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
40 -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.
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.
41 41  
42 -{{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 June. From then on, all data before the 12th of May 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}}
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.
43 43  
44 -== **Feedback items ** ==
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.
45 45  
46 -//__Make sure the message format can be viewed without "Start editing"__//
47 -With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
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.
48 48  
49 -//__Various styling improvements in the flow testing functionality__//
50 -Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
51 -
52 52  == **Fancy Forum Answers** ==
53 53  
54 54  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:
55 55  
56 -* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
57 -* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
63 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
58 58  
59 59  == **Key takeaways** ==
60 60  
... ... @@ -75,6 +75,6 @@
75 75  {{info}}
76 76  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77 77  
78 -~*~* Indicates a GEN3-only feature.
84 +~*~* Indicates a next-generation-architecture only feature.
79 79  {{/info}})))((({{toc/}}))){{/container}}
80 80  {{/container}}