A paper forms barcode
electronically captures user-supplied data in an interactive PDF
form. When an end user fills the form using Adobe Reader or Acrobat, the
barcode is updated automatically to encode the user-supplied data.
The user can then return the filled form by printing it and returning
it by fax, mail, or hand. Upon receipt, the user-supplied data can
be decoded using a scanning device.
To use the paper forms barcode object, your organization must
have implemented Reader Extensions.
The Barcoded Forms solution provides a workflow where users completes
the form using Adobe Reader and the data is automatically encoded
into the barcode. After the form is printed and the paper copy returned
to you, you can extract the form data by using a common barcode
scanner. The result is 100% data accuracy, eliminating the need
for rekeying data.
Using the paper forms barcode in a form eliminates the need for
manual data entry or OCR-based forms processing. Data captured from
fill-and-print paper forms can be reinserted into the electronic
workflow quickly and accurately, with no loss of data caused by
scanning or manual rekeying mistakes. Furthermore, you can retain
a digital copy of the transaction, complete with ink signatures.
For example, a company has a PDF form that can be filled electronically.
However, the form requires the user’s signature; therefore, the
completed form must be printed, signed, and returned by fax or mail.
By including a paper forms barcode on the form, the data entered
electronically is encoded into the barcode. When the printed form
is returned, a barcode reader can read all of the captured data into
a structured data file. Only the signature needs to be verified.
Note: The paper forms barcode object cannot be used
on a form saved as an Acrobat 6.0-compatible PDF form. Users filling
a form that contains a paper forms barcode require Acrobat 7.0 or
later, or Adobe Reader 7.0 or later for PDF 417 barcodes, and Acrobat
7.0.5 or later, or Adobe Reader 7.0.5 or later for QR Code and DataMatrix barcodes
in order for the barcode to encode the captured data.
How the paper forms barcode works
The
paper forms barcode object is a two-dimensional (2D) barcode that
is encoded with an industry standard PDF417, QR Code (Version 2),
or DataMatrix (the ECC200 model) symbology. It includes an intelligent
calculation script that encodes the data captured in a form’s fields.
You select the form fields to be encoded by the paper forms barcode.
However, because the barcodes have limited storage capacity, it
is important that you select only required fields.
After you add a paper forms barcode to the form design, you specify
its properties so that it behaves in the manner appropriate for
your requirements. Using the Object palette, you can define these
properties and others for the paper forms barcode:
Barcode label
Symbology encoded in the barcode
Scanning method used to decode the paper forms barcode
Error correction level, and the module width and height of
the barcode (when you choose a custom scanning method)
Object’s visibility on the form
Data compression options
Form data to include in the barcode
Data format that the paper forms barcode uses to encode data
and the fields to be included
When you distribute your finished form, users fill the form,
print it, and return it. After received, the user-supplied data
is decoded by using a scanning device.
Consider the following points when designing forms that include
the Paper Forms barcode object:
The Paper Forms Barcode object encodes data that users
type in a fillable PDF form. The use of paper forms barcodes for
paper forms processing requires Reader Extensions.
Users must use Acrobat or Adobe Reader 7.0.5 or later to
fill a form using QR Code or Data Matrix Paper Forms Barcode. Therefore,
form authors must not save the form as either Acrobat 7.0.5 Compatible
or Acrobat 6.0.2 Compatible.
Users must use Acrobat or Adobe Reader 7.0.5 or later to
fill a form that includes the PDF417 Paper Forms Barcode.
Note: To make use of the paper forms barcode, your organization
must have implemented Reader Extensions.