Submit Completed QCDS Signer Fields

Submit is the point where signer draft progress becomes a completed participant action. QCDS checks Identity Verification and required fields again, finalizes the signer values, records participant completion, advances routing, and starts completion processing when the routing graph is finished.

Before You Press Submit

• Complete every required assigned field.
• Correct or clear any unfinished invalid Selectable Date entry.
• Wait for active autosaves or attachment uploads to finish.
• If Identity Verification is required, complete it successfully so signing is allowed.

The browser disables Submit while these conditions are not ready and can jump you to the first missing required field.

QCDS Saves Pending Changes First

If the signer screen still has unsaved field changes when you submit, QCDS attempts to save that progress first. The server then resolves the exact participant session and validates the transaction again; the browser’s green field states are helpful guidance, not the only authority.

Server Validation Runs Again

The server refuses submission if required Identity Verification has not allowed signing or if any required assigned field is still incomplete. Automatic Contact fields and linked Signed Date values are synchronized before this final check so the server evaluates the current evidence state rather than only the visible browser controls.

What Successful Submit Records

QCDS marks the signer’s saved field values final, preserves or supplies the relevant signing timestamps, and records the participant completion through the Request routing service. It then:

• makes any eligible signer-confirmed Contact corrections as best-effort future-use updates;
• marks the signer session completed;
• captures signing-completed evidence and timeline/audit events; and
• reconciles invitation delivery for any signer who becomes active next.

The Request’s immutable send-time snapshot is not rewritten by this process.

What Happens to Routing and Finalization

If more required routing work remains, the Request continues and the appropriate next signer or active stage proceeds. If routing is complete, QCDS attempts final completion processing for the Request.

A later invitation-delivery or completed-PDF finalization problem is retryable. It does not undo a participant completion that was already recorded successfully.

What the Signer Sees After Success

The signer screen changes to a Signing Complete message showing the participant and Request. Depending on the Request state, QCDS can also indicate that another delivery step will be retried, that final output was generated, or that finalization still needs retry processing.

Do not sign again merely because final delivery or PDF generation is still finishing. Reopening a completed signer invitation returns a completed state instead of reopening editable fields.

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.