Skip to Content

Changes for page 216 - Hack Heaven

Last modified by CarlijnKokkeler on 2024/04/18 13:04
From version 82.1
edited by Erik Bakker
on 2023/02/14 14:42
Change comment: There is no comment for this version
To version 389.1
edited by Erik Bakker
on 2024/02/13 15:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +214 - System Symphony
Content
... ... @@ -1,70 +1,65 @@
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 major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have a new event streaming graph and some updates to our platform in general.
6 +**Hi there, eMagiz developers!** This release contains multiple bug fixes, as well as some other improvements. The monitoring graphs have been improved, such that they can now show data up to the last thirty days. Moreover, we can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible. Furthermore, several improvements regarding failover functionality have been done. Lastly, bug fixes regarding resource paths and image versions have been done.
6 6  
7 -== **Start/Stop Flows** ~*~* ==
8 +== **Feedback Items** ==
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 +//__On premise Windows machines__//
11 +We can now deploy on Windows without relying on a Linux subsystem (WSL) to make on-premise deployment on a Windows host more accessible.
10 10  
11 -To enhance the options you have 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 runtime level you can open the context menu and select the option called "Start/Stop Flows".
13 +[[image:Main.Images.Microlearning.WebHome@emagiz-runtime-management--intermediate-runtime-management-deploy-agent.png]]
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
15 +//__Adding multiple attributes__//
16 +It is now possible to add multiple existing attributes to an entity at once. This saves time when having to add multiple attributes to an entity.
14 14  
15 -After selecting the option eMagiz will open a pop-up in which you can stop and start the starting point of each flow that is deployed on that runtime. The effect of this is that no new messages will be processed by the flow but all remaining messages will still be processed by the flow after stopping the flow. To stop a flow you simply select a flow and press the Stop button. To start it again press Start.
18 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-tree-attributes.png]]
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
20 +//__Monitoring graphs__//
21 +The monitoring graphs can now show data up to the last thirty days. To utilize this, a new runtime image, [[V.2.1.1>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V211/||target="blank"]], is needed.
18 18  
19 -{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
23 +== **Bug Fixes** ==
24 +//__Image versions__//
25 +To keep the overview of releases compact we now have improved the (automatic) deletion behavior in the following way:
26 +* The deletion of releases with deployed container versions will not be blocked anymore.
27 +* Automated release clean up behaviour will also not exclude these releases from deletion.
28 +* Images that belong to deleted releases will be kept if there are other releases that would reuse them, otherwise they will be deleted together with the releases.
20 20  
21 -== **Manage overview Event Streaming** ~*~* ==
30 +//__Failover group helptext__//
31 +The helptext of the Group attribute has been improved.
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 streaing statistics." You can access this functionality via the "Monitoring" menu in Manage. Then, by clicking on the "Event streaing statistics" overview, you can see metadata information on all your topics. Among others you can see whether data is consumed, on which topic a lot of data is produced, and whether consumers are lagging in consuming data.
33 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-helptext.png]]
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
35 +//__Failover group refresh__//
36 +A new state 'Leader (single node)' has been added in case there is only one node for failover setup. Moreover, a refresh button is added in the Group tab of "Start/Stop Flows" screen.
26 26  
27 -== **Feedback items ** ==
38 +[[image:Main.Images.Release Blog.WebHome@release-blog-214-system-symphony-group-refresh.png]]
28 28  
29 -We have also solved other feedback items besides the flow designer's critical updates.
40 +//__Resource paths__//
41 +After migrating a gateway away fom the legacy runtime architecture, the path references in the event processors would be broken. This has been fixed.
30 30  
31 -//__Topic configuration calculation__//
32 -With this release we have simplified the configuration of settings on topic level to enforce certain best practices within the portal and at the same time make it easier to configure topics.
33 -
34 -//__Make preparation step in deployment plan visible__//
35 -For a deployment on the 3rd generation runtime to work some preparation work needs to be done by the portal. We have now made this step explicit and part of the deployment plan.
36 -
37 -{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
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.
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.
44 -
45 -//__User Management synchronization now happens in one step__//
46 -With this release we have updated the synchronization process between Design and Deploy with regards to User Management. From now on, when you press the "Transfer from design" button both Users and Roles will be synchronized.
47 -
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"]]
47 +* [[Token header dispeared after XSLT extension gateway>>https://my.emagiz.com/p/question/172825635703734925||target="blank"]]
48 +* [[Weird characters such as '¥' and '¶' in eMagiz but not in Postman>>https://my.emagiz.com/p/question/172825635703747839||target="blank"]]
49 +* [[Failed to list files error log>>https://my.emagiz.com/p/question/172825635703747912||target="blank"]]
50 +* [[API new client secret>>https://my.emagiz.com/p/question/172825635703748007||target="blank"]]
55 55  
56 -== **Key takeaways** ==
52 +== **Key Takeaways** ==
57 57  
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:
54 +Thanks to all who 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  
60 60  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  * If you have feedback or ideas for us, talk to the Platypus
62 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
58 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
63 63  * Clear your browser cache (Ctrl + Shift + Del)
64 64  * Check out the release notes [here]
65 65  * Start thinking about how the license tracker can aid your development
66 66  * Start thinking about major, minor, and patch
67 -* Upgrade to the latest build number
68 68  * Keep making great integrations
69 69  
70 70  Let's stay in touch and till next time!
... ... @@ -72,6 +72,11 @@
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}}
70 +{{/info}}
71 +)))
72 +
73 +(((
74 +{{toc/}}
75 +)))
77 77  {{/container}}
77 +{{/container}}