Skip to Content

Changes for page 202 - New Equilibrium

Last modified by Carlijn Kokkeler on 2024/04/18 13:13
From version 83.1
edited by Erik Bakker
on 2023/02/14 15:33
Change comment: There is no comment for this version
To version 145.1
edited by Erik Bakker
on 2024/02/20 08:32
Change comment: Renamed back-links.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +202 - New Equilibrium
Content
... ... @@ -1,59 +1,74 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
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 worked hard on building several essential things that will be released later this Q. On top of that, we finished additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the other features, we have a new event streaming graph and general updates to our platform.
6 +**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 -== **Start/Stop Flows** ~*~* ==
8 +== **Release Properties** ==
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}}
10 +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:
10 10  
11 -To enhance your options when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows." You can access this functionality via the "Deploy Architecture" overview in Deploy. On the runtime level, you can open the context menu and select the "Start/Stop Flows" option.
12 +* 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
13 +* 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.
14 +* 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.
15 +* 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.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
17 +{{info}}
18 +For more information, please check out the following microlearnings:
14 14  
15 -After selecting the option, eMagiz will open a pop-up where you can stop and start the starting point of each flow deployed on that runtime. This effect is that the flow will process no new messages, but the flow will still process all remaining messages after stopping the flow. To prevent a flow, you select a flow and press the Stop button. To start it again, press Start.
20 +* [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
21 +* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
22 +* [[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"]]
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
24 +Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
25 +{{/info}}
18 18  
19 -{{info}}Only in "Start Editing" mode can you start and stop specific flows{{/info}}
27 +== ** Manage - Graphs improvements ~*~* ** ==
20 20  
21 -== **Manage overview Event Streaming** ~*~* ==
29 +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 -To enhance the observability of your event streaming solution while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Event streaming statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, you can see metadata information on all your topics by clicking on the "Event streaming statistics" overview. Among others, you can see whether data is consumed, on which topic much data is produced, and whether consumers are lagging in consuming data.
31 +[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
33 +== **Feedback Items** ==
26 26  
27 -== **Feedback items ** ==
35 +//__Improved editability when testing in eMagiz without Edit rights in Create__//
36 +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.
28 28  
29 -We have also solved other feedback items besides the flow designer's critical updates.
38 +//__Improved auditability on Deploy Architecture__//
39 +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).
30 30  
31 -//__Topic configuration calculation__//
32 -With this release, we have simplified the configuration of settings on the topic level to enforce certain best practices within the portal and simultaneously make it easier to configure topics.
41 +//__Test your own exported store content__//
42 +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.
33 33  
34 -//__Make preparation step in deployment plan visible__//
35 -For deployment on the 3rd generation runtime to work, the portal needs some preparation work. We have now made this step explicit and part of the deployment plan.
44 +{{info}}
45 +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"]]
46 +{{/info}}
36 36  
37 -{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
48 +//__Improved comparison of flows in the releases overview__//
49 +We have now made it possible to see the differences in the flow versions between the two releases for all three patterns.
38 38  
39 -//__3rd generation runtime debugger feedback__//
40 -We have improved the user experience of the 3rd generation runtime debugger with this release by solving various feedback items we noticed in the first adoptions of the functionality.
51 +== **Bug Fixes** ==
41 41  
42 -//__No "Shift key" needed anymore to select multiple items in the flow designer__//
43 -As of now, you do not have to hold your "Shift key" when you want to select multiple items in the flow designer. This will make it easier to select parts of flows.
53 +//__Improved validation on XPath header enricher__//
54 +To avoid unexpected behavior when filling in the XPath header enricher component, we have improved the validation on this component.
44 44  
45 -//__User Management synchronization now happens in one step__//
46 -With this release, we have updated the synchronization process between Design and Deploy concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized.
56 +//__Cancel behavior on flow testing property overview fixed__//
57 +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.
47 47  
59 +//__Cancel behavior on flow fragment level when exporting store content__//
60 +We have ensured that when you press Cancel when exporting a flow fragment, the flow fragment will no longer disappear from the list.
61 +
62 +//__Adding numbers on containers in Deploy Architecture__//
63 +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.
64 +
48 48  == **Fancy Forum Answers** ==
49 49  
50 50  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:
51 51  
52 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
53 -* [[Mapped request header "Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]
54 -* [[OAUTH2.0 Advanced Options 'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]
69 +* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
55 55  
56 -== **Key takeaways** ==
71 +== **Key Takeaways** ==
57 57  
58 58  Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
59 59  
... ... @@ -72,6 +72,12 @@
72 72  {{info}}
73 73  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74 74  
75 -~*~* Indicates a GEN3-only feature.
76 -{{/info}})))((({{toc/}}))){{/container}}
90 +~*~* Indicates a next-generation-architecture only feature.
91 +{{/info}}
92 +)))
93 +
94 +(((
95 +{{toc/}}
96 +)))
77 77  {{/container}}
98 +{{/container}}