Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 362.1
edited by Carlijn Kokkeler
on 2024/01/29 14:49
on 2024/01/29 14:49
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,85 +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 achieved.6 +**Hi there, eMagiz developers!** We have... 7 7 8 +== **Alerts** == 8 8 9 -== **Pop-up Improvements** == 10 -//__Property releases__// 11 -When a new property release is created, this property release can now be viewed and 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. 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 - 25 -== **Formatting & Alignments** == 26 - 27 -//__Input fields__// 28 -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. 29 - 30 -//__UI improvements__// 31 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 32 - 33 -//__Runtime overview image versions__// 34 -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. 35 - 36 -//__Component changes reversion__// 37 -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. 38 - 39 -//__State generation statistics__// 40 -The state generation graphs will now show the correct number of cache hits and misses. 41 - 42 -//__Queue browser timestamps__// 43 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 44 - 45 -//__Addition and deletion of internal recipients__// 46 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 47 - 48 - 49 49 == **Feedback Items** == 50 50 51 -//__ Updateflows__//52 -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. 53 53 54 -//__Q&A forum search__// 55 -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]] 56 56 57 -//__ Memorysettings__//58 - It isnowpossibleto changethememorysettingsof acontainerbefore pressing"Applytoenvironment".Before,it was only possibleo view thememorysettingsifacontainerwasrunningonAWSorrunningon adockermachine.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. 59 59 60 -//__Ru ntime validation__//61 - Validationfor runtimes thatare movedfromonpremisestohecloudorviceversahasbeen improved.26 +//__Rebuilding of images__// 27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images. 62 62 63 63 64 64 == **Bug Fixes** == 65 65 66 -//__Rem ovalof onramp__//67 - Wefixedan issuewhereitwas notpossibletoremovethe lastonramp linkedtoa splittedentry (that was an all-entrybefore).32 +//__Runtime metrics processing__// 33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing. 68 68 69 -//__ Runtimestatisticsdetails__//70 -We fixed anissuewhereheapmemoryusagedatawasaccumulatingwhenzooming outintheruntimestatistics detailsdashboards.35 +//__Deployment plan__// 36 +We solved a bug where a deployment step in the deployment plan could randomly get stuck. 71 71 72 -//__ Deploymentprechecks__//73 - Duringdeploymentsprecheckswillbedoneonruntimesthatstillhave tobedeployedfromployarchitecture.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. 74 74 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. 75 75 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. 46 + 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 + 50 + 76 76 == **Fancy Forum Answers** == 77 77 78 78 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: 79 79 80 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 81 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 82 -* [[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"]] 83 83 84 -== **Key Takeaways** ==57 +== **Key takeaways** == 85 85 86 86 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: 87 87 ... ... @@ -92,6 +92,7 @@ 92 92 * Check out the release notes [here] 93 93 * Start thinking about how the license tracker can aid your development 94 94 * Start thinking about major, minor, and patch 68 +* Upgrade to the latest build number 95 95 * Keep making great integrations 96 96 97 97 Let's stay in touch and till next time! ... ... @@ -99,6 +99,7 @@ 99 99 {{info}} 100 100 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 101 101 76 +~*~* Indicates a next-generation-architecture only feature. 102 102 {{/info}} 103 103 ))) 104 104