Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 370.1
edited by Carlijn Kokkeler
on 2024/01/31 12:01
on 2024/01/31 12:01
Change comment:
There is no comment for this version
To version 286.1
edited by Carlijn Kokkeler
on 2023/12/04 15:48
on 2023/12/04 15:48
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 3-JoyfulJourneys1 +210 - Deployment Delights - Content
-
... ... @@ -3,81 +3,59 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Inthis release,severalimprovementsforpop-upshavebeen made sothatmoreuser friendlymessagesare shownthatreflectactual behaviour. Moreover,formattingnd alignmentimprovementshavebeen madetoimprovetheuser journey. Lastly, wehaveworkedonsomemorefeedback itemsand severalmore bugfixes havebeendone.6 +**Hi there, eMagiz developers!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several for the Store. Lastly, we made some changes to the alerts that you may be receiving. 7 7 8 -== ** Pop-up Improvements** ==8 +== **Alerts** == 9 9 10 -//__ Propertyreleases__//11 - Whenanew propertyreleaseiscreated, thispropertyreleasecannow notnly beviewedbutalsoreleasepropertiescandeleted.10 +//__Topic approaching max size alert__// 11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 13 +//__Missing metrics alert__// 14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 14 14 15 -//__Runtime deletion__// 16 -When deleting a runtime, the error message is more descriptive. The error message will now include the names of the flows that run on the container. 17 - 18 -//__Wiretap & debug error messages__// 19 -The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 20 - 21 -//__Action messages__// 22 -The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 23 - 24 -== **Formatting & Alignments** == 25 - 26 -//__Input fields__// 27 -Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions. 28 - 29 -//__UI improvements__// 30 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 31 - 32 -//__Component changes reversion__// 33 -In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed. 34 - 35 -//__State generation statistics__// 36 -The state generation graphs will now show the correct number of cache hits and misses. 37 - 38 -//__Queue browser timestamps__// 39 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 40 - 41 -//__Addition and deletion of internal recipients__// 42 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 43 - 44 44 == **Feedback Items** == 45 45 46 -//__ Updateflows__//47 -In Create> Resources,a button"Updateflows"hasbeenaddedtoupdate versionsofallflows in whicharesourceisused.18 +//__Container version overview__// 19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section. 48 48 49 -//__Q&A forum search__// 50 -The option to search by pressing the Enter key has been added to the Q&A forum. 21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 51 51 52 -//__Memory settings__// 53 -It is now possible to change the memory settings of a newly added container before pressing "Apply to environment". 54 -//__Runtime validation__// 55 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 23 +//__Unchanged containers__// 24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 56 56 57 -//__Ru ntimeoverviewimageversions__//58 - Insightintointendedand actualdeploymentshas been improved.If the releaseversion numberonruntimesis differentcomparedwith the release,this is showninthe runtimeoverview.26 +//__Rebuilding of images__// 27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 59 59 60 60 == **Bug Fixes** == 61 61 62 -//__Rem ovalof onramp__//63 - Wefixedan issuewhereitwas notpossibletoremovethe lastonramp linkedtoa splittedentry (that was an all-entrybefore).31 +//__Runtime metrics processing__// 32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 64 64 65 -//__ Runtimestatisticsdetails__//66 -We fixed anissuewhereheapmemoryusagedatawasaccumulatingwhenzooming outintheruntimestatistics detailsdashboards.34 +//__Deployment plan__// 35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 67 67 68 -//__ Deploymentprechecks__//69 - Duringdeployments, precheckscanbexecuted onruntimeslevelfor runtimes thatstill have tobe deployed.Theseprecheckscanbe executedviaDeploy> Architecture.37 +//__View all store items__// 38 +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. 70 70 40 +//__Out of memory behavior__// 41 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 42 + 43 +//__Max fetch size__// 44 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. 45 + 71 71 == **Fancy Forum Answers** == 72 72 73 73 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: 74 74 75 -* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 76 -* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 77 -* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 50 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 51 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 52 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 53 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 54 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 78 78 79 -== **Key Takeaways** == 80 80 57 +== **Key takeaways** == 58 + 81 81 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: 82 82 83 83 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -87,6 +87,7 @@ 87 87 * Check out the release notes [here] 88 88 * Start thinking about how the license tracker can aid your development 89 89 * Start thinking about major, minor, and patch 68 +* Upgrade to the latest build number 90 90 * Keep making great integrations 91 91 92 92 Let's stay in touch and till next time! ... ... @@ -94,6 +94,7 @@ 94 94 {{info}} 95 95 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 96 96 76 +~*~* Indicates a next-generation-architecture only feature. 97 97 {{/info}} 98 98 ))) 99 99