Edit a Published QCDS Template Without Changing Existing Requests

Editing a published QCDS Template creates or reopens a separate draft version. The currently published version remains active for new Requests until you validate and publish the successor draft, and Requests that already exist keep their original frozen Template snapshot.

What Edit Does to a Published Template

From Templates, choose Edit on a published Template. QCDS does not modify the published version in place. If an active draft already exists, QCDS reopens that draft. Otherwise, it creates the next Template version as a draft based on the current published version.

The new draft records its published parent. The Template itself remains in published state while you work, so Use continues to resolve the current published version until the successor draft is explicitly published.

Edit the Successor Draft

  1. Open Templates and choose Edit for the published Template.
  2. Confirm the builder header shows the draft version and, when applicable, Draft based on Published v#.
  3. Make the required document, field, role, property, or logic changes.
  4. Use Save as you work. Each save appends a new draft revision rather than rewriting the prior published version.
  5. Run Validate and correct blocking errors.
  6. Choose Publish Template only when the successor draft is ready for future Requests.

What Happens When You Publish the New Version

Publication requires the active draft to pass current server-side validation. QCDS then marks that draft as the new published Template version and marks the formerly published version as superseded. The Template's published pointer moves to the new version.

That change affects future Template use. It does not reach backward into Requests that were already created.

Why Existing Requests Do Not Change

When QCDS creates a Request from a Template, it copies the selected Template version into transaction-specific Request data and records the source Template/version. Participant, field-value, signature, token, evidence, and audit collections then belong to that Request.

Because the Request is independent after creation, later Template edits or publication cannot silently move fields, replace the document, change signer evidence, or rewrite a completed transaction.

Verify the Change Safely

  • Before publishing, use the builder preview and validation results to confirm the draft.
  • After publishing, create a new test Request and confirm it uses the new Template version.
  • Open an older Request and confirm its document, participants, Timeline, and completed evidence remain unchanged.

If You Need to Correct an Existing Request

Do not edit the reusable Template expecting an already-created Request to change. Handle the issue from the Request workflow itself, or create a new Request when the transaction truly must be replaced.

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.