Currently under the Role Base Access, if you have full control to an application, and wish to add SuperSedence to an application the User only has read access to, you are unable to do that. The ability to do this is currently available when adding a dependency on an existing app the user only has read rights to.

It would great to see the feature where collections above a certain number of members are hidden made available to the application deployment wizard, rather than just task sequences.

While applixation deployment may not be as high a risk, I'm sure it would provide a lot more reassurance for users new to SCCM and the application deployment process.

It would be great if an supersedence could be created for programs not deployed via SCCM (or previously deployed via packages). I find myself creating "dummy" applications just for a detection, so that we can automatically upgrade applications that are "Available". In other words, often times we don't care that you installed a specific program, but we do care that if it is installed it's up to date. Maybe when selecting the Application and Deployment type to supersede an additional option to supersede base on a detection rule set could be added?

It would be nice if an Software Package is required in the Future to set a specific Time when a Software CAN be automatically installed ! E.g. : Deployment availability: NOW
Requirement Date of a Software Install: 5 Weeks
Recommended Date of a Software Install: 2 Weeks

If a Client Shutdown after the Date of Recommend Date of Software Deployment is reached SCCM have to install the Application/Update.

Lot of Customers doesn't like to reboot the PC if there is an important security issue or Preparing for a new Software Upgrade.

Allow the option of changing the client cache size on a per application basis.
Large applications can then be installed and if set to not persist in client cache, the cache is then resized to the global site default

Ability to deploy multiple applications to single collection at once, like with this application http://www.vanhatalo.eu/projects/tva_SMAD/v13/ I have made.

Allow us to choose where to publish applications for the users. Alot of applications are still installed in Task sequences and it would be great to be able to deploy these and present them in the application catalog.

The users are getting confused when some applications are in software center and some in application catalog. Please let us have a one stop shop for this.

When creating a file detection type, it would be lovely if it were possible to use a standard file type dialog as opposed to the current dialog.

The application detection method only runs in the user context if it is deployed to a user collection. This would be reasonable if the Deployment Type user experience were set to "Install for User" (User context), however the detection method runs in the user context when this is set to "Install for system" installation behavior (SYSTEM context).

For the same reasons that computer and collection variables are useful and strategic for OSD, they would also be with the application model. Examples:
+ Customizing command-line parameters for installation
+ Leveraging in scripts for the protection of secret/sensitive data like passwords or product keys

Sometimes you just need to have an app that is detected successfull when something is not existing. Delete files or registry keys etc. It would be nice if there was a logical operator in app detection to select a file and then mark a box "NOT" or "DOES not exist" to tell the detedetection system that we are done when thi thing does not exist anymore.
Now we need to use ps-scripts (to return something when file is not detected and nothing when it is detected) to achieve this, like:

$strFileName="c:\temp\test.txt"
If (Test-Path $strFileName){

}Else{return $true}

If you have e.g. Oracle as dependency set for ~50 applications and a new version is available, you have to manually update all 50 deployment types with this new dependency version.

If you only supersede it, the main applications which are using this as a dependency do not show up in softwarecenter anymore.

There must be a possibility to have an overview of dependent applications and update all of them with one click or exclude some for certain reasons.

Right now there is no way to distinguish between flavors of Windows 10 when configuring OS-based Application requirements. Please split it up into different OS flavors such as 1507, 1511, 1607, 1703...etc.

Please allow us to export and import global conditions. The code exists somewhere since this can be done when exporting and importing applications. Bonus points for Powershell cmdlets.

We can turn off software updates, hw inventory, sw inventory, and even the ability to remote control with the client, but there isn't a way to easily disable software deployments (application and packages). In healthcare, we have machines that we cannot patch so we turn off the update component as an added layer of protection. We also have systems we do not want software deployed to as well and there are ways to try and prevent targeting, just turning off that component on the client would be much easier with a client setting option.

This article (http://blogs.technet.com/b/configmgrteam/archive/2015/08/20/faster-virtual-app-publishing-at-first-logon-for-np-vdi-environment-in-configmgr-sp2-and-r2sp1.aspx) makes it clear that if I want to download and execute an app to a laptop, but also stream to a VDI, that to get fast channel to work, I need 2 apps instead of one app with 2 DTs. That doubles our work and doubles our chance of making mistakes.