Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 360.1
edited by Carlijn Kokkeler
on 2024/01/29 14:41
on 2024/01/29 14:41
Change comment:
There is no comment for this version
To version 317.1
edited by Carlijn Kokkeler
on 2023/12/21 14:45
on 2023/12/21 14:45
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,80 +3,76 @@ 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 -== **Pop-up Improvements** == 9 -//__Property releases__// 10 -When a new property release is created, this property release can now be viewed and deleted. 8 +== **TBD** == 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 13 13 14 -//__Runtime deletion__// 15 -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 -//__Wiretap & debug error messages__// 18 -The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly. 12 +== **Feedback Items** == 19 19 20 -//__ Actionmessages__//21 - Theformattingofactionmessagesregarding changesinretentionbytes/hourshasbeenimproved.The actionmessagewill nowdisplaythecorrect,actualbehaviour.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. 22 22 23 -== **User Journey** == 24 -//__Update flows__// 25 -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]] 26 26 27 -//__ Inputfields__//28 - 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. 29 29 30 -//__UI improvements__// 31 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved. 22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 32 32 33 -//__ Q&A forum search__//34 - Theoption tosearchbypressingtheEnterkeyhasbeenaddedto theQ&Aforum.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'. 35 35 36 - ==**FeedbackItems** ==27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 37 37 38 -//__ Memorysettings__//39 - Itis now possibletochangehememorysettingsofacontainerbeforepressing "Apply to environment".Before,itwasonlypossibletoviewthe memorysettings ifacontainerwasrunningonAWSorrunningonadockermachine.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. 40 40 41 -//__ Runtimevalidation__//42 - Validationforruntimesthat are movedfrom on premisestothecloudorviceversahaseen improved.32 +//__Broker queue metrics dashboards__// 33 +It is now possible to select the MQTT broker in the queue metrics dashboards. 43 43 44 -//__Runtime overview image versions__//45 - 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. 46 46 47 -== **Bug Fixes** == 38 +//__Runtime restart or redeploy overview__// 39 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 48 48 49 -//__Removal of onramp__// 50 -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). 41 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 51 51 52 -//__Component changes reversion__// 53 -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. 43 +== **Bug Fixes** == 54 54 55 -//__ Stateneration statistics__//56 -The s tate generationgraphs will now show the correct numberof cache hits andmisses.45 +//__Message throughput__// 46 +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. 57 57 58 -//__ Runtimestatisticsdetails__//59 - Wefixedan issue whereheapmemoryusage datawasaccumulatingwhenzoomingoutin the runtimestatistics detailsdashboards.48 +//__Cloud template upgrade unjust rollback__// 49 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks. 60 60 61 -//__ Queuebrowsertimestamps__//62 - Alltimestampformattinginthequeuebrowseris now aligned toyyyy-MM-dd HH:mm:ss.SSS.51 +//__Missing log entries__// 52 +We improved crash handling so that log messages clearly show when and why a container failed to start. 63 63 64 -//__ Deployment prechecks__//65 - Duringdeploymentsprechecks will bedone onruntimesthatstillhaveto bedeployedfromdeployarchitecture.54 +//__Runtime logging__// 55 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 66 66 67 -//__ Additionand deletionof internalrecipients__//68 - Internalrecipients are nowadded and deleted correctly. Before, an internalrecipient couldbeaddedandthereafterdeleted automaticallywhen refreshingthepage.57 +//__Next generation block__// 58 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 69 69 60 +//__Deployment execution error message__// 61 +In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up. 62 + 70 70 == **Fancy Forum Answers** == 71 71 72 72 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: 73 73 74 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]] 75 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]] 76 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]] 67 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 68 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 69 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 70 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 71 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 77 77 78 -== **Key Takeaways** == 79 79 74 +== **Key takeaways** == 75 + 80 80 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: 81 81 82 82 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -86,6 +86,7 @@ 86 86 * Check out the release notes [here] 87 87 * Start thinking about how the license tracker can aid your development 88 88 * Start thinking about major, minor, and patch 85 +* Upgrade to the latest build number 89 89 * Keep making great integrations 90 90 91 91 Let's stay in touch and till next time! ... ... @@ -93,6 +93,7 @@ 93 93 {{info}} 94 94 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 95 95 93 +~*~* Indicates a next-generation-architecture only feature. 96 96 {{/info}} 97 97 ))) 98 98