This guide provides technical instructions for the spatial mapping and configuration of cryptographic fields (Signatures, Initials, and Data Inputs) within a document asset.
Prerequisites
- Successful ingestion of document assets into an active envelope.
- Assigned recipients within the envelope routing workflow.
Strategic Overview
Field placement is the process of defining the exact spatial coordinates where recipients will interact with the document. Within the IUSign ecosystem, fields are not merely visual elements; they are cryptographic anchors. When a recipient executes a signature field, the platform binds their digital identity to the document's SHA-256 hash at that specific moment. Precise field mapping is essential for ensuring legal defensibility and a frictionless recipient experience.
Implementation Sequence
1. Activating the Field Editor
Upon asset ingestion and recipient assignment, the Field Editor interface is initialized. This high-performance workspace provides a full-fidelity preview of the document assets.
2. Recipient Selection and Context Switching
Before placing fields, select the target Recipient from the editor's toolbar. Each field is cryptographically linked to a specific identity. Selecting a recipient updates the field palette to reflect that user's specific context (e.g., their specific signature color or designated initial style).
3. Spatial Mapping (Drag & Drop)
Drag the required field types from the toolbar and place them onto the document asset:
| Field Type | Functional Description | Use Case |
|---|---|---|
| Signature | Full cryptographic execution point. | Final approval and non-repudiation. |
| Initials | Low-density approval point. | Acknowledgement of specific clauses. |
| Date Signed | Automated timestamp field. | Recording the exact execution time (UTC). |
| Text Input | Dynamic data capture field. | Collecting names, titles, or addresses. |
| Checkbox | Binary selection point. | Consenting to terms or specific options. |
4. Field Property Configuration
Selecting a placed field opens the Properties Panel, allowing for granular control over the field's behavior:
- Mandatory Status: Mark the field as required to prevent the recipient from completing the document without interaction.
- Validation Rules: For text inputs, define regex patterns (e.g., Email, Date, Numeric) to ensure data integrity at the source.
- Conditional Logic (Enterprise): Configure fields to appear or disappear based on the state of other fields (e.g., "Show Textbox ONLY if Checkbox is Checked").
Efficiency Pro-Tips: Advanced Field Management
- Keyboard Shortcuts: Utilize standard shortcuts (Ctrl+C / Ctrl+V) to rapidly replicate fields across multiple pages or documents.
- Auto-Alignment: Use the editor's snap-to-grid and alignment tools to ensure professional document aesthetics.
- Bulk Assignment: For multi-document packets, utilize the Document Tab Navigation to rapidly switch assets while maintaining your selected recipient context.
- Precision Placement: Use the zoom interface (up to 400%) for surgical placement of fields in small-font legal disclosures.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Fields not appearing | Recipient visibility conflict | Verify the recipient is correctly assigned to the active document asset. |
| Validation failure | Regex mismatch | Review the validation pattern in the Properties Panel and ensure it aligns with expected input. |
| Auto-save delay | Network latency | Wait for the "Draft Saved" indicator before navigating away from the editor to prevent data loss. |