Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 306.1
edited by Carlijn Kokkeler
on 2023/12/21 14:01
on 2023/12/21 14:01
Change comment:
There is no comment for this version
To version 359.1
edited by Carlijn Kokkeler
on 2024/01/29 14:34
on 2024/01/29 14:34
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 1-LogLuminary1 +213 - Joyful Journeys - Content
-
... ... @@ -3,62 +3,78 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** 6 +**Hi there, eMagiz developers!** This release .... 7 7 8 -== **TBD** == 9 9 9 +== **Feedback Items** == 10 10 11 +//__Property releases__// 12 +When a new property release is created, this property release can now be viewed and deleted. 11 11 12 - == **FeedbackItems** ==14 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 13 13 14 -//__Runtime overview__//15 -We addedanew overviewintheDeployphase,called'RuntimeOverview',whichshowstheinformationofall runtimesonrunningmachinesinoverview.16 +//__Runtime deletion__// 17 +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 16 17 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 19 +//__Update flows__// 20 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. 18 18 19 -//__ Missingpropertiesoverview__//20 - Themissingpropertiesoverviewhasbeen updatedtoshowtheruntimesandflowversionsofmissingpropertyvalues.22 +//__Input fields__// 23 +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. 21 21 22 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 25 +//__Memory settings__// 26 +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. 23 23 24 -//__ Breaking changes pop-up__//25 - Pendingchanges thathave a highrisk levelare nowshowninredboldinthepopupthatappears afterclicking 'Apply toenvironment'.28 +//__Runtime validation__// 29 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved. 26 26 27 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 31 +//__UI improvements__// 32 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 28 28 29 -//__ Brokerqueuemetricsdashboards__//30 - Itis nowpossibleto select theMQTTbrokerin thequeuemetricsdashboards.34 +//__Q&A forum search__// 35 +The option to search by pressing the Enter key has been added to the Q&A forum. 31 31 32 -//__ Runtimeimageversion__//33 -The version ofruntimeimagesusedto prepareyourcontainersfordeploymentswill be the same across all environments.Thisholdsfor releasesthat aredeployed andpromoted toa nextenvironment.37 +//__Wiretap & debug error messages__// 38 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 34 34 40 +//__Runtime overview image versions__// 41 +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. 42 + 35 35 == **Bug Fixes** == 44 +//__Action messages__// 45 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour. 36 36 37 -//__ Deploymentexecutionerror message__//38 - Insomecases when a machinetype stepin your deploymentexecution hasanerror andtheportal triesto displaythis errormessage, itmay givean error intheportal. This casehas been fixed by now showing a generic error in the deploymentplanandlogging thefull errortotheDeploy history. TheDeploy historywill showasummaryof the errorandshow the fullrormessage in a new popup.47 +//__Removal of onramp__// 48 +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). 39 39 40 -//__C loud templateupgrade unjustrollback__//41 - Anissuehasbeenfixed where a cloud template upgradewould berolledbackunjustlydue tofailedruntime checksongen3.50 +//__Component changes reversion__// 51 +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. 42 42 43 -//__ Missinglogtries__//44 - Weimproved crash handling sothatlogmessagesclearlyshowwhenand why acontainer failedtostart.53 +//__State generation statistics__// 54 +The state generation graphs will now show the correct number of cache hits and misses. 45 45 46 -//__Runtime logging__//47 -We fixed a bugwhereno newlogmessages wereshowing up,even though theywere produced bythecontainer.56 +//__Runtime statistics details__// 57 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards. 48 48 59 +//__Queue browser timestamps__// 60 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS. 61 + 62 +//__Deployment prechecks__// 63 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 64 + 65 +//__Addition and deletion of internal recipients__// 66 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page. 67 + 49 49 == **Fancy Forum Answers** == 50 50 51 51 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: 52 52 53 -* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 54 -* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 55 -* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 56 -* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 57 -* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 72 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 73 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 74 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 58 58 76 +== **Key Takeaways** == 59 59 60 -== **Key takeaways** == 61 - 62 62 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: 63 63 64 64 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -68,7 +68,6 @@ 68 68 * Check out the release notes [here] 69 69 * Start thinking about how the license tracker can aid your development 70 70 * Start thinking about major, minor, and patch 71 -* Upgrade to the latest build number 72 72 * Keep making great integrations 73 73 74 74 Let's stay in touch and till next time! ... ... @@ -76,7 +76,6 @@ 76 76 {{info}} 77 77 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 78 78 79 -~*~* Indicates a next-generation-architecture only feature. 80 80 {{/info}} 81 81 ))) 82 82