Section 10.2.4 Workflow

The production Workflow is a structured sequence of tasks designed to ingest, organize, and manage incoming sessions of boxes and their content in the WIB™ Review Web Application. A Workflow defines which pipeline modules are enabled when processing boxes for a Collection. WIB™ Review organizes these tasks into Modules that can be defined for a Collection. Each new box and its associated images progress through the Workflow until all images are completed and deemed ready for Export.

The set of modules is fixed and universal — every Workflow is built from the same modules. What varies is how a Workflow is applied: a Workflow can be assigned to many Collections, but a Collection can have only one Workflow. Per-module settings are configured on the Collection once the Workflow is assigned (see Section 10.2.4.9). The Batch Manager is the control center for managing and tracking batches through the Workflow (Section 8).

The following describes each module, then how to create, assign, and manage a Workflow.

Section 10.2.4.1 Batch Manager

The Batch Manager facilitates the grouping of similar tasks or files (a "batch") to be processed together. It is designed to handle high-volume data, reducing manual labor, improving consistency, and enabling, in many cases, automated, unattended operations. It allows users to define, queue, and manage batches, determining when they are released into the production pipeline (e.g., nightly, on demand). It often includes functionality to handle dependencies between jobs.

Key capabilities:

• Automation: Executes tasks automatically, such as converting files to standard formats, resizing images, or performing bulk metadata updates.
• Monitoring & Control: Provides visibility into the status of batches, tracking progress, and identifying failures in real time.

Section 10.2.4.2 Quality Control

Combines automated checks (for technical metadata and file integrity) with manual, visual inspection of images (for subjective quality). The Quality Control Module can be filtered to show ONLY those images that have an AI Quality Tag, or all images in the batch (box). The user can change the navigation view to list the image names or show the thumbnails of the images in the batch. The module can be configured, through Security Profiles, to allow review of ONLY those images with Quality Tags or to require 100% review of all images in the batch. Once all images — or at a minimum, those with errors — are reviewed, they are either remedied or pass a subjective review and are accepted as passable.

Section 10.2.4.3 Rescan

Rescan, in this context, is defined as the process of transforming products that do not fulfill preset specifications for acceptable-quality images. This module is separate from the Quality Control module because it requires rework on a WIB™ Unit or through the Mobile Application. The Rescan Module filters the box image(s) that require a rescan or an insertion to deem the batch complete and free of capture errors.

Section 10.2.4.4 Redaction

Digital-conversion production-workflow redaction is the process of permanently removing or obscuring sensitive information (e.g., PII, confidential or privileged data) from documents during their transformation into their deliverable format. Unlike simple black-box covering, true electronic redaction in a workflow removes the underlying text, images, and metadata, ensuring the information is irretrievable. The Redaction Module allows the user to manually redact PII, confidential, or privileged information in images that could not be automatically redacted. The AI Redaction feature identifies images where the automated redaction did not completely or only partially obfuscate the sensitive information.

Section 10.2.4.5 Index

The Indexing Module is the manual data-entry process of human operators reading, interpreting, and typing information into attributes for a Collection. The attributes that require manual data entry can be identified for Collections and then added to the Workflow and Taxonomy. Indexing always precedes Verification.

Section 10.2.4.6 Verification

Verification is the second step in the manual data-entry and data-extraction process, where human operators verify the values for each attribute in the Collection.

Section 10.2.4.7 Export

The Export phase is the final step in the Workflow, where the edited, processed, or digitized content is rendered and converted into a specific, distributable file format optimized for its intended platform. Export is always enabled.

Section 10.2.4.8 Creating a Workflow

Workflows are managed from Configuration Management. On the Configuration Management page, select the Workflow tile to open the Workflows area.

The Workflows area provides two reference views:

• Overview — explains what a Workflow is and outlines the three steps to put one into production: Create Workflow, Configure Modules, and Assign to Collection.
• Catalog — displays all existing Workflows in a grid, showing each Workflow's Name, Enabled Modules, Date Created, and Actions.

To create a new Workflow, select New Workflow (or + New). WIB™ Review prompts you to Choose Workflow Form View, offering two ways to build the same Workflow — a guided Workflow Wizard or an all-at-once Design View.

Workflow Wizard steps you through each module one at a time.

1. Enter a Name and Description for the Workflow.
2. Step through each module using Next and Back. For each module, set the toggle to ENABLED or DISABLED. The modules appear in order: Quality Control, Rescan, Redaction, Index, Verification, and Export. Export is always enabled.
3. Select Create Workflow to save.

Design View uses the same Name and Description fields, but replaces the step-by-step stepper with a single checklist of all modules. Check or uncheck each module to enable or disable it, and use Select All or Deselect All to set them in bulk. Export remains enabled. Select Create Workflow (or Save Changes when editing) to save.

You can move from the Wizard to the checklist at any time with Switch to Design View.

Section 10.2.4.9 Assigning a Workflow to a Collection

A Workflow does not process boxes on its own — it must be assigned to a Collection to control which steps run during box processing. Per-module settings are configured on the Collection at the time of assignment. A Workflow can be assigned to many Collections, but a Collection can have only one Workflow. A Workflow is assigned when creating a Collection (see Section 9.2.6 New Collection).

Section 10.2.4.10 Managing Workflows

• Edit: Open a Workflow by clicking its name in the Catalog or the My Workflows list, adjust the enabled modules in the Design View checklist, and select Save Changes.
• Clone: Use Clone From (when creating) or Clone (on an existing Workflow) to duplicate an existing Workflow as a starting point.
• Delete: Remove a Workflow using the trash icon in the Actions column of the Catalog, or select Delete on the Workflow page.