Create a New QCDS Template from a PDF

Use Add Template, name it, upload the PDF source, create/open the builder, and understand that each upload is stored as that Template's unique protected source document.

This guide applies to All plans; sender and follows the accepted QC Digital Signature 2.0.7 implementation. Where older walkthrough language differs from the current interface or source behavior, use the current QCDS state as the authority.

Before You Begin

  • Start with a clean PDF. QCDS current Template intake is PDF-only; convert DOC/DOCX or other source formats to PDF before upload.
  • Choose a stable document layout before placing fields because field coordinates are tied to the PDF page geometry.
  • Use a simple test PDF first when diagnosing rendering or placement so document complexity is not confused with a builder problem.

Step-by-Step Workflow

  1. Open QCDS > Templates and click Add Template.
  2. Enter a clear Template name.
  3. Choose Upload PDF and select the PDF source for the Template.
  4. Choose Create & Open.
  5. Wait for QCDS to store the protected source and open the visual builder, then confirm every page renders before placing fields.

Add Template

A Template is reusable document preparation. It stores the protected PDF source, field layout, assignments/properties, and published version used to start future Requests. Editing and publishing a later Template version does not rewrite Requests that were already sent. The Use action should be treated as the handoff from reusable preparation into one transaction-specific Request.

For Create a New QCDS Template from a PDF, verify this behavior using the actual object involved rather than a generic assumption. A global administrator setting, a sender-workspace preference, a reusable Template, and a sent Request have different ownership and history rules. QCDS is intentionally designed so changes for future work do not silently rewrite the evidence of an already-sent transaction.

Name it

A Template is reusable document preparation. It stores the protected PDF source, field layout, assignments/properties, and published version used to start future Requests. Editing and publishing a later Template version does not rewrite Requests that were already sent. The Use action should be treated as the handoff from reusable preparation into one transaction-specific Request.

For Create a New QCDS Template from a PDF, verify this behavior using the actual object involved rather than a generic assumption. A global administrator setting, a sender-workspace preference, a reusable Template, and a sent Request have different ownership and history rules. QCDS is intentionally designed so changes for future work do not silently rewrite the evidence of an already-sent transaction.

Upload the PDF source

A Template is reusable document preparation. It stores the protected PDF source, field layout, assignments/properties, and published version used to start future Requests. Editing and publishing a later Template version does not rewrite Requests that were already sent. The Use action should be treated as the handoff from reusable preparation into one transaction-specific Request.

Create/open the builder

A Template is reusable document preparation. It stores the protected PDF source, field layout, assignments/properties, and published version used to start future Requests. Editing and publishing a later Template version does not rewrite Requests that were already sent. The Use action should be treated as the handoff from reusable preparation into one transaction-specific Request.

And understand that each upload is stored as that Template's unique

A Template is reusable document preparation. It stores the protected PDF source, field layout, assignments/properties, and published version used to start future Requests. Editing and publishing a later Template version does not rewrite Requests that were already sent. The Use action should be treated as the handoff from reusable preparation into one transaction-specific Request.

How This Fits into the QCDS Workflow

A Template is reusable preparation, not a live signature transaction. QCDS versions published Template work so future Requests can use a new layout while older sent Requests remain based on their frozen snapshot.

Use Template versioning as the safety boundary: improve future preparation without altering the immutable snapshot already attached to an older Request.

Verify the Result

  • The Template validates and a new test Request renders the expected field/content behavior without changing older Requests.
  • The Completed PDF/Package opens, preserves the signed source and evidence, and the Audit Trail remains readable.
  • A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

  • Publishing before running Validate and resolving actual configuration problems.
  • Assuming a later Template edit will update a Request that was already sent.
  • Asking signers to sign again when only final PDF generation or completion delivery failed.
  • Replacing a prior valid artifact before a regeneration attempt has been verified.

Troubleshooting

  • If the PDF preview or completed artifact fails, reproduce with a small known-good PDF and check QCDS Status/Scheduled Task health before changing field data.

Operational Best Practice

Test meaningful changes with controlled data before relying on them in production. Keep QCDS, Joomla mail, Scheduled Tasks, and entitlement health observable; preserve successful Requests and completed evidence; and make the smallest change that solves the actual problem. For handoff or support, record the QCDS version, relevant Request/Template reference, the exact action taken, and the visible result without including secrets.

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.