This guide provides technical instructions for utilizing status, temporal, and identity filters to manage high-volume document workflows within the IUSign Enterprise platform.
Prerequisites
- Successful authentication into the IUSign portal.
- Existence of at least one document transaction within the accessible scope.
Strategic Overview
Effective document logistics requires the ability to rapidly categorize and isolate transactions based on their current functional state. IUSign provides a multi-layered filtering engine that allows users and administrators to slice the document repository by lifecycle status (e.g., Pending, Completed), temporal windows (e.g., Last 30 days), and participant identities. This capability is essential for identifying bottlenecks, monitoring team-wide performance, and executing bulk administrative actions.
Implementation Sequence
1. Status-Based Navigation (Filter Pills)
The primary filtering mechanism is located at the header of the Documents repository. These "Filter Pills" provide a real-time count and instantaneous access to specific lifecycle states:
| Filter Pill | Operational Definition | Use Case |
|---|---|---|
| All | Comprehensive view of every active transaction. | Standard overview |
| Pending | Transactions currently awaiting signature execution. | Tracking bottlenecks |
| Completed | Transactions where all cryptographic requirements are satisfied. | Finalizing archival |
| Draft | Ingested assets not yet dispatched to recipients. | Resuming work |
| Declined | Transactions formally refused by a recipient. | Corrective action |
| Voided | Manually invalidated transactions. | Compliance review |
2. Temporal Filtering (Growth+)
Users on premium tiers can refine their view using the Date Range filter. This is particularly effective for quarterly audits or monthly performance reviews:
- Preset Windows: Rapidly filter by "Last 7 Days," "This Month," or "Last 30 Days."
- Custom Temporal Range: Specify a precise start and end date to isolate transactions from a specific fiscal period.
3. Identity and Sender Filtering (Team)
Administrators and Team Leads can filter the repository based on the identity of the initiating actor:
- Individual Filtering: View only the envelopes initiated by a specific team member.
- Cross-Departmental View: Filter to see all transactions initiated within a specific department or the entire organization.
Executing Bulk Actions via Filtered Sets
Filtering is often the first step in executing bulk administrative operations. By isolating a specific set (e.g., all "Pending" envelopes from "John Doe"), you can then perform:
- Batch Reminders: Simultaneously trigger notifications for the entire filtered set.
- Batch Archival: Rapidly move an entire category of documents (e.g., old "Declined" drafts) to the Trash repository.
- Bulk Export: Generate a manifest and ZIP archive of all documents satisfying the current filter criteria.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Zero results displayed | Over-restrictive filter logic | Reset all filters to All and re-apply criteria one by one. |
| Inconsistent counts | UI synchronization lag | Execute a browser refresh to re-sync the real-time counters with the backend database. |
| Restricted filters | Tier or Role constraint | Ensure your Subscription Tier supports advanced date and sender-based filtering. |