Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From 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
To version 363.1
edited by Carlijn Kokkeler
on 2024/01/29 14:50
on 2024/01/29 14:50
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 0-DeploymentDelights1 +213 - Joyful Journeys - Content
-
... ... @@ -3,59 +3,85 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** We have have donemuchwork for theDeploy phase. Moreover,we didseveralbug fixes,mainlyrelating totheDeploy phase again, butalsoseveralforthe Store. Lastly,we made some changesto thealertsthat you may be receiving.6 +**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been achieved. 7 7 8 -== **Alerts** == 9 9 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. 9 +== **Pop-up Improvements** == 10 +//__Property releases__// 11 +When a new property release is created, this property release can now be viewed and deleted. 12 12 13 -//__Missing metrics alert__// 14 -We solved an issue where the ‘missing metrics’ alert did not always contain the full container name. 13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 15 15 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 +//__Component changes reversion__// 34 +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. 35 + 36 +//__State generation statistics__// 37 +The state generation graphs will now show the correct number of cache hits and misses. 38 + 39 +//__Queue browser timestamps__// 40 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 41 + 42 +//__Addition and deletion of internal recipients__// 43 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 44 + 45 + 16 16 == **Feedback Items** == 17 17 18 -//__ Containerversion overview__//19 -In Deploy> Releases,itis nowpossibleto seethecontainerversionsinthe releasedetails.This canbe viewed by clicking thethree dotsin the Createphasesection.48 +//__Update flows__// 49 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 20 20 21 -[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]] 51 +//__Q&A forum search__// 52 +The option to search by pressing the Enter key has been added to the Q&A forum. 22 22 23 -//__ Unchanged containers__//24 - Whendeployinganewrelease,containers thathavechanges betweenthedeployedrelease andthenewreleasewillnotbedeployedand restarted.54 +//__Memory settings__// 55 +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. 25 25 26 -//__R ebuildingof images__//27 - Changing thelistfflows thatshould runonacontainerwill nowtriggertherebuildingofimages.57 +//__Runtime validation__// 58 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 28 28 60 +//__Runtime overview image versions__// 61 +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. 62 + 29 29 == **Bug Fixes** == 30 30 31 -//__R untimeetricsprocessing__//32 - Thecollectionandpublishing of runtimemetricsis nolongersynchronizedacrosscontainers,whichimprovestheirprocessing.65 +//__Removal of onramp__// 66 +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). 33 33 34 -//__ Deploymentplan__//35 -We solved abugwhere adeployment stepinthedeploymentplancouldrandomly getstuck.68 +//__Runtime statistics details__// 69 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 36 36 37 -//__ View all storeitems__//38 - An issue has beenfixedwhereitwasnotpossibleto loadmorestoreitemsintheleftpanelintheCreatephaseFlowDesigner.71 +//__Deployment prechecks__// 72 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 39 39 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 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 - 46 46 == **Fancy Forum Answers** == 47 47 48 48 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: 49 49 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"]] 79 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 80 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 81 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 55 55 83 +== **Key Takeaways** == 56 56 57 -== **Key takeaways** == 58 - 59 59 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: 60 60 61 61 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -65,7 +65,6 @@ 65 65 * Check out the release notes [here] 66 66 * Start thinking about how the license tracker can aid your development 67 67 * Start thinking about major, minor, and patch 68 -* Upgrade to the latest build number 69 69 * Keep making great integrations 70 70 71 71 Let's stay in touch and till next time! ... ... @@ -73,7 +73,6 @@ 73 73 {{info}} 74 74 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 75 75 76 -~*~* Indicates a next-generation-architecture only feature. 77 77 {{/info}} 78 78 ))) 79 79