The feature lets you find out if the document contains any dynamic content or external dependencies.
It also lets you find out if the document contains any constructs such as form fields, multimedia, or Java Script that could affect its appearance.
Another thing I like to do is to display the validation error message on the form in an otherwise hidden field: The problem with our last solution is that if the user saves a partially filled form, and picks it up at a later time, that error message that popped up is long gone, and the only indication that there is something wrong with the form is the modified field color.
So, having a text field contain that error message might be a good idea.
After the “Edit” button is clicked, a new window will open that allows us to edit the new script: This script also includes a check for an empty string, so that the user can wipe out a wrong string and start from scratch.
To start, we create a text field and bring up the properties dialog for the field.
Then we select the “Validate” tab to see the validation options: The default is that the field will not get validated.
When the form is complete, the agency certifies the document, allowing users to change only form fields and sign the document. However, if they remove pages or add comments, the document doesn’t retain its certified status.
You can apply a certifying signature only if the PDF doesn’t already contain any other signatures. A blue ribbon icon in the Signatures panel indicates a valid certifying signature.
You can change the trust settings of certificates to allow specific actions.