Send a QCDS Request in Signing Order

Use Sign in order, establish signer sequence, understand activation of the next signer after completion, and verify order before Send Now.

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 Prepare & Send and assign every field to the correct signer.
  2. Reorder the signer list into the exact sequence that should control activation.
  3. Choose Sign in order.
  4. Click Check and review the order again before Send Now.
  5. After sending, confirm only the first applicable signer is active; QCDS activates later signers as earlier signers complete.

Sign in order

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 Send a QCDS Request in Signing Order, 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.

Establish signer sequence

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 Send a QCDS Request in Signing Order, 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.

Activation of the next signer after completion

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 verify order before Send Now

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

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