Currently, under "Manage installation logging", it is possible to select the folder where logs will be generated when the installation/update of a software occurs. The logname is based on the installer's filename (i.e. for Github CLI 2.32.0 --> gh_2.32.0_windows_amd64.msi.log).
Some installer don't have a very evocative name, especially for helpdesk looking for recent changes on a device. Or one may want to standardize the name of the log based on the application name instead of the installer's filename. Something like "%ApplicationName% %Version% %Action%.log"
Keeping Github CLI as an example: "GitHub CLI 2.32.0 Install.log", "GitHub CLI 2.32.0 Update.log", "GitHub CLI 2.32.0 Uninstall.log"
--> For this purpose, one could choose to rely on the "Modify command line" feature instead. I see various reasons why this could not be sufficient:
"Manage installation logging" can be set at the top-most node "All Products", and replicate over all the child products;
There is no %Version% variable available in "Modify command line";
Biggest drawback: when modifying the command line to specify log location, if the destination folder does not exist, msiexec would quit with error 1622. On the other hand, when relying on "Manage installation logging", ScriptRunner seems to create the destination folder beforehand -- and thus allow msiexec to generate the logfile. (Here I'm specifically targeting msiexec, but I'm sure other installers could also fail for this reason.)
Submitted https://ideas.patchmypc.com/ideas/PATCHMYPC-I-3176 for the second part of the suggestion, so both suggestions could be evaluated independently.