Keep the current single box for 'Installation Program' and ' Uninstall Program' under the 'Programs' tab in a deployment type... however allow admins to select 'granular' switches or arguments.

So in this option, the admin would have:
A 'pre-program install' argument field.
A 'program' field.
And a 'post-program install' argument field.

The same for un-installations.

Additionally to this, I imagine the granular options will have a new window.
This windows should also have a 'explore program' button, which when clicked brings up the potential switches or arguments for EXE / MSI / MSIX / etc. Allowing users to select the options required.

ConfigMgr will then simply populate the original installation / uninstall program field with the one liner, with the full argument.

This will retain the option for admins to either type in, copy paste from another location, or manually select the switches / arguments as needed.

So the deployment template will sit at the 'top' of deployment types of an application.

Admins could then choose which deployment types would use the template in a new tab called, let's say 'deployment types applied to'.

Admins would use tick box options on each tab, to choose what they want to be active in the deployment type template.

So as an example. You could have x86 and x64 deployment types where all the tabs, bar the 'Programs' tab, as set by the template.

This way you set the template once, add the x86 and x64 deployment types and you only need to change the MSI / EXE / etc on each of the deployment types. If you ever need to change the parameters for both the x86 and x64 deployments, unless it's the actual installation program, you'll only need to edit the deployment type template.

Task Sequence Deployments - Immediate Push Failure - Computer Policy initialization from Console.

Forcing a computer policy against a deployment of a Task sequence (any) to run via Software Center, results in failure of downloading of the deployment policy the first time and goes in retry until the agent on the endpoint initiates a polling itself. While SCCM CB is supposed to be user centric and based on Pull methodology, sometimes a deployment needs to be pushed to users immediately and the current behavior causes lot of inconveniences and delays in deploying Task sequence based installations via Software Center (Immediate Push and not a schedule in future). This behavior can be replicated in the following way -
1. Create a deployment of a TS including an application.
2. Initiate Computer policy on the targeted collection.
3. Check for the errors in execmgr.log indicating that the policy of the respective deployment was not found in WMI and will re-try.
4. Agent is able to pull the policy in next retry after a set schedule (Specific to each endpoint)

Currently when we want to run PowerShell commands in an ConfigMgr Application we need to wrap them in a script or run them with powershell.exe -command and make it a oneliner. This is because it's always triggered from cmd.exe.
Would be nice to be able to choose to directly start PowerShell.exe and just run the PowerShell command.
An example of what I'd like to achieve is to simply add that command in the "installation program" field.
Add-WindowsCapability -Online -LimitAccess -Name Tools.Graphics.DirectX~~~~0.0.1.0 -Source .
Currently we have to use this oneliner instead which is far more complex.
Powershell.exe -NoLogo -NoProfile -NonInteractive -Command "Add-WindowsCapability -Name "Tools.Graphics.DirectX~~~~0.0.1.0" -Online -LimitAccess -Source (Get-Location).Path ; if (!$?) { $Host.SetShouldExit($Error[0].Exception.HResult) }"

Problem: When an application has "require approval" enabled we get a long list of users or devices where this application is approved for. But when I add a new application and delete the old, I loose all approvals! And the users need to request again.

This is a problem in multiple cases:
1) Example 1: We have an application in version 1.0.1 that and get a new version 1.0.2 I want to make a new application and test this. When it is tested I want to turn on "superceede" and then remove the old application. The license is still valid for all that got the previous version approved, so these users should not need to request a new approval. And new users should request the new version from Software Center

2) Example 2: We have a software in a major version and get a new version in a newer major version. For instance we may have Visio 2016 and then we want to use Visio 2019. Again I want to create a new application, test this, and then when it is tested automate upgrade. We have enterprise license so all users that are approved for 2016 version are allowed to use 2019. No need for new approval.

--
If it is difficult to add the feature in the console itself, a powershell script would be OK.

Br
Torstein