Use Document Attachment Fields

Use a Document Attachment field when a signer must supply one supporting image during signing. QCDS 2.0.7 accepts one PNG or JPEG per attachment field, stores the protected original, and includes attachment evidence with the completed Request.

What a Document Attachment Field Accepts

A Document Attachment is a signer-input field. The current signer app accepts one PNG or JPEG image for that field. The server independently inspects the upload, confirms the detected image type, passes it through the protected quarantine/storage path, and records its SHA-256 evidence.

This field is not a general document uploader. PDFs, Word files, and arbitrary file types are not accepted by the current Document Attachment workflow.

Add the Field to a Template

  1. Place Document Attachment on the intended page.
  2. Give it a clear label that tells the signer what image to provide.
  3. Assign it to the correct signer role.
  4. Enable Required when the signer must upload the image before completion.
  5. Choose whether the attachment image should be displayed normally in the completed PDF.
  6. Save, Validate, publish, and test the Template.

What the Signer Experiences

The signer sees an Upload Image control. After a successful upload, QCDS shows the file name and allows the signer to replace the image while the signing session is still editable. Unsupported image types or uploads that fail inspection are rejected rather than being attached to the Request.

A Required Document Attachment is complete only after QCDS has a protected stored object and a valid SHA-256 value for the upload.

What Happens at Completion

QCDS appends attachment presentation pages to the completed document set and records which signer supplied each attachment. If the Request contains at least one completed Document Attachment, the sender's normal completed-download action changes from Download Completed PDF to Download Completed Package.

The completed package contains the completed PDF artifact(s) plus the original signer attachment image files. This is important when an attachment is configured for privacy-obscured presentation: the PDF can obscure the visible presentation while authorized package access still preserves the original evidence.

Test the Entire Attachment Path

  1. Send a test Request to an address you control.
  2. Upload a PNG or JPEG through the signer link.
  3. Replace it once to confirm the active-session behavior.
  4. Complete the Request.
  5. Verify the completed PDF presentation and download the Completed Package to confirm the original image is present.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.