Use QCDS Signer Information Fields

Signer Name, First Name, Last Name, Email, Phone, Address, Company, and Title/Position; which are editable, which are evidence-sensitive, how values prefill, and what can write back to a Contact after successful signing.

This guide applies to All plans; sender and signer 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

  • Open the current Template draft in the visual builder and confirm the PDF page you are editing is visible before placing or moving fields.
  • Decide which fields are signer-interactive, which are fixed creator content, and which values should be entered at Request time.
  • Keep assignment and required-state decisions intentional; the builder can publish reusable unassigned fields, but Send Now requires all interactive fields to resolve correctly.

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.

Signer Name, First Name, Last Name, Email, Phone, Address, Company, and

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 Use QCDS Signer Information Fields, 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.

Which are editable, which are evidence-sensitive, how values prefill, and

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 Use QCDS Signer Information Fields, 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.

How This Fits into the QCDS Workflow

Field choice determines both the signer experience and the evidence rendered into the final artifact. Use the current streamlined palette for new Templates; legacy registry types may remain readable for compatibility but are not the design target for new work.

Field properties should communicate a clear signer task. Required fields should be discoverable, signer-information fields should reflect the participant snapshot, and fixed creator content should not masquerade as editable signer input.

Verify the Result

  • A real test message leaves Joomla and arrives at the intended mailbox with the correct sender identity and format.
  • The Template validates and a new test Request renders the expected field/content behavior without changing older Requests.
  • 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.
  • Troubleshooting QCDS message content before confirming Joomla itself can send mail.
  • Editing the characters inside a supported token or translating the token name.
  • Asking signers to sign again when only final PDF generation or completion delivery failed.

Troubleshooting

  • If the email does not arrive, test Joomla mail, check QCDS delivery history, then distinguish authentication/connection problems from a rejected recipient address.

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.