Use Check to Validate a QCDS Request Before Send Now

Run request validation, resolve missing assignments/document/participant issues, and use Check as the final pre-send review rather than discovering preventable problems after submission.

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

  • Use a published Template and confirm the required Contacts are present before opening the Request workflow.
  • Finish unsent work in the current browser session. The streamlined flow does not present ordinary new Requests as persistent server-side drafts before Send Now.
  • Confirm Joomla mail and the current request allowance before production sending so a delivery or entitlement issue is found early.

Step-by-Step Workflow

  1. Finish Request Details and Prepare & Send configuration.
  2. Click Check.
  3. Correct each red/unassigned field, invalid required property, broken Signed Date link, missing signer, or other blocking problem QCDS identifies.
  4. Review routing, expiration, subject/message, signer addresses, and Identity Verification requirements.
  5. Run Check again until the Request is ready, then use Send Now.

Run request validation

Check is the preflight step for the Request. It catches unassigned/invalid interactive fields, broken required configuration, missing signer information, and related send blockers. Send Now then performs the current plan/allowance authorization before the transaction becomes sent and attempts the initial invitations immediately. Automatic Reminders is for later reminder work; it is not the initial-send mechanism.

For Use Check to Validate a QCDS Request Before Send Now, 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.

Resolve missing assignments/document/participant issues

Check is the preflight step for the Request. It catches unassigned/invalid interactive fields, broken required configuration, missing signer information, and related send blockers. Send Now then performs the current plan/allowance authorization before the transaction becomes sent and attempts the initial invitations immediately. Automatic Reminders is for later reminder work; it is not the initial-send mechanism.

For Use Check to Validate a QCDS Request Before Send Now, 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 use Check as the final pre-send review rather than discovering

Check is the preflight step for the Request. It catches unassigned/invalid interactive fields, broken required configuration, missing signer information, and related send blockers. Send Now then performs the current plan/allowance authorization before the transaction becomes sent and attempts the initial invitations immediately. Automatic Reminders is for later reminder work; it is not the initial-send mechanism.

How This Fits into the QCDS Workflow

The Request editor is the boundary between reusable preparation and an immutable transaction. QCDS lets you make Request-specific choices before sending, then freezes the final participants, fields, routing, message source, and other transaction context when Send Now succeeds.

Because Send Now is the transaction boundary, review the entire transaction immediately before sending: people, assignments, routing, expiration, invitation source, verification requirement, and request allowance.

Verify the Result

  • Request Details shows the expected lifecycle, participant, Timeline, and delivery state after the action.
  • 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

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