Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 366.1
edited by Carlijn Kokkeler
on 2024/01/29 15:02
on 2024/01/29 15:02
Change comment:
There is no comment for this version
To version 278.1
edited by Carlijn Kokkeler
on 2023/12/04 14:54
on 2023/12/04 14:54
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 -2 13-JoyfulJourneys1 +209 - Deployment Delights - Content
-
... ... @@ -3,81 +3,56 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In this release,several improvements for pop-upshavebeen made so that more user friendly messages are shown that reflect actual behaviour.Moreover, formatting and alignment improvements have been made to improve the user journey.Lastly, we have worked on some more feedback items and several more bug fixes have been done.6 +**Hi there, eMagiz developers!** We have... 7 7 8 -== ** Pop-up Improvements** ==8 +== **Release Maintenance** == 9 9 10 -//__Property releases__// 11 -When a new property release is created, this property release can now be viewed and deleted. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 14 14 15 -//__Runtime deletion__// 16 -When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container. 17 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 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. 14 +== **Feedback Items** == 23 23 24 -== **Formatting & Alignments** == 16 +//__Container version overview__// 17 +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. 25 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. 19 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]] 28 28 29 -//__U Iimprovements__//30 - UIimprovementsforicinputcomponentshavebeen done and thetooltip for optional/required toggles has beenimproved.21 +//__Unchanged containers__// 22 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted. 31 31 32 -//__ Componentchangesreversion__//33 - In the flowdesignerabug couldoccurwhere the changesto a component wouldberevertedifthe editingpop-up would be kept openforsome minutes without havingsaved the changesyet.This has been fixed.24 +//__Rebuilding of images__// 25 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 34 34 35 -//__State generation statistics__// 36 -The state generation graphs will now show the correct number of cache hits and misses. 37 37 38 -//__Queue browser timestamps__// 39 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 28 +== **Bug Fixes** == 40 40 41 -//__ Additionand deletionof internal recipients__//42 - Internalrecipientsarenow addedanddeleted correctly.Before,aninternalrecipientcould beaddedandthereafterdeleted automatically whenrefreshingthe page.30 +//__Runtime metrics processing__// 31 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 43 43 44 -== **Feedback Items** == 33 +//__Deployment plan__// 34 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 45 45 46 -//__ Updateflows__//47 - In Create> Resources,abutton"Update flows"has beenadded toupdateversionsofall flows inwhicharesource isused.36 +//__Store message merging__// 37 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages. 48 48 49 -//__ Q&Aforumsearch__//50 - Theoptionto searchby pressingtheEnterkeyhasbeenaddedtotheQ&A forum.39 +//__View all store items__// 40 +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. 51 51 52 -//__ Memorysettings__//53 - Itis nowpossible to change thememorysettingsofa containerbefore pressing"Applyto environment". Before, it wasonlypossibletoview thememorysettings if a containerwasrunningon AWS orrunningon a docker machine.42 +//__Out of memory behavior__// 43 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 54 54 55 -//__Runtime validation__// 56 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 45 +//__Max fetch size__// 46 +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 the behavior. 47 + 57 57 58 -//__Runtime overview image versions__// 59 -Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview. 60 - 61 -== **Bug Fixes** == 62 - 63 -//__Removal of onramp__// 64 -We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before). 65 - 66 -//__Runtime statistics details__// 67 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 68 - 69 -//__Deployment prechecks__// 70 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 71 - 72 72 == **Fancy Forum Answers** == 73 73 74 74 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: 75 75 76 -* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]] 77 -* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]] 78 -* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]] 53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 79 79 80 -== **Key Takeaways** ==55 +== **Key takeaways** == 81 81 82 82 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: 83 83 ... ... @@ -88,6 +88,7 @@ 88 88 * Check out the release notes [here] 89 89 * Start thinking about how the license tracker can aid your development 90 90 * Start thinking about major, minor, and patch 66 +* Upgrade to the latest build number 91 91 * Keep making great integrations 92 92 93 93 Let's stay in touch and till next time! ... ... @@ -95,6 +95,7 @@ 95 95 {{info}} 96 96 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 97 97 74 +~*~* Indicates a next-generation-architecture only feature. 98 98 {{/info}} 99 99 ))) 100 100