In enterprise content management (ECM) and document process systems like Hyland’s Perceptive Content (formerly ImageNow), “Hold Image” and “Viewer” workflows refer to the specific steps and user interfaces utilized to temporarily freeze document processing. This function ensures that transaction routing stops while a user investigates an exception, awaits missing metadata, or performs a manual review. Core Concepts
The Viewer Window: The central, read-only or interactive interface where a user opens an item, task, or multi-page image packet from a workflow queue. It exposes an Actions Pane to handle the file.
The “Hold” Action: A temporary status flag applied directly to an item. Placing an item on hold stops it from advancing automatically to the next sequential queue, allowing you to close the document safely and return to it later. Step-by-Step Hold Workflow
When an exception occurs during a document review session, a typical user workflow proceeds as follows:
[Open Document in Viewer] ──> [Identify Issue] ──> [Trigger Close / Put on Hold] ──> [Log Reason & Comments] ──> [Item Frozen]
Reviewing the Image: You open a document from your designated queue, displaying it inside the main viewer panel.
Pausing the Session: If you cannot finish processing (e.g., a line item on an invoice is incorrect), you close the workflow item.
Applying the Hold: The system prompts a decision to route, forward, or pause. Select Put on Hold.
Metadata Logging: An On Hold dialog box appears. You are required to input: Follow-up Date: When the item should be re-examined.
Hold Reason: A standardized category code (e.g., Missing Signature, Audit Required).
Comments: Specific context explaining why processing stopped.
Queue Freezing: The system saves your entries, updates the item’s status, and keeps it safely parked in your current queue view until the hold is resolved. Key Capabilities of the Viewer Panel
Beyond simple page manipulation, the viewer panel functions as an interactive command center for your document pipeline.
The Actions Pane: Allows users to apply holds, add digital signatures, update index values, or route the item to a completely different container.
Concurrent Loading: Supports opening multiple item viewer windows simultaneously (frequently up to 9 items) to cross-reference text and visuals across tasks.
Search Integration: Contains a content results pane that maps exact keyword hits to individual pages of a multi-page document.
Version Control: If enabled, the viewer tracks previous revisions, allowing checked-out items to lock while preserving history.
If you are setting up or managing these queues, would you like to explore how to configure automated alarms for expired holds, or should we look at customizing the user access permissions for the workflow viewer? What is Viewer? – What is Viewer? – Use Workflow
Leave a Reply