Skip to Content

Changes for page 222 - Flee Frustration

Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 486.1
edited by CarlijnKokkeler
on 2024/04/23 15:19
Change comment: There is no comment for this version
To version 82.1
edited by Erik Bakker
on 2023/02/14 14:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -219 - Creation Carousel
1 +192 - Small Step
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,73 +1,70 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, the path length in OpenAPI spec imports has been increased to a maximum of 300 characters. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
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.
7 7  
8 -== **Feedback Items** ==
7 +== **Start/Stop Flows** ~*~* ==
9 9  
10 -//__eMagiz Mendix connector__//
11 -We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
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}}
12 12  
13 -//__Improved OpenAPI import__//
14 -The path length in OpenAPI spec imports has been increased to a maximum of 300 characters.
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".
15 15  
16 -//__Flow test stack trace__//
17 -If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab.
13 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
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.
20 20  
21 -{{info}}With the release of Spring 6 in our previous release, some users reported that their filters have begun logging warnings about discarding messages even though the filter is configured to not throw an exception on rejection. For flows that process high numbers of messages (and potentially discard a lot of messages as well) this can significantly disturb the overview of the logs in the manage phase.
17 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]
22 22  
23 -To mitigate this, you can change the filter that throws the warning so it specifically refers to a discard channel. Given the chosen configuration, we advice to use the nullChannel option. This will silently drop the message without registering a warning in the log. In case you find the warning in the log a nice addition, we suggest to add an explicit discard channel leading to a logging outbound channel adapter. This log component can then be configured to throw a warning.
19 +{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
24 24  
25 -In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}}
21 +== **Manage overview Event Streaming** ~*~* ==
26 26  
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.
27 27  
28 -== **Bug Fixes** ==
29 -//__Error handling__//
30 -When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
25 +[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]]
31 31  
32 -//__Volume mapping passwords__//
33 -Passwords for network volumes are hidden on the machine after deployment.
27 +== **Feedback items ** ==
34 34  
35 -//__Create integration removal__//
36 -When removing an integration from Create, the Create phase is now correctly updated.
29 +We have also solved other feedback items besides the flow designer's critical updates.
37 37  
38 -//__Legacy statistics__//
39 -Legacy pages are now correctly hidden when running on the current runtime architecture.
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.
40 40  
41 -//__Unused properties__//
42 -Users are not able to edit or delete eMagiz properties, so now they will also not be shown in the 'Unused property overview' anymore.
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.
43 43  
44 -//__Enumeration values__//
45 -Enumeration values for event processors can now be edited in Create.
37 +{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}}
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
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.
48 48  
49 -//__SFTP sessions__//
50 -SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
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.
51 51  
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 +
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 -* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
57 -* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
58 -* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||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"]]
59 59  
60 -== **Key Takeaways** ==
56 +== **Key takeaways** ==
61 61  
62 -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:
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:
63 63  
64 64  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
65 65  * If you have feedback or ideas for us, talk to the Platypus
66 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
62 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
67 67  * Clear your browser cache (Ctrl + Shift + Del)
68 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
64 +* Check out the release notes [here]
69 69  * Start thinking about how the license tracker can aid your development
70 70  * Start thinking about major, minor, and patch
67 +* Upgrade to the latest build number
71 71  * Keep making great integrations
72 72  
73 73  Let's stay in touch and till next time!
... ... @@ -75,11 +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 -{{/info}}
79 -)))
80 -
81 -(((
82 -{{toc/}}
83 -)))
75 +~*~* Indicates a GEN3-only feature.
76 +{{/info}})))((({{toc/}}))){{/container}}
84 84  {{/container}}
85 -{{/container}}