Best practices

The following characteristics of LiveCycle and the Signature service result in limitations to the way you can use dynamic Adobe PDF forms:

• Digital signatures are invalidated when a signed form is rendered to PDF.

• The Signature service cannot enforce field-locking (MDP+) signature rules for Adobe PDF forms and Adobe XML forms.

Generally, you must decide whether the use of dynamic PDF forms or the use of digital signatures on the server is more important for your solution:

• If you need to use features of the Signature service that do not support dynamic Adobe PDF forms, use a different type of form and ensure that no rendering occurs in Acrobat or Adobe Reader. (See Ensuring that no rendering occurs after signing.)

• If you need to use dynamic PDF forms, you can convert the form to a non-interactive form before using the features of the Signature service on the form. (See Converting to non-interactive form.)

• Before you use the form with the Signature service, ensure that the form is not a dynamic Adobe PDF form. (See Checking the form type.)

Also, to use digital signatures on forms that users open in Workspace, your form must conform to specific design criteria. (See XREF).

• Order of operations
• Ensuring that no rendering occurs after signing
• Converting to non-interactive form
• Checking the form type
• Requirements for form design and Workspace

 Twitter™ and Facebook posts are not covered under the terms of Creative Commons.