Home → Using LincDoc 3.0 → Signatures → Mobile signatures

12.3. Mobile signatures

Mobile signatures

When using LincDoc on mobile devices, the signature type specified in the form by the form administrator is overridden to use a method native to the mobile device.  Currently, only the iPad is supported by LincDoc.

Prerequisites

  • Valid LincDoc Signature Capture license
  • Signing certificate – this can be acquired through LincWare or any of Adobe's CDS providers
  • PDF document with signature field(s)
    • Note: the minimum size of a signature field is 20 pt x 20 pt (using Adobe Acrobat measurement tools)
    • Note: Word source documents are not supported with this signature type at this time
  • iPad

Set-up Procedure

In LincDoc's administrator interface (using the standard LincDoc application), complete the following

  1. Upload the signing certificate (Note: This step must only be completed once. Once the certificate is set up, it can be used repeatedly, and for any signature type.  If this step has been completed, move to step 2)
    • Under the desktop System menu, select upload signing key
    • Fill in the appropriate fields 
      • Format – the format of the certificate.  If LincWare is your signature certificate provider, it will be a Java keystore.  If the certificate is from Adobe, it will be of the PKCS#12 format.
      • Upload file – upload your certificate file
      • File password – the certificate password
      • Private key password – the private key password
  2. Add an Adobe digital signature to your PDF document
  3. Commit the document and reparse to enable configuration in LincDoc
  4. Set up the appropriate fields via the administrator interface.
    • Set the field type to signature
    • Set the signature provider.  If this form is going to be used with standard LincDoc instances as well as on mobile devices, set the signature provider to the one that will be used for the standard instance.  If this form will be is a mobile only form, set the signature provider to On-Screen Canvas.  Although the signature provider is overridden when using the form on a mobile device, there are expectations of additional security when the signature provider is set as a Topaz signature pad.
    • Choose which person will be signing this field
    • Select the certification level:
      • None
      • Not Certified
      • Form Filling Allowed
      • Form Filling and Annotations Allowed
      • No Changes Allowed
    • Choose which fields to lock (if any)
    • Check exempt from flattening
  5. Set the trust levels for the certificates in order to validate signatures.
    • Click on the validity unknown icon in the upper right corner of the screen
    • Follow the directions to set up the trust levels for the certificates in Adobe Acrobat (or Reader)

Signer name field

Defines the field value that will be used in the signature signing process.  This must either be the current LincDoc user or a field in the document that will be filled out with the signer's name.  For example, suppose a document has a field called "first_signer", which will be filled with the name of the person who will be signing the document.  By placing first_signer into Signer name field, when the user selects sign inside the generated document, the name typed into first_signer will be used to populate the list of signature fields to sign.

Certification Levels

A certification level is set when the first signature is applied. Once set, it cannot be changed without invalidating existing signatures. Any changes not allowed by the level will result in the signature being marked as invalid. Changes since a signature has been applied can be listed by clicking on the signature. The signed version of the document may be seen by clicking on the signature.
  • Not Certified: Additional signatures may be added. Changes to the document and the form data may be made. Document meta-data may be added.
    • Use case: You have a document detailing a proposal.  In order to fill this out the form must be approved.  However, the contents of the form may be subject to change (new sections, schedules, etc...).  This certification level would be used in this case.
  • Form Filling and Annotations: Additional signatures may be added. Editable form fields may be changed or locked. Annotations may be added. Document meta-data may be added.
    • Use case: Suppose that your documents need to be annotated after signing, you must choose this option.
  • Form Filling: Additional signatures may be added. Editable form fields may be changed or locked. Document meta-data may be added.
    • Use case: Suppose that there is an office only section of a form that must be completed after the rest of the form is signed. This certification level will allow this functionality
  • No Changes Allowed: No additional signatures may be added. All form fields are set to read-only. No changes may be made at all.
    • Use case: You have a document that once signed, such as a contract, that cannot be modified.  This certification level will essentially lock all fields.

Note: These options only affect the ability of the PDF to be modified through Adobe Acrobat.

Fields to lock:

These are the fields that will be locked – which prevents the user from changing the values after a signature has been applied to the document.  Consider the following:

In this example, once the signature is applied, the fields Order_Number and Total_Price will be locked.  They can no longer be edited through Adobe Acrobat.  If a document is reopened in LincDoc, the signature is removed – the document is no longer signed.

Exempt from flattening:

This must be selected for any signature field if flatten generated PDFs is checked under PDF options on the Other Options tab. If it is not, the signing process will fail and an error will be shown.

Knowledge Tags
signatures  /  mobile  / 

This page was: Helpful | Not Helpful
← 1. eForms design