Forms in PDF are a critical part of the PDF ecosystem. Fortune 500 companies and governments around the world have adopted and standardized on using PDF forms technology, and built this functionality into their critical workflows.
Most Acroform elements and their properties are supported. Note the following:
Most Forms Central form elements are supported. Note the following:
Unsupported. While Reader Mobile does support Acroforms (forms created by Acrobat’s form tools), it currently does not support the XFA forms created with LiveCycle Designer. Some forms can be filled in and will appear to work, but when you open the forms on another viewer (such as Acrobat), the data isn’t there.
alert(): Support for the parameter cMsg. Both cMsg and nIcon are required, but nIcon is ignored.
10.3: Fully supported except for creating field objects using a naming hierarchy. The getField API takes a field name as parameter and returns a Field object. As long as the field name is a flat name, this API will work.
10.4: Added support for creating field objects using a naming hierarchy.
resetForm(): All paramaters are ignored all form fields are reset.
submitForm(): Implemented to support FormsCentral forms only.
- cURL: The URL to submit to. Value must begin with “https://adobeformscentral.com”.
- cSubmitAs: Indicates the format for submission. Value must be “HTML”.
- cCharset: The encoding for the values submitted. This parameter must be passed but we ignore its value.
Reader Mobile supports a subset of the event properties as follows:
Reader Mobile supports a subset of the forms events as follows:
© Copyright 2012-2013
Adobe Systems, Inc.
Updated Jun 03, 2013.