This guide provides technical instructions for initializing a digital transaction (envelope) and orchestrating the ingestion of assets within the IUSign Enterprise platform.
Prerequisites
- Successful authentication into the IUSign portal.
- Administrative or User-level permissions.
- Source documents in supported ISO-standard PDF or Microsoft Office formats.
Strategic Overview
The Envelope is the primary unit of transaction within the IUSign ecosystem. It serves as a secure container that cryptographically links document assets, recipient identities, signing requirements, and an immutable audit trail. Initializing an envelope is a multi-step orchestration process that involves defining the transactional scope, sequencing recipients, and configuring the cryptographic parameters that will govern the document's lifecycle.
Implementation Sequence
1. Initializing the Transaction Gateway
Navigate to the Documents repository and select the New Envelope action. This initializes the envelope orchestration wizard, a high-performance interface designed for rapid transactional setup.
2. Digital Asset Ingestion
Select the target assets for the transaction. The platform supports:
- Singular Asset Ingestion: Drag and drop a single document for immediate processing.
- Multi-Asset Packaging (Growth+): Ingest multiple documents simultaneously. IUSign will consolidate these into a single signing packet, ensuring recipients are guided through each asset in a logical sequence.
3. Subject Line and Transactional Context
Define the Subject Line for the envelope. This metadata is essential for both recipient communication and internal repository indexing:
- Clarity: Use descriptive subjects (e.g., "Mutual NDA: IUSign & [Company Name]") to ensure high open rates and rapid retrieval.
- Internal Context: You may add private internal notes to the envelope for administrative tracking; these notes are not visible to recipients.
Technical Specifications: Ingestion Engine
| Parameter | Specification | Enterprise Note |
|---|---|---|
| Max Combined Size | 100 MB (Standard) | Customizable up to 500 MB for Enterprise tenants. |
| Normalization | Automated PDF/A Conversion | Ensures long-term archival stability and PAdES compliance. |
| Malware Analysis | Heuristic & Signature-based | Blocks execution of malicious payloads in Office/PDF files. |
Efficiency Pro-Tips for Enterprise Scale
- Template Utilization: For high-volume repeatable workflows, utilize Templates instead of manual creation to reduce setup time by up to 90%.
- Sequential vs. Parallel Routing: Decide early if you need recipients to sign in a specific order (1 → 2 → 3) or if all parties can sign concurrently. Sequential routing is recommended for multi-departmental approvals.
- Draft Persistence: IUSign automatically saves your progress. You can initialize an envelope, ingest assets, and resume the configuration later via the Drafts filter.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Asset conversion error | Font embedding/Corruption | Ensure all fonts are embedded in the source PDF or re-export the file from its native editor. |
| Payload too large | Tier-based size limit | Utilize PDF optimization or re-distribute assets across multiple envelopes. |
| Initialization timeout | Network instability | Verify connection and re-initialize from the Drafts folder if necessary. |