Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 483.1
edited by Carlijn Kokkeler
on 2024/04/23 14:46
on 2024/04/23 14:46
Change comment:
There is no comment for this version
To version 292.1
edited by Carlijn Kokkeler
on 2023/12/18 12:20
on 2023/12/18 12:20
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 9-CreationCarousel1 +211 - Log Luminary - Content
-
... ... @@ -3,62 +3,60 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** This release, we introduce new environment templates for Docker single and double lane. Moreover, 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 +**Hi there, eMagiz developers!** 7 7 8 -== **Environment Template R13 Docker - Single Lane** == 9 -This release introduces a new non-service affecting environment template for all our customers running in a single-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R13 Docker - Single Lane.WebHome||target="blank"]]. 8 +== **TBD** == 10 10 11 -== **Environment Template R15 Docker - Double Lane** == 12 -This release introduces a new non-service affecting environment template for all our customers running in a double-lane setup. This environment template updates the on-premise machine agents. The complete release notes on the environment template can be found [[here>>doc:Main.Release Information.Cloud Templates.R15 Docker - Double Lane.WebHome||target="blank"]]. 13 13 11 + 14 14 == **Feedback Items** == 15 15 16 -//__ eMagiz Mendixconnector__//17 - We releasedanew versionof our eMagiz MendixconnectorthatwillsupportMendixversion10and higher.14 +//__Missing properties overview__// 15 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 18 18 19 -//__Improved OpenAPI import__// 20 -The path length in OpenAPI spec imports has been increased to a maximum of 300 characters. 17 +ADD FIGURE 21 21 22 -//__ Flowteststacktrace__//23 - Ifaflowtestcreates alog line withlevel‘Warning’or‘Error’andthereisastack trace created,thenwe showthestacktraceinside thelogmessageon aseparatetab.19 +//__Container version overview__// 20 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@release-21 9-creation-carousel-stack-trace.png]]22 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 26 26 27 -{{info}}{{/info}} 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. 24 +//__Improved deployment process__// 25 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance. 31 31 32 -//__ Volumemappingpasswords__//33 - Passwords fornetworkvolumes arehidden onthe machineafterdeployment.27 +//__Rebuilding of images__// 28 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 34 34 35 -//__Create integration removal__// 36 -When removing an integration from Create, the Create phase is now correctly updated. 30 +== **Bug Fixes** == 37 37 38 -//__ Legacystatistics__//39 - Legacypages are nowcorrectly hiddenwhenrunning on the currentruntimearchitecture.32 +//__Runtime metrics processing__// 33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 40 40 41 -//__ Unusedproperties__//42 - Usersare not abletoeditordeleteeMagizproperties,sonowtheywill alsootbe showninthe'Unusedropertyoverview'anymore.35 +//__Deployment plan__// 36 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck. 43 43 44 -//__ Enumerationvalues__//45 - Enumerationvalues forevent processorscannowbe editedin Create.38 +//__View all store items__// 39 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer. 46 46 47 -[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]] 41 +//__Out of memory behavior__// 42 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 48 48 49 -//__ SFTPsessions__//50 - SFTP sessionfactoriesdid not closetheir connection afteritwascomplete.This couldcauseconnectionstarvationontheSFTP server,andwas especiallynoticablewhen usingtheSFTP SessionFactorywithoutcaching,as that factory opensanewconnectionforeverycall.Forthis,anew [[runtimeimage>>doc:Main.ReleaseInformation.Runtime Images.V304.WebHome||target="blank"]]has beenreleased.44 +//__Max fetch size__// 45 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior. 51 51 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"]] 51 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 52 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 53 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 54 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 55 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 59 59 60 -== **Key Takeaways** == 61 61 58 +== **Key takeaways** == 59 + 62 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: 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,9 +65,10 @@ 65 65 * If you have feedback or ideas for us, talk to the Platypus 66 66 * 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"]]66 +* 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 69 +* 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,6 +75,7 @@ 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 77 +~*~* Indicates a next-generation-architecture only feature. 78 78 {{/info}} 79 79 ))) 80 80