Changes for page 222 - Flee Frustration
Last modified by CarlijnKokkeler on 2024/06/05 09:31
From version 83.1
edited by Erik Bakker
on 2023/02/14 15:33
on 2023/02/14 15:33
Change comment:
There is no comment for this version
To version 486.1
edited by CarlijnKokkeler
on 2024/04/23 15:19
on 2024/04/23 15:19
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -19 2-Small Step1 +219 - Creation Carousel - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,70 +1,73 @@ 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 lastcoupleof weeks, weworkedhardonbuildingseveralessential things that willbereleasedlater thisQ.Ontop ofthat,wefinishedadditionalfeaturesforour3rdgenerationruntimethatgiveyouchirurgicalprecision whendoingmaintenanceon amodel. Amongtheotherfeatures,we haveaneweventstreaminggraph andgeneralupdatestoourplatform.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. 6 6 7 -== ** Start/StopFlows**~*~*==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 +//__eMagiz Mendix connector__// 11 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher. 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. 13 +//__Improved OpenAPI import__// 14 +The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]] 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. 14 14 15 - After selectingtheoption, eMagiz will openapop-up where you canstop and start thestarting point of each flow deployed on that runtime. Thiseffectis that the flow will process no new messages,but the flow will still process all remaining messagesafter stopping the flow. To preventaflow, youselect a flow and pressthe Stop button. To startit again, press Start.19 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]] 16 16 17 - [[image:Main.Images.ReleaseBlog.WebHome@192-release-blog--start-stop-flows-pop-up-menu.png]]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. 18 18 19 - {{info}}Only in"StartEditing"modecan youstart and stopspecificflows{{/info}}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. 20 20 21 - ==**Manage overviewEventStreaming**~*~*==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}} 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. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--event-streaming-overview-manage.png]] 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. 26 26 27 -== **Feedback items ** == 32 +//__Volume mapping passwords__// 33 +Passwords for network volumes are hidden on the machine after deployment. 28 28 29 -We have also solved other feedback items besides the flow designer's critical updates. 35 +//__Create integration removal__// 36 +When removing an integration from Create, the Create phase is now correctly updated. 30 30 31 -//__ Topicconfiguration calculation__//32 - Withthis release,wehavesimplifiedtheconfigurationof settingson thetopiclevel to enforce certain best practices withintheportal and simultaneouslymakeiteasier toconfiguretopics.38 +//__Legacy statistics__// 39 +Legacy pages are now correctly hidden when running on the current runtime architecture. 33 33 34 -//__ Make preparation stepin deploymentplan visible__//35 - Fordeploymentonthe3rd generationruntimetowork,theportalneedssome preparationwork.Wehavenowmadethisstepexplicit and partof thedeploymentplan.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. 36 36 37 -{{warning}}Make sure to update your deployment plan accordingly to ensure that the preparation step is not forgotten{{/warning}} 44 +//__Enumeration values__// 45 +Enumeration values for event processors can now be edited in Create. 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. 47 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 41 41 42 -//__ No "Shiftkey" needed anymore toselect multiple itemsin the flow designer__//43 - Asofnow,youdonothave toholdyour"Shiftkey"whenyouwant to selectmultiple items in theflowdesigner.This willmakeiteasierto selectpartsofflows.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. 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. 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 -* [[C hangeproperty with newreleasein generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]53 -* [[ Mapped requestheader"Accept">>https://my.emagiz.com/p/question/172825635703300348||target="blank"]]54 -* [[ OAUTH2.0 AdvancedOptions'Resource'>>https://my.emagiz.com/p/question/172825635703300155||target="blank"]]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"]] 55 55 56 -== **Key takeaways** ==60 +== **Key Takeaways** == 57 57 58 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: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: 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. 66 +* 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 -* Check out the release notes [here] 68 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]] 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}} 78 +{{/info}} 79 +))) 80 + 81 +((( 82 +{{toc/}} 83 +))) 77 77 {{/container}} 85 +{{/container}}