Assign QCDS Template Fields to Contacts or the Sender

Search saved contacts, choose an assignee, assign fields during Template preparation when useful, and understand that assignments may remain incomplete until Request creation.

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 the Template draft in QCDS and wait until the PDF is visibly rendered.
  2. Make the field/layout/content change described in this guide.
  3. Review assignment, Required state, links/options, and page placement.
  4. Run Validate and correct every real problem before publishing.
  5. Save/publish, then start a test Request to verify the signer and Completed PDF behavior.

Search saved contacts

A QCDS Contact is reusable workspace data for a real participant. It can hold name information, company, title, phone, consolidated address, one or more email addresses, a Preferred Language, and private Notes. The Contact is not the historical Request itself: when a Request is sent, QCDS freezes participant data into the transaction so later Contact edits do not rewrite prior evidence. Signer-correctable profile fields can update the saved Contact after successful signing where the current field behavior allows it.

For Assign QCDS Template Fields to Contacts or the Sender, 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.

Choose an assignee

A QCDS Contact is reusable workspace data for a real participant. It can hold name information, company, title, phone, consolidated address, one or more email addresses, a Preferred Language, and private Notes. The Contact is not the historical Request itself: when a Request is sent, QCDS freezes participant data into the transaction so later Contact edits do not rewrite prior evidence. Signer-correctable profile fields can update the saved Contact after successful signing where the current field behavior allows it.

For Assign QCDS Template Fields to Contacts or the Sender, 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.

Assign fields during Template preparation when useful

A QCDS Contact is reusable workspace data for a real participant. It can hold name information, company, title, phone, consolidated address, one or more email addresses, a Preferred Language, and private Notes. The Contact is not the historical Request itself: when a Request is sent, QCDS freezes participant data into the transaction so later Contact edits do not rewrite prior evidence. Signer-correctable profile fields can update the saved Contact after successful signing where the current field behavior allows it.

And understand that assignments may remain incomplete until Request creation

A QCDS Contact is reusable workspace data for a real participant. It can hold name information, company, title, phone, consolidated address, one or more email addresses, a Preferred Language, and private Notes. The Contact is not the historical Request itself: when a Request is sent, QCDS freezes participant data into the transaction so later Contact edits do not rewrite prior evidence. Signer-correctable profile fields can update the saved Contact after successful signing where the current field behavior allows it.

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.
  • Request Details shows the expected lifecycle, participant, Timeline, and delivery state after the action.
  • 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.
  • Cancelling/recreating an otherwise valid Request just to repair one failed email address.
  • Leaving transient unsent work and expecting it to appear later as a persistent draft Request.

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.
  • If the Request is partly successful, preserve it and repair the failed participant/delivery step. Successful links and recorded history should remain usable.

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.