Understand QCDS Signer Field Colors and Navigation

Current incomplete/focused/complete visual states, moving through assigned fields, page navigation, and how completion state helps signers find what remains.

This guide applies to All plans; external signer 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

  • Treat the signer link as personal transaction access. Do not publish, forward, or paste it into public support posts.
  • If Level 2 Identity Verification is required, confirm the applicable Didit or Shufti provider profile is configured and tests successfully before sending.
  • Test the signer experience in a normal browser/mobile context, not only while logged into Joomla as an administrator.

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.

Incomplete/focused/complete visual states

The signer UI uses simple state colors: red means required/interactive work still needs attention, blue marks the currently selected/focused field, and green indicates the signer field is complete/ready. These colors are guidance, not the only validation mechanism; Submit still checks required values before accepting the signer’s completion.

For Understand QCDS Signer Field Colors and Navigation, 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.

Moving through assigned fields

The signer UI uses simple state colors: red means required/interactive work still needs attention, blue marks the currently selected/focused field, and green indicates the signer field is complete/ready. These colors are guidance, not the only validation mechanism; Submit still checks required values before accepting the signer’s completion.

For Understand QCDS Signer Field Colors and Navigation, 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.

Page navigation

The signer UI uses simple state colors: red means required/interactive work still needs attention, blue marks the currently selected/focused field, and green indicates the signer field is complete/ready. These colors are guidance, not the only validation mechanism; Submit still checks required values before accepting the signer’s completion.

And how completion state helps signers find what remains

The signer UI uses simple state colors: red means required/interactive work still needs attention, blue marks the currently selected/focused field, and green indicates the signer field is complete/ready. These colors are guidance, not the only validation mechanism; Submit still checks required values before accepting the signer’s completion.

How This Fits into the QCDS Workflow

Ordinary QCDS signing is a secure-link workflow and does not require the signer to have a Joomla account. Identity Verification is an additional assurance layer for selected transactions; it does not replace the core signing system.

Signer usability and evidence quality are linked. Clear field placement, private secure-link handling, and explicit Identity Verification requirements make it easier for the signer to complete the intended act without ambiguous workarounds.

Verify the Result

  • The Template validates and a new test Request renders the expected field/content behavior without changing older Requests.
  • A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

  • Publishing before running Validate and resolving actual configuration problems.
  • Assuming a later Template edit will update a Request that was already sent.

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.

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.