This guide provides technical instructions for auditing and reviewing the comprehensive metadata, real-time recipient telemetry, and field data associated with a specific digital transaction (envelope) within the IUSign Enterprise platform.
Prerequisites
- Successful authentication into the IUSign portal.
- Existence of a previously initialized, dispatched, or completed envelope.
- Assigned role with permission to view transactional details.
Strategic Overview
The IUSign Envelope Detail interface provides a high-fidelity view into the lifecycle of a document transaction. It consolidates real-time recipient engagement data, cryptographic field mappings, and an immutable forensic audit trail into a single, centralized dashboard. This interface is the primary tool for administrators and owners to monitor progress, intervene in stalled workflows, and verify the integrity of the signing process.
Implementation Sequence
1. Accessing Detailed Telemetry
Navigate to the Documents repository and select the target envelope from the list or grid view. This action initializes the detailed analysis interface.
2. Transaction Summary and Identity
The header section provides a snapshot of the envelope's core identity parameters:
| Identity Parameter | Technical Description |
|---|---|
| Transactional Subject | The primary human-readable identifier for the envelope. |
| Lifecycle Status | Real-time state (e.g., Pending, Completed, Declined, or Voided). |
| Temporal Data | Exact timestamps of creation, dispatch, and final execution (UTC). |
| Unique Identifier | The 16-character Envelope ID used for forensic cross-referencing. |
3. Recipient Telemetry and Engagement
The Recipients module provides granular visibility into the status of each participant in the workflow:
- Engagement Tracking: Monitor when a recipient has received, opened, and interacted with the document.
- Execution Confirmation: View exact timestamps, IP origins, and user agent strings for each recipient's signature.
- Status Indicators: Rapidly identify which recipients are pending, which have signed, and which have declined the transaction.
Field Data and Mapping Analysis
The Fields tab provides a real-time preview of the cryptographic fields placed across the document assets:
- Spatial Mapping: Review the precise coordinates and page assignments for all signatures, initials, and text fields.
- Signer Association: Verify which field is assigned to which recipient.
- Data Capture: For completed envelopes, view the actual data values input into form fields (e.g., text, checkboxes) by the participants.
Forensic Audit Trail (Compact View)
The detail interface includes a chronological record of the most recent transactional events. This log is derived from the immutable system ledger:
| Event Type | Forensic Detail |
|---|---|
| ENVELOPE_SENT | Successful cryptographic dispatch of the document invitation. |
| RECIPIENT_SIGNED | Successful cryptographic execution of assigned fields by a verified recipient. |
| EMAIL_DELIVERED | Confirmation of successful SMTP delivery to the recipient's mail server. |
| DOCUMENT_VIEWED | Recipient has successfully accessed the secure signing interface. |
[!NOTE] For a comprehensive, multi-page forensic analysis including system-level events, navigate to the Full Audit Trail module.
Operational Lifecycle Actions
Depending on the current state of the envelope, the following administrative actions are available:
- Send Reminder: Manually trigger an automated notification to all pending recipients.
- Void Transaction: Terminate an active envelope to prevent further signatures and invalidate the document.
- Retrieve Assets: Download the finalized, cryptographically signed PDF and its associated Certificate of Completion.
- Modify Envelope: Execute Resend/Revision protocols for declined or incorrect envelopes.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Envelope not found | Archive relocation | Verify if the envelope was moved to the Archive (Trash) repository. |
| Stale telemetry data | UI desynchronization | Execute a manual browser refresh to re-sync with the latest backend state. |
| Restricted actions | Permission constraint | Verify that your User Role allows for administrative intervention on this specific envelope. |