AcroForms Overview
When merging, a form's fields can be completed, the form flattened, form fields removed, existing values from a form field read, and the locations of form fields determined. When merging PDFs, there are also options for modifying pre-existing AcroForms. These topics are covered in the following documentation pages.
| Topic | Description |
|---|---|
| Form Filling | Discusses merging form field values, using AcroForm field values, reorganized AcroForm fields, and FDF files. |
| Form Flattening | Discussed using flattening a form - remove all form field structures from the document and replacing them with their values. |
| Removing Form Fields | Discusses removing form fields from a PDF. |
| Reading Form Fields Values | Shows how to read the values of AcroForm fields from an existing PDF using the Form property of the MergeDocumnt class. |
| Retrieving Form Field Locations | Discusses retrieving the X and Y coordinates of a form field. |
| Marking Form Fields as Read Only | Shows how to mark form fields as read only so they cannot be modified once set. |
These topics discuss working with a pre-existing form. Refer to the Interactive Forms topic for documentation on creating a form.
Form
AcroForm fields are merged using the Form property of the MergeDocument class. The Form property - inherited from the Document class - has a Fields property, a FormFieldList that contains the FormField instances. The FormFieldList contains zero or more FormField instances. You can manipulate a form by flattening it, removing form fields, reading the form field's values and locations, and marking form fields as read only.
Do not confuse the FormField class with the FormElement class and its child classes!
MODIFYING or completing a form using code uses the cete.dynamicpdf.forms namespace while CREATING a form uses the cete.dynamicpdf.pageelements.forms namespace.
This page pertains to the cete.dynamicpdf.forms namespace and the Form class and its children.