Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From 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
To version 312.1
edited by Carlijn Kokkeler
on 2023/12/21 14:26
on 2023/12/21 14:26
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 +211 - Log Luminary - Content
-
... ... @@ -3,78 +3,71 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** This release ....6 +**Hi there, eMagiz developers!** 7 7 8 +== **TBD** == 8 8 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. 13 13 14 - [[image:Main.Images.ReleaseBlog.WebHome@release-blog-213-joyful-journeys-property-release.png]]12 +== **Feedback Items** == 15 15 16 -//__Runtime deletion__//17 -W hendeletingaruntime,the errormessage that isdisplayed ismoredescriptive.The error messageswillnowincludethe namesof theflowsthatrunonthecontainer.14 +//__Runtime overview__// 15 +We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview. 18 18 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. 17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 21 21 22 -//__ Inputfields__//23 - Multiple inputfieldshave been updated such that theyexpand whenthe amountofcharactersexceedsthe defaultsize. These updateswere doneto caterolargeexpressions.19 +//__Missing properties overview__// 20 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 24 24 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. 22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 27 27 28 -//__ Runtimevalidation__//29 - Validationfor runtimes that aremovedfromonpremisesto thecloudorviceversahas beenimproved.24 +//__Breaking changes pop-up__// 25 +Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'. 30 30 31 -//__UI improvements__// 32 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 33 33 34 -//__ Q&A forumsearch__//35 -The o ptiontosearch bypressingthe Enterkeyhasbeen added to theQ&Aforum.29 +//__External recipients emailaddress__// 30 +The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users. 36 36 37 -//__ Wiretap& debugerrormessages__//38 - Theerrormessagesthatmay be displayedwhenusingwiretapsandthedebuggerhave been improved,theseare now more user friendly.32 +//__Broker queue metrics dashboards__// 33 +It is now possible to select the MQTT broker in the queue metrics dashboards. 39 39 40 -//__Runtime overview image versions__//41 - Insightintoinventedand actualdeploymentshasbeenimproved. Ifthereleaseversionnumberruntimes is differentcomparedwith therelease,thisisshownin theruntimeoverview.35 +//__Runtime image version__// 36 +The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment. 42 42 43 43 == **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. 46 46 47 -//__ Removalof onramp__//48 - Wefixed an issuewhere itwasnot possibletoremovethelastonramplinkedasplitted entry(thatwas an all-entrybefore).40 +//__Message throughput__// 41 +The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases. 49 49 50 -//__ Component changesreversion__//51 -In theflow designerabugcouldoccurwherethechanges to acomponentwouldberevertedifthe editingpop-upwouldbekeptpenforsomeminutes withouthavingsavedthechangesyet. Thishasbeenfixed.43 +//__Deployment execution error message__// 44 +In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup. 52 52 53 -//__ State generationstatistics__//54 - Thestategenerationgraphswillnowshow the correctnumberofcachehitsandmisses.46 +//__Cloud template upgrade unjust rollback__// 47 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3. 55 55 56 -//__ Runtimestatisticsdetails__//57 -We fixed anissuewhere heapmemoryusagedata wasaccumulatingwhenzoomingout in theruntimestatistics detailsdashboards.49 +//__Missing log entries__// 50 +We improved crash handling so that log messages clearly show when and why a container failed to start. 58 58 59 -//__ Queue browsertimestamps__//60 - Alltimestampformattinginthequeuebrowserisnowalignedto yyyy-MM-ddHH:mm:ss.SSS.52 +//__Runtime logging__// 53 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 61 61 62 -//__Deployment prechecks__// 63 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 64 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 67 57 + 68 68 == **Fancy Forum Answers** == 69 69 70 70 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: 71 71 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"]] 62 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 63 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 64 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 65 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 66 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 75 75 76 -== **Key Takeaways** == 77 77 69 +== **Key takeaways** == 70 + 78 78 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: 79 79 80 80 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -84,6 +84,7 @@ 84 84 * Check out the release notes [here] 85 85 * Start thinking about how the license tracker can aid your development 86 86 * Start thinking about major, minor, and patch 80 +* Upgrade to the latest build number 87 87 * Keep making great integrations 88 88 89 89 Let's stay in touch and till next time! ... ... @@ -91,6 +91,7 @@ 91 91 {{info}} 92 92 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 93 93 88 +~*~* Indicates a next-generation-architecture only feature. 94 94 {{/info}} 95 95 ))) 96 96