How QCDS Preserves Sent and Completed Request History After Later Edits

Historical stability across later Template, Contact, Email Template, language, provider, or workspace-setting changes; explain immutable snapshots and why a completed transaction should not be 'updated' in place.

This guide applies to All plans; sender and administrator 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 or completion-recovery Request.
  2. Confirm signer completion and the current artifact/delivery state.
  3. Use the supported recovery, regeneration, download, or evidence-review action.
  4. Verify the resulting artifact and Audit Trail.
  5. Preserve prior valid artifacts and protected attachment originals according to records policy.

Historical stability across later Template, Contact, Email Template,

Participant language is resolved at use time in this order: Contact Preferred Language, sender/workspace Default frontend language, administrator Default frontend language, then English (en-GB). QCDS can translate creator-authored participant communication when needed, while protecting tokens, URLs, and HTML. If safe translation is unavailable, it falls back to the complete frozen source message rather than sending a partially translated mixture.

For How QCDS Preserves Sent and Completed Request History After Later Edits, 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.

Immutable snapshots and why a completed transaction should not be 'updated'

Participant language is resolved at use time in this order: Contact Preferred Language, sender/workspace Default frontend language, administrator Default frontend language, then English (en-GB). QCDS can translate creator-authored participant communication when needed, while protecting tokens, URLs, and HTML. If safe translation is unavailable, it falls back to the complete frozen source message rather than sending a partially translated mixture.

For How QCDS Preserves Sent and Completed Request History After Later Edits, 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

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.
  • 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.
  • Troubleshooting QCDS message content before confirming Joomla itself can send mail.

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