Define signature, initials, date, text, checkbox, and other signable fields.

Overview

Define signature, initials, date, text, checkbox, and other signable fields. FeraRender declares signing intent and returns manifest metadata; the signing system should resolve final coordinates after conversion to the signing PDF.

Key points

• Every field needs a unique anchor.
• recipient links the field to a recipient key.
• fieldType controls the signing control.
• required, label, placeholder, defaultValue, options, and validation control behavior.
• geometry and offsets guide placement from the resolved anchor.
• fieldOrder controls navigation.

Recommended procedure

1. Place stable anchors in the rendered document.
2. Embed and validate a versioned signature manifest.
3. Resolve recipient keys from trusted application data.
4. Generate the document, convert it, resolve anchors, and review the draft envelope.

Troubleshooting

A required field is not placed

Confirm the anchor survives conversion and the manifest refers to the same anchor and recipient key.

A recipient cannot be resolved

Supply trusted recipient data or valid name and email paths before creating or sending the envelope.

The field is offset incorrectly

Review anchor point, dimensions, offsets, and final PDF text extraction behavior.

Related documentation

• Signature Recipient Definitions
• FeraRender Signature Manifest
• Create FeraSign-Ready Documents

Documentation source: feradelinc/feradel.render.api, reviewed against repository revision b2c3a710. Verify behavior against the deployed release before publishing exact routes, limits, or version requirements.