Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10

From version 144.1
edited by Erik Bakker
on 2023/08/15 10:23
Change comment: There is no comment for this version
To version 83.1
edited by Erik Bakker
on 2023/02/14 15:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -203 - Fast Paced
1 +192 - Small Step
Content
... ... @@ -2,32 +2,56 @@
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 processed some of the early feedback on the release properties. On top of that we have improved the scalability of our complete solution and solved various smaller feedback items.
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 6  
7 -== **Release Properties - Early Feedback** ==
8 -The release property functionality was well received by the community. However, there was still room for improvement based on some of the early feedback we received from the community. Some of these early feedback items have been addressed in this release. As a result we have updated the layout of the edit screen of a property and have updated our checks on nested properties to avoid missing properties.
7 +== **Start/Stop Flows** ~*~* ==
9 9  
10 -== **Feedback Items** ==
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}}
11 11  
12 -//__"All entries" are now cleaned up as part of the migration__//
13 -To avoid problems when removing integrations after the migration towards the next-generation architecture we now clean-up the "all-entries" as part of the migration towards the next-generation architecture.
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.
14 14  
15 -//__Trigger ID added to our alerting on the next-generation architecture__//
16 -We have added a unique trigger ID to each alert configuration to make the interpretation for our support desk much easier and better manageable.
13 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
17 17  
18 -== **Bug Fixes** ==
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.
19 19  
20 -//__Ensure no flow can be in a release twice__//
21 -We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
17 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
22 22  
23 -//__Ensure no flow can be in a release twice__//
24 -We have fixed a bug that could cause one flow to end up in the same release with two different flow versions. As this will break your solution on various occasions we fixed this.
19 +{{info}}Only in "Start Editing" mode can you start and stop specific flows{{/info}}
25 25  
21 +== **Manage overview Event Streaming** ~*~* ==
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.
24 +
25 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
26 +
27 +== **Feedback items ** ==
28 +
29 +We have also solved other feedback items besides the flow designer's critical updates.
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.
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.
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 concerning User Management. When you press the "Transfer from design" button, both Users and Roles will be synchronized.
47 +
26 26  == **Fancy Forum Answers** ==
27 27  
28 28  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:
29 29  
30 -* [[Issue with mail server dropping messages>>https://my.emagiz.com/p/question/172825635703530232||target="blank"]]
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"]]
31 31  
32 32  == **Key takeaways** ==
33 33  
... ... @@ -48,6 +48,6 @@
48 48  {{info}}
49 49  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
50 50  
51 -~*~* Indicates a next-generation-architecture only feature.
75 +~*~* Indicates a GEN3-only feature.
52 52  {{/info}})))((({{toc/}}))){{/container}}
53 53  {{/container}}