I can no longer sign my current formed pdf documents after upgrading from Reader 10.1.3 to 10.1.4. The "Done Signing" button is greyed out no matter what I do. This was not an issue in 10.1.3
With the current 10.1.4 release, the functionality of the "Done Signing" button has been changed, to ensure that it only gets enabled once the PDF has been signed i.e. User must place an eSignature first to be able to do "Done Signing".
Can you please see if you are actually signing the Document (by the Place Signature button in the Sign panel), prior to trying to click on Done Signing.
Why has this functionallity been changed?!?! This now means that legacy forms are now useless and redundant. Totally unsatisfatory and is causing lots of issues withing our business. Please can you release an update restoring prior functionallity to this button - I do not understand the reasoning behind this change.
Many thanks - looking forward to hearing from you,
It's interesting. I imagine Adobe never imagined people would ever use this button except when they had signed a document. That's how programmers think: they would never click a "Done X" button unless they had indeed done "X".
Some people might have assumed that "Done signing" by itself signed a document and got in trouble that way. So they are now protected, and should actually be signing it.
I'm curious what the workflow is that people were setting up. What were the end users expected to do?
Well apart from our set up, several big international banks are sending out "signable forms" not for a technical 'signature', but to be filled in and exported as a new pdf independent from the original source file. Most workflows impacted by this poorly thought through change centre around this idea of having a template pdf and then being able to export it with the form filled in as a seperate file. This would be used perhaps when you are reviewing students grades. you open up grade.pdf fill in all of the relevant details, and then click done signing and save the file as joe bloggs age 10.pdf Then when you get to the next child you just open up grade.pdf and repeat.
Well if you do not want to make the form editable, signing it is one solution. Flattening it is another. Enabling Security like password protection or DRM is yet another. The problem with your workflow is that you were using it for an unintended purpose. Now you have been bitten by the changes. As a faculty member, I frequently flatten files that I do not want changed. Can people really change them, of course, but those changes are easy to detect. If you want grades to be official then signing them makes sense. That is one some universities do with digital signatures. But signing without signing, was asking for trouble. It is too easy to be bitten by the rule of unintended consequences.
By the way, if the document is signed without being signed are you sure it cannot be unsigned?
There is no problem with the work flow. It makes sense that legacy features should be supported with updates. If it was not the intended purpose why was this ability available in the first place.
Anyway that is besides the point, I'm yet to see why it was so essential to remove this functionalitly with the update - why not just leave it there?
Europe, Middle East and Africa