My enterprise has subscriptions to individual Creative Cloud apps (e.g. PhotoShop, Illustrator, InDesign, etc), as well as "All App" subscriptions (i.e. the entire Creative Cloud bundle), as well as Acrobat Standard, and Acrobat Professional. Adobe should provide me with alerts when it detects that a user is over subscribing. For example: (1) If a user is assigned an All Apps subscription, an alert should be raised it they are also assigned any other subscription. (2) If a user is assigned 3 or more individual Creative Cloud apps (excluding Acrobat) an alert should be raised since it is more cost effective for them to have an All Apps subscription. (3) If a user is assigned an Acrobat Standard subscription and an Acrobat Professional subscription, an alert should be raised. Named user subscriptions makes it easy for accidental over subscription to occur. Adobe should help customers avoid this by detecting and alerting over subscription.

For my enterprise I subscribe to multiple individual Creative Cloud products (for users who need 1 or 2 products only, since it is more cost effective than an All Apps subscription). I might have 9 of 10 PhotoShop subscriptions assigned, 10 of 10 Illustrator subscriptions assigned, and 11 of 10 InDesign subscriptions just assigned. That means I have to true up InDesign by 1 even though I overestimated my PhotoShop and am 'overpaying' until I am allowed to true it down. All individual subscriptions cost the same, so Adobe should allow me to transfer quantities between products (so I can just reduce PhotoShop by 1 by transferring it to InDesign - bringing InDesign up to 11). The new subscription model is already working in Adobe's favor - the least Adobe can do is provide more value to its customers by creating flexible subscription controls like this.

We just notcied a strange behavior of Acrobat/Adobe Reader (DC 2019.021.20056) and found the root cause:

There's a generated PDF that uses standard fonts which are referenced through the AcroForm default resources entry, too. Strangely the font has a Name entry in its dictionary:

3 0 obj
<</Type/Font/Subtype/Type1/BaseFont/Helvetica/Name/F1/Encoding/WinAnsiEncoding>>
endobj

We add 2 signature fields with our own tool and certify/sign one field. This results in a valid document, which you can download here (https://customers.setasign.com/adobe/document-with-name-in-font.pdf). Do not wonder, there's really only a single line on the page.

When you open this document in Adobe Acrobat or Reader and sign the left field the new signature is fine but the previous one is invalid because of changes which were not allowed. The resulting document is available here (https://customers.setasign.com/adobe/document-with-name-in-font-signed.pdf).

We tracked it down that Adobe Acrobat/Reader simply removes the Name entry from the font dictionary which invalidates the first signature:

3 0 obj
<</BaseFont/Helvetica/Encoding/WinAnsiEncoding/Subtype/Type1/Type/Font>>
endobj

If we remove the Name key before we add the signature fields and the first signature everything runs without any issue.

So from my point of view this seems to be a bug in Acrobat, or? Not to say that the generation library should omit the Name entry, too.

I received this document via email, and it previews fine in my Outlook Client, I downloaded and opened the file to sign, and Acrobat Pro would not display the file correctly. I was under pressure to sign the document, and I ended up downloading Foxit Reader and it read and allowed me to sign the document for free. Later I viewed the same document on my Android device in Acrobat, and the same error was reproduced. I contacted support and they were unable to resolve the issue. I'm would like to elevate this for a resolution. I pay money to use Adobe products, and Acrobat Pro cannot perform this basic task, unlike a free product that is able. I would like to have it work soon.

I need to share a PDF of some confidential documents of our business that are integral to finalising a deal with a new partner. They need to view these documents before they can sign an agreement

I can ensure that they cannot copy, edit or print the PDF, but I cannot stop them from downloading a copy and storing it locally. Even though this copy would also be uncopyable or unprintable they would be able to share their local copy with other people if they shared their password too.

It would be a good feature to stop a local copy being saved, so in the event we decide not to go ahead with the deal I would still have full control over my confidential documents

The "save as" dialog menu in Acrobat Pro (Windows edition) looks counterintuitive, especially the location of "Choose a different folder" button. I've never seen such a menu structure ever. Normally Windows Explorer has a similar thing on the top of the menu. It's a good idea to have a list of recent folders on a screen, but actually I need easy access to other folders on my computer. And it would be great to make this menu looks similar to Windows Explorer. At least I'd place the folder path somewhere at the top of the window (as seen on the screenshot).

The location of the "Choose a different folder" button is very counterintuitive now because normally it is a place for the submit button. I'd left the "Save" or "Ok" button there.

It would be great to improve this dialog box in future editions. Now I ought to spend more time to figure out how can I find a different folder because all other software I use have the standard "save as" dialog boxes.

Acrobat DC is better than 11.x in many ways, but one lost feature is the ability to default opening documents viewed for the first time with 2-up continuous view (or other choices). Downloading pdfs from many sources, pdfs may be single page, single page scroll, etc, with bookmarks or menus open or closed. Acro11 actually worked when setting this default to 2-up. In DC preferences/page display/default layout & zoom, setting to 2-up has ZERO effect on documents opened for the first time. They open in the default of the provider. Please make this function WORK, as it did in v11. It does remember to re-open for user in the view in the previous instance, but that's not good enough. Wasted time and clicks every single download.