Use Lock Placement and Hidden-by-Default Field Properties

Advanced field properties that protect field geometry or initial visibility, when they are appropriate, and how they interact with the signer experience.

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

  • Start with a clean PDF. QCDS current Template intake is PDF-only; convert DOC/DOCX or other source formats to PDF before upload.
  • Choose a stable document layout before placing fields because field coordinates are tied to the PDF page geometry.
  • Use a simple test PDF first when diagnosing rendering or placement so document complexity is not confused with a builder problem.

Step-by-Step Workflow

  1. Open the Template draft in QCDS and wait until the PDF is visibly rendered.
  2. Make the field/layout/content change described in this guide.
  3. Review assignment, Required state, links/options, and page placement.
  4. Run Validate and correct every real problem before publishing.
  5. Save/publish, then start a test Request to verify the signer and Completed PDF behavior.

Advanced field properties that protect field geometry or initial visibility

The current visual builder uses the rendered PDF as the coordinate authority. You can move between pages, click or drag fields from the palette, select/move/resize them, use Undo/Redo, Copy/Paste, Delete, Fit Width, zoom controls, bulk assignment, and right-click Field options. Do not save placement against a blank/failed PDF preview: resolve protected-delivery/rendering errors first so coordinates are based on the actual page.

For Use Lock Placement and Hidden-by-Default Field Properties, 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.

When they are appropriate

The current visual builder uses the rendered PDF as the coordinate authority. You can move between pages, click or drag fields from the palette, select/move/resize them, use Undo/Redo, Copy/Paste, Delete, Fit Width, zoom controls, bulk assignment, and right-click Field options. Do not save placement against a blank/failed PDF preview: resolve protected-delivery/rendering errors first so coordinates are based on the actual page.

For Use Lock Placement and Hidden-by-Default Field Properties, 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 how they interact with the signer experience

The current visual builder uses the rendered PDF as the coordinate authority. You can move between pages, click or drag fields from the palette, select/move/resize them, use Undo/Redo, Copy/Paste, Delete, Fit Width, zoom controls, bulk assignment, and right-click Field options. Do not save placement against a blank/failed PDF preview: resolve protected-delivery/rendering errors first so coordinates are based on the actual page.

How This Fits into the QCDS Workflow

A Template is reusable preparation, not a live signature transaction. QCDS versions published Template work so future Requests can use a new layout while older sent Requests remain based on their frozen snapshot.

Use Template versioning as the safety boundary: improve future preparation without altering the immutable snapshot already attached to an older Request.

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 the result differs from this guide, capture the current QCDS version, Status message, owning object ID/reference, and exact reproducible action before opening a support request.

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.