QCDS Production Go-Live Checklist

End-to-end launch checklist covering version, HTTPS, Joomla mail, four Scheduled Tasks, QCTNH/quiet-site wakeups, languages, frontend appearance, Custom CSS if used, Identity Verification, group limits, sender workspace, email templates, representative field/routing tests, attachments, completion, and support info.

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

Capture the exact QCDS version, current Status message, Request identity, and the action that failed before changing several unrelated settings.
Do not include API keys, webhook signing secrets, old license keys, secure signer links, or private identity evidence in public diagnostics.
When possible, reproduce the problem with a small test PDF/test Contact so production data is not used as the diagnostic tool.

Step-by-Step Workflow

Open Components > QC Digital Signature and the administrator tab that owns this setting or status.
Record the current value/status before changing it.
Apply the intended change using the current QCDS control.
Save or run the provided action and read the resulting message.
Verify the Status page and one representative frontend workflow before considering the change complete.

End-to-end launch checklist covering version, HTTPS, Joomla mail, four

QCDS relies on Joomla Scheduled Tasks for unattended work. The customer-facing canonical set is Automatic Reminders, Request Timing and Deadlines, Final PDF and Completion Delivery, and Entitlement Revalidation. Their normal cadences are 60 minutes, 5 minutes, 5 minutes, and 60 minutes respectively. Internal worker methods may exist in the package, but they are not extra tasks administrators should manually create. On a quiet site, a healthy task definition still needs Joomla to be triggered; use QC Task Nudge & Health or another reliable Joomla-native wake-up strategy when normal traffic is too sparse.

For QCDS Production Go-Live Checklist, 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.

The current QCDS workflow preserves the intended result

To verify before relying on this behavior in production

How This Fits into the QCDS Workflow

Operational troubleshooting works best when the failure domain is isolated: installation/access, Scheduled Tasks, entitlement, PDF preparation, sending/mail, signer access/Identity Verification, or completion. Fix the narrow layer rather than resetting unrelated data.

When escalation is necessary, provide enough non-secret detail to reproduce the failure without sharing secure signer URLs, provider credentials, private identity media, or other protected evidence.

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.
Provider Test Connection succeeds and a representative Level 2 test follows the expected provider flow.
Joomla Scheduled Tasks shows the relevant canonical QCDS task enabled with a sensible next execution time.
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.
Treating provider-backed Identity Verification as required for every ordinary secure-link signing workflow.
Posting provider credentials, webhook secrets, or identity evidence in public diagnostics.
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 Level 2 verification fails, use the provider Test Connection and inspect provider/profile/callback configuration; ordinary Level 1 signing and historical evidence should not be reset.
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.

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.