What Send Now Checks Before QCDS Sends Invitations

Synchronous current entitlement and Basic/Pro allowance authorization, idempotent request authorization, field/routing validation, snapshot freezing, and why the same authorized retry should not count twice.

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. Open the QCDS screen or record that owns the topic so you are reading the current state rather than an old screenshot or memory.
  2. Compare the visible state with the current 2.0.7 rules described in this guide.
  3. Identify whether the value belongs to global installation settings, one sender workspace, a reusable Template, or one immutable/sent Request.
  4. Make changes only at the layer that owns the behavior.
  5. Verify the result with a safe test and preserve historical Requests/evidence.

Synchronous current entitlement and Basic/Pro allowance authorization

QCDS currently exposes two ordinary routing modes. Everyone at once lets all active signers work independently in parallel. Sign in order activates signers sequentially, so later signers are not treated as active until the earlier required signer completes. Changing routing before Send Now changes invitation timing; after the Request is sent, the frozen routing belongs to that transaction history.

For What Send Now Checks Before QCDS Sends Invitations, 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.

Idempotent request authorization

QCDS currently exposes two ordinary routing modes. Everyone at once lets all active signers work independently in parallel. Sign in order activates signers sequentially, so later signers are not treated as active until the earlier required signer completes. Changing routing before Send Now changes invitation timing; after the Request is sent, the frozen routing belongs to that transaction history.

For What Send Now Checks Before QCDS Sends Invitations, 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.

Field/routing validation

QCDS currently exposes two ordinary routing modes. Everyone at once lets all active signers work independently in parallel. Sign in order activates signers sequentially, so later signers are not treated as active until the earlier required signer completes. Changing routing before Send Now changes invitation timing; after the Request is sent, the frozen routing belongs to that transaction history.

Snapshot freezing

QCDS currently exposes two ordinary routing modes. Everyone at once lets all active signers work independently in parallel. Sign in order activates signers sequentially, so later signers are not treated as active until the earlier required signer completes. Changing routing before Send Now changes invitation timing; after the Request is sent, the frozen routing belongs to that transaction history.

And why the same authorized retry should not count twice

QCDS currently exposes two ordinary routing modes. Everyone at once lets all active signers work independently in parallel. Sign in order activates signers sequentially, so later signers are not treated as active until the earlier required signer completes. Changing routing before Send Now changes invitation timing; after the Request is sent, the frozen routing belongs to that transaction history.

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

  • 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.
  • Status shows the expected Base and Effective tier and no unresolved entitlement-task integrity warning.
  • A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

  • Following old instructions that require entering a current license key instead of using Authorized Domains.
  • Starting the one-time Max Preview merely to inspect a feature before you are ready to evaluate it.
  • 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.

Troubleshooting

  • If a paid feature unexpectedly locks, inspect Authorized Domain resolution, Base/Effective tier, and the hourly Entitlement Revalidation task before changing saved configuration.
  • 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.