Regenerate a QCDS Completed PDF from Stored Evidence

Regenerate from the immutable Request snapshot and stored signer evidence, preserve prior artifact revisions, avoid new signatures, and understand that regeneration does not automatically resend completion email.

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

  • Confirm all required signers are complete before troubleshooting finalization; a completion failure is not a request to collect signatures again.
  • Preserve any already-valid Completed PDF while attempting recovery or regeneration.
  • Keep protected Completed Packages and attachment originals in authorized storage rather than exposing them through ordinary public URLs.

Step-by-Step Workflow

  1. Open the completed Request and review the current stored artifact before regenerating.
  2. Choose Regenerate Completed PDF only when you need to rebuild the presentation from frozen Request/signing evidence.
  3. Allow QCDS to create a new artifact revision without collecting new signatures.
  4. Verify the regenerated document and Audit Trail.
  5. Use Resend separately if the regenerated document also needs to be emailed; regeneration itself does not automatically resend completion mail.

Regenerate from the immutable Request snapshot and stored signer evidence

Signature and Initials are interactive signing fields. The current signer experience supports typed or drawn completion, and QCDS keeps the rendered result within the intended field rectangle. Signed Date is different: it is a read-only server-generated date linked to one exact Signature or Initials field and fills when that linked field is completed, preserving the relationship between the signing action and its date.

For Regenerate a QCDS Completed PDF from Stored Evidence, 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.

Preserve prior artifact revisions

Signature and Initials are interactive signing fields. The current signer experience supports typed or drawn completion, and QCDS keeps the rendered result within the intended field rectangle. Signed Date is different: it is a read-only server-generated date linked to one exact Signature or Initials field and fills when that linked field is completed, preserving the relationship between the signing action and its date.

For Regenerate a QCDS Completed PDF from Stored Evidence, 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.

Avoid new signatures

Signature and Initials are interactive signing fields. The current signer experience supports typed or drawn completion, and QCDS keeps the rendered result within the intended field rectangle. Signed Date is different: it is a read-only server-generated date linked to one exact Signature or Initials field and fills when that linked field is completed, preserving the relationship between the signing action and its date.

And understand that regeneration does not automatically resend completion

Signature and Initials are interactive signing fields. The current signer experience supports typed or drawn completion, and QCDS keeps the rendered result within the intended field rectangle. Signed Date is different: it is a read-only server-generated date linked to one exact Signature or Initials field and fills when that linked field is completed, preserving the relationship between the signing action and its date.

How This Fits into the QCDS Workflow

QCDS treats completion artifacts as evidence-bearing outputs. Recovery and regeneration rebuild presentation from stored transaction/signing evidence and preserve prior valid artifacts rather than rewriting history.

A completed artifact is not just a visual PDF. It is the presentation of a frozen transaction plus stored evidence; recovery should reconstruct from that evidence instead of creating a new signing event.

Verify the Result

  • A real test message leaves Joomla and arrives at the intended mailbox with the correct sender identity and format.
  • 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

  • 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 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.
  • 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 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.