by default .. all apps are assigned to "default" scope.
If you choose a SCOPE.. you then define a powershell detection script to identify membership in that scope.. and an order of evlauation.
Then Allow a defined scope to be selected for each application/update.. with different settings. If you define a scope for a piece of software.. it gets added to sccm/wsus with the Scope added to the application name so it can be identified as being applicable to that scope. (so you could end up with multiple sccm application installs for each)
yes ,, i support a univeristy with multiple it groups.. each needing to apply different settings for software deployments. Each is seperated by an sccm SCOPE. but they all have READ rights to "default" scope.. so they can copy/duplicate a shared app install.
Is your biggest use case having an option to have multiple profiles (like customizations of an application) such as different command lines etc?
never mind.. then.. i retract my votes.
We may look at adding custom application scopes. We wouldn't provide any of the additional options you mentioned with scripts.