How Time Zone, Reminder Interval, and Default Expiration Affect Requests

Explain how workspace timing defaults seed new Requests, how local time is interpreted, and which values can be overridden for an individual transaction without rewriting the saved defaults.

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

  • Open QCDS from the published frontend Workspace Dashboard menu item and confirm you are signed in as the intended Joomla user.
  • Remember that Contacts and sender settings are workspace-scoped; changing one sender’s workspace should not be treated as a site-global edit.
  • For language-sensitive work, distinguish the Contact Preferred Language from the sender/workspace and administrator fallback languages.

Step-by-Step Workflow

  1. Open the relevant QCDS frontend area from the sender workspace.
  2. Review the existing saved value or Contact before editing it.
  3. Make the intended workspace-scoped change and save it.
  4. Start or open a safe test workflow that uses the updated value.
  5. Confirm the change affects future/use-time behavior without rewriting older sent Requests.

How workspace timing defaults seed new Requests

Manual reminders are sender-triggered for eligible incomplete participants. Automatic reminders use the sender’s reminder interval plus the Automatic Reminders Scheduled Task. Both should target only active incomplete signers; neither should recreate the Request or invalidate a successful invitation link.

For How Time Zone, Reminder Interval, and Default Expiration Affect Requests, 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.

Local time is interpreted

Manual reminders are sender-triggered for eligible incomplete participants. Automatic reminders use the sender’s reminder interval plus the Automatic Reminders Scheduled Task. Both should target only active incomplete signers; neither should recreate the Request or invalidate a successful invitation link.

For How Time Zone, Reminder Interval, and Default Expiration Affect Requests, 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 which values can be overridden for an individual transaction without

Manual reminders are sender-triggered for eligible incomplete participants. Automatic reminders use the sender’s reminder interval plus the Automatic Reminders Scheduled Task. Both should target only active incomplete signers; neither should recreate the Request or invalidate a successful invitation link.

How This Fits into the QCDS Workflow

The sender workspace is deliberately private. Contacts, Templates, Requests, Email Template overrides, and sender defaults belong to that workspace so one Joomla user does not accidentally operate another sender’s transaction history.

The workspace model also explains why one user’s Contacts or Email Template override should not be used as global data for another sender. Site-global policy belongs in Administrator settings; sender defaults belong in the sender workspace.

Verify the Result

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

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