Detection methods supported in the generic detection script (PowerShell) - only work for MSI or Registry. One application, Adobe Digital Editions, currently can only be properly detected by looking at an info attribute of the installed exe file, such as file modified date.
Please enhance the detection rule capability to include the sort of info that Config Manager file type detection can offer.
I suggest doing it in a similar way to how you have Registry detection (eg you use a multi-layer hash parameter and a function in the PowerShell detection script, and your publishing service likely has other things that service around this).
This will fix the detection issue for Adobe Digital Editions, and likely improve the range of other products you can reliably detect.