Changes for page 213 - Joyful Journeys
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From 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
To version 315.1
edited by Carlijn Kokkeler
on 2023/12/21 14:40
on 2023/12/21 14:40
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,85 +3,79 @@ 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-ups have been achieved.6 +**Hi there, eMagiz developers!** 7 7 8 +== **TBD** == 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. 12 12 13 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]] 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. 12 +== **Feedback Items** == 17 17 18 -//__ Wiretap& debug error messages__//19 - Theerror messagesthatmay bedisplayedwhenusingwiretaps and thedebuggerhavebeenimproved,theseare nowmore userfriendly.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. 20 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. 17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 23 23 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 - == **Formatting& Alignments** ==22 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 26 26 27 -//__ Inputfields__//28 - Multipleputfieldshave beenupdatedsuchthattheyexpandwhen theamount of characters exceedsthedefaultsize.Theseupdatesweredone to catertolargeexpressions.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'. 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. 27 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 32 32 33 -//__ Componentchangesreversion__//34 - In theflowdesignerbug couldoccurwherehechanges toa componentwould be revertedifthe editingpop-upwouldbekeptopenforsomeminuteswithouthavingsaved thechangesyet.Thishas beenfixed.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. 35 35 36 -//__ Stategenerationstatistics__//37 - Thestategenerationgraphswillnowshowthecorrectnumberofcachehits andmisses.32 +//__Broker queue metrics dashboards__// 33 +It is now possible to select the MQTT broker in the queue metrics dashboards. 38 38 39 -//__ Queuebrowser timestamps__//40 - Alltimestampformattingin thequeuebrowser isnowaligned toyyyy-MM-ddHH:mm:ss.SSS.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. 41 41 42 -//__ Additionanddeletionof internal recipients__//43 - Internalrecipientsarenow addedanddeleted correctly.Before,aninternalrecipient couldbeadded andthereafterdeletedautomaticallywhenrefreshingthepage.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. 44 44 41 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 45 45 46 -== **Fe edback Items** ==43 +== **Bug Fixes** == 47 47 48 -//__ Updateflows__//49 - InCreate> Resources,abutton"Updateflows"hasbeenaddedupdateversions ofallflowsinwhicharesourceisused.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. 50 50 51 -//__ Q&Aforumsearch__//52 - Theoption to searchbypressing theEnterkeyhas been added to theQ&Aforum.48 +//__Deployment execution error message__// 49 +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. 53 53 54 -//__ Memorysettings__//55 - Itisnow possibleto changethememory settingsofa containerbeforepressing"Apply to environment". Before,itwasonlypossibletoviewthememorysettingsifcontainerwasrunningonAWSor runningon a docker machine.51 +//__Cloud template upgrade unjust rollback__// 52 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3. 56 56 57 -//__ Runtimevalidation__//58 - Validationforruntimes thatare movedfromon premisesto thecloudorviceversa hasbeenmproved.54 +//__Missing log entries__// 55 +We improved crash handling so that log messages clearly show when and why a container failed to start. 59 59 60 -//__Runtime o verview image versions__//61 - Insightinto invented andactualdeploymentshas beenimproved.If thereleaseversionnumber onruntimesis differentcompared with the release,this is shownintheruntimeoverview.57 +//__Runtime logging__// 58 +We fixed a bug where no new log messages were showing up, even though they were produced by the container. 62 62 63 -== **Bug Fixes** == 60 +//__Next generation block__// 61 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 64 64 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). 63 +//__Feedback deployment plan__// 67 67 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. 70 70 71 -//__Deployment prechecks__// 72 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture. 73 - 74 - 75 75 == **Fancy Forum Answers** == 76 76 77 77 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: 78 78 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"]] 70 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]] 71 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]] 72 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]] 73 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]] 74 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]] 82 82 83 -== **Key Takeaways** == 84 84 77 +== **Key takeaways** == 78 + 85 85 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: 86 86 87 87 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -91,6 +91,7 @@ 91 91 * Check out the release notes [here] 92 92 * Start thinking about how the license tracker can aid your development 93 93 * Start thinking about major, minor, and patch 88 +* Upgrade to the latest build number 94 94 * Keep making great integrations 95 95 96 96 Let's stay in touch and till next time! ... ... @@ -98,6 +98,7 @@ 98 98 {{info}} 99 99 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 100 100 96 +~*~* Indicates a next-generation-architecture only feature. 101 101 {{/info}} 102 102 ))) 103 103