Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 365.1
edited by Carlijn Kokkeler
on 2024/01/29 14:59
on 2024/01/29 14:59
Change comment:
There is no comment for this version
To version 282.1
edited by Carlijn Kokkeler
on 2023/12/04 15:08
on 2023/12/04 15:08
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,58 @@ 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 +== **Alerts** == 9 9 10 -//__ Propertyreleases__//11 - Whenanew propertyreleaseiscreated,this propertyreleasecannowbeviewedand deleted.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 that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container. 16 +== **Feedback Items** == 17 17 18 -//__ Wiretap & debugerrormessages__//19 - Theerrormessages thatmaybedisplayedwhenusing wiretapsandthedebuggerhavebeenimproved,thesearenowmoreuserfriendly.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. 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. 21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 23 23 24 -== **Formatting & Alignments** == 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. 25 25 26 -//__ Inputfields__//27 - Multiple input fields havebeenupdatedsuchthatthey expandwhenthe amountofcharactersexceedsthedefault size. These updates were donetocater to largeexpressions.26 +//__Rebuilding of images__// 27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 28 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 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. 30 +== **Bug Fixes** == 34 34 35 -//__ Stategenerationstatistics__//36 -The stategenerationgraphswillnowshowthe correctumberofcachehitsand misses.32 +//__Runtime metrics processing__// 33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 37 37 38 -//__ Queue browser timestamps__//39 - Alltimestampformattingin thequeue browserisnowalignedtoyyy-MM-ddHH:mm:ss.SSS.35 +//__Deployment plan__// 36 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 40 40 41 -//__ Addition and deletionof internalrecipients__//42 - Internalrecipientsre nowaddedanddeletedcorrectly. Before,an internalrecipientcouldbeddedandthereafterdeletedautomaticallywhen refreshing thepage.38 +//__Store message merging__// 39 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages. 43 43 44 -== **Feedback Items** == 41 +//__View all store items__// 42 +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. 45 45 46 -//__ Updateflows__//47 - InCreate> Resources, a button"Updateflows"hasbeenaddedto updateversionsofall flowsinwhicharesourceisused.44 +//__Out of memory behavior__// 45 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs. 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. 47 +//__Max fetch size__// 48 +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. 49 + 51 51 52 -//__Memory settings__// 53 -It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine. 54 - 55 -//__Runtime validation__// 56 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 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 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 77 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 78 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 55 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]] 79 79 80 -== **Key Takeaways** ==57 +== **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 68 +* 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 76 +~*~* Indicates a next-generation-architecture only feature. 98 98 {{/info}} 99 99 ))) 100 100