Complete Text, Date, Checkbox, and Dropdown Fields as a Signer

How each current signer-input field behaves, required/optional completion expectations, and how the final values are frozen into the completed Request evidence.

This guide applies to All plans; external 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

  • Treat the signer link as personal transaction access. Do not publish, forward, or paste it into public support posts.
  • If Level 2 Identity Verification is required, confirm the applicable Didit or Shufti provider profile is configured and tests successfully before sending.
  • Test the signer experience in a normal browser/mobile context, not only while logged into Joomla as an administrator.

Step-by-Step Workflow

  1. Open the secure signer link in the intended signer/browser context.
  2. Complete any required Identity Verification step before signing if the Request requires it.
  3. Work through the assigned fields and correct any allowed signer information carefully.
  4. Submit only after all required fields are complete.
  5. Verify the resulting signer status and, when applicable, the next routing/completion step.

Each current signer-input field behaves

After required signing is complete, QCDS finalizes the evidence-bearing artifact. The normal Completed PDF places the signed source pages first, adds attachment presentation pages when used, and appends the Audit Trail. When signer attachments exist, the downloadable Completed Package can also include the protected original attachment files. Completion recovery/regeneration uses stored evidence; signers do not re-sign merely because PDF finalization or delivery needs to be retried.

For Complete Text, Date, Checkbox, and Dropdown Fields as a Signer, 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.

Required/optional completion expectations

After required signing is complete, QCDS finalizes the evidence-bearing artifact. The normal Completed PDF places the signed source pages first, adds attachment presentation pages when used, and appends the Audit Trail. When signer attachments exist, the downloadable Completed Package can also include the protected original attachment files. Completion recovery/regeneration uses stored evidence; signers do not re-sign merely because PDF finalization or delivery needs to be retried.

For Complete Text, Date, Checkbox, and Dropdown Fields as a Signer, 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.

And how the final values are frozen into the completed Request evidence

After required signing is complete, QCDS finalizes the evidence-bearing artifact. The normal Completed PDF places the signed source pages first, adds attachment presentation pages when used, and appends the Audit Trail. When signer attachments exist, the downloadable Completed Package can also include the protected original attachment files. Completion recovery/regeneration uses stored evidence; signers do not re-sign merely because PDF finalization or delivery needs to be retried.

How This Fits into the QCDS Workflow

Ordinary QCDS signing is a secure-link workflow and does not require the signer to have a Joomla account. Identity Verification is an additional assurance layer for selected transactions; it does not replace the core signing system.

Signer usability and evidence quality are linked. Clear field placement, private secure-link handling, and explicit Identity Verification requirements make it easier for the signer to complete the intended act without ambiguous workarounds.

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.
  • 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.
  • 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.
  • Asking signers to sign again when only final PDF generation or completion delivery failed.

Troubleshooting

  • If due work is late, confirm the canonical task is enabled and being triggered; a correctly defined task on a quiet Joomla site can still remain overdue without a reliable wake-up mechanism.
  • 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.