Use Lock Placement and Hidden-by-Default Field Properties

QCDS 2.0.7 actively enforces Lock placement in the visual builder. The builder also stores a Hidden by default property, but the current signer payload does not carry or enforce that flag, so it should not be relied on for signer-side visibility in this version.

Use Lock Placement to Protect Finished Geometry

After a field is positioned and sized correctly, enable Lock placement from the field properties. In the current 2.0.7 builder, a locked field does not receive the normal resize handle and direct pointer/keyboard movement is blocked.

Lock placement is useful when:

  • signature/date fields are aligned precisely with printed lines;
  • you have a dense multi-page form and want to reduce accidental movement;
  • the field geometry has been reviewed and only assignment/content properties still need attention.

Locking does not turn the field into immutable historical evidence. It is a draft-builder editing control; you can unlock the field again while the Template version remains editable.

What Hidden by Default Stores

The builder's detailed field-properties panel includes Hidden by default, and QCDS persists that boolean in Template/Request item data. In the builder preview, hidden items are visually de-emphasized so the property is visible to the sender preparing the layout.

Current 2.0.7 Limitation: Do Not Rely on Hidden by Default for Signer Visibility

In the active 2.0.7 signing path, the signer field payload is assembled from the Request snapshot and does not include or evaluate the stored field-level hidden flag. The active signer application therefore has no field-level Hidden-by-default value to enforce.

For that reason, treat the property as saved builder metadata in 2.0.7—not as a reliable way to keep a field invisible to the signer. Do not place sensitive information in a signer-assigned field on the assumption that checking Hidden by default will protect it.

Use Explicit Rules for Conditional Behavior Only After Testing

The builder supports rule actions such as show and hide, but visibility/rule behavior should be tested end-to-end with the exact field types and signer path you intend to use. A saved builder checkbox by itself is not proof that signer-side hiding is active.

Recommended Workflow

  1. Finish field placement and sizing.
  2. Enable Lock placement on fields whose geometry should no longer move accidentally.
  3. If you see Hidden by default, do not depend on it as a security or signer-visibility control in QCDS 2.0.7.
  4. Validate and publish the Template.
  5. Create a controlled test Request and verify the actual signer view before using any visibility-sensitive design in production.

If You Need a Field Not to Appear

Prefer a workflow that does not assign/render the field for that signer, or use a tested supported rule/workflow designed for the required condition. For sensitive content, verify the actual signer experience rather than depending on a builder-only presentation state.

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.