If you have worked with another enterprise document capture product, DocView Capture will feel familiar. The same ideas are here: batches, document classes, index fields, separation, recognition, validation and export. Some things have different names. This page maps the general terms you know to their DocView Capture equivalents, so you can find your way quickly.
Note: Every product works differently, and the mappings below are approximate. They describe common, general concepts only. Use them as a starting point, not as a feature-by-feature comparison.
Key differences at a glance
- Everything is in the browser. Setup, scanning, indexing and administration all happen in the web app. Only scanning needs a small local program, the DocView Scan Agent.
- One place to set up a batch. A Batch Setup holds the workflow, image cleanup, separation, document classes, fields, finders, validation, event scripts and export for one kind of batch.
- Versions are built in. You edit a draft and Release it. Batches in progress keep the version they started with.
- DocView Workers do the automatic work. One or more DocView Workers pull batches from a shared queue in SQL Server.
- Scripts in familiar languages. Browser and server event scripts are JavaScript. Export scripts can be C#.
Term mapping: Kofax Capture / Tungsten Capture
| Kofax / Tungsten term | DocView Capture term | Where to read more |
|---|---|---|
| Batch class | Batch Setup | Batch Setups overview |
| Publish (a batch class) | Release (a Batch Setup version) | Versions and publishing |
| Document class, form type | Document class | Document classes and classification |
| Index fields | Fields (document fields and batch fields) | Fields and extraction |
| Locators | Finders | Kofax locators and DocView finders |
| Queues / modules in the batch class | Workflow steps | Workflow |
| Scan module | Scan | Scan documents |
| Quality control | Quality check | Quality check |
| Validation | Index / Validate | Index and validate |
| Verification | Verify (double-key verify) | Verify |
| Recognition server | DocView Worker | DocView Workers |
| Export connector (release script) | Export destination | Output and export |
| Release (sending a batch to export) | Release batch, then PDF generation & export | Output and export |
| Batch Manager | Batch Manager | Batch Manager |
| Scan profile | Scan profile | Scan profiles |
| Import connector, hot folders | Import sources (watched folders, mailboxes, REST API) | Import sources |
| Validation and export scripts | Event scripts (JavaScript) and C# export scripts | Events and scripts |
Tip: In DocView Capture, the word Release is used in two places. Operators release a batch to send it to the next step. Administrators release a Batch Setup version to make it available to operators.
Kofax locators and DocView finders
Kofax Transformation reads values with locators. DocView uses finders. This table shows which finder replaces each locator.
| Kofax Transformation locator | DocView Capture |
|---|---|
| Advanced Zone Locator | Advanced zones (form) finder: zones with their own recognition (text with drop-out and character sets, tick boxes, signatures, barcodes) and page registration. See Advanced zones (form). |
| Zone Locator | Fixed zone finder |
| Barcode Locator | Barcode finder with a search area |
| Format Locator | Pattern (regular expression) or Label and value finder. Use the search area for its regions, and Search near what another finder found to search relative to a keyword. |
| Database Locator, Vendor Locator, Address Locator | Database lookup (fuzzy) finder. Every column of the matched row is an output. |
| Script Locator | Script finder, with several outputs |
| Table Locator, line items | Table / line items finder |
| Relation Locator | Search near what another finder found |
| Locator evaluation (several locators, best result) | Fallbacks in order (If nothing is found, use the result of), and Combine other finders |
| Classification Locator | Document type (classification) finder |
| Check boxes (OMR in the Advanced Zone Locator) | Tick boxes (OMR) finder or field method, or a tick-box zone of an Advanced zones finder. See Forms, tick boxes and signatures. |
| Trainable Group Locator, Invoice and Order Group Locators | No learnt locator. Build label-and-value, pattern and lookup finders, for example with New finder from selection on a sample, and check them on all your samples in the Samples & testing panel. |
| Check / MICR Locator | Not available, because there is no permissively licensed MICR reader. Use a cloud OCR engine or a barcode. |
| Text Content Locator | Not available. Use a Script finder or the Cloud key-value (Azure) finder. |
An import from Kofax Capture turns the Advanced Zone Locator and barcode locators into finders for you, and script locators into Script finders that keep the Kofax code as a comment to port. Its report lists every locator of the project with the finder that replaces it: converted, partly converted (the finder to finish) or not converted (with the alternative).
Term mapping: IBM Datacap
| Datacap term | DocView Capture term |
|---|---|
| Application | Batch Setup |
| Workflow, jobs and tasks | Workflow steps of a Batch Setup |
| Task profile | Workflow step, and the worker profile that runs it |
| Document type, page type | Document class (pages belong to documents) |
| Fields | Fields |
| Rules and actions | Finders, formatters, validators, rules and event scripts |
| Verify task | Index / Validate, Correction and Verify |
| Rulerunner / background tasks | DocView Worker |
| Export | PDF generation & export, with export destinations |
Term mapping: Ephesoft
| Ephesoft term | DocView Capture term |
|---|---|
| Batch class | Batch Setup |
| Document type | Document class |
| Index fields | Fields |
| Review (classification) | Classification |
| Validation | Index / Validate |
| Batch instance management | Batch Manager |
| Export plugins | Export destinations |
| Upload batch | Import |
Term mapping: ABBYY FlexiCapture
| FlexiCapture term | DocView Capture term |
|---|---|
| Project | A set of Batch Setups |
| Batch type | Batch Setup |
| Document definition | Document class, with its fields and finders |
| Data verification | Correction (one field at a time across the batch) |
| Verification | Index / Validate |
| Processing station | DocView Worker |
| Workflow stages | Workflow steps |
| Export | Export destinations |
DocView Capture terms you may not know
| Term | What it means |
|---|---|
| Classification | A manual step where operators confirm the class of documents the classifier was unsure about, and check how pages were split, before extraction. |
| Correction | A fast "key what you see" step: one field at a time across the whole batch, with a clip of the page where the value was found. |
| Finder | A way of locating a value: a zone, a label and value, a pattern, a barcode, a table, a fuzzy database lookup, or a script. Fields take their value from a finder. |
| Screen designer | Designs the form operators see in each step, per document class. |
| Four-eyes rule | A workflow step can require someone other than whoever worked on the batch in another step. |
| Worker profile | Says which modules a DocView Worker runs, in which order, and for which Batch Setups. |
For more definitions, see the Glossary.
Moving your setup across
From Kofax Capture: import the batch class export (.cab, including the Kofax Transformation project) directly. DocView creates draft Batch Setups with document types, fields, finders, zones, tick boxes, checks, validation screens, the workflow and dictionaries, and shows a full review first. See Import a setup from Kofax Capture, Kodak Info Input and other products.
From Kodak Info Input: import the jobs export (.zip) directly. Each job becomes a draft Batch Setup with its document types, fields, zones, tick boxes, barcodes, lookups, separation, workflow and exports; scripts are kept to port. See How Kodak Info Input maps to DocView.
From other products (importers for ABBYY FlexiCapture and DocuWare are planned), the quickest route is usually:
- Start from a template with New Batch Setup. See Batch Setup templates.
- Add your document classes and fields.
- On the Finders tab, drag samples onto the Samples & testing panel, then set up finders and try them with Run test.
- Recreate your validation rules on the Validation tab.
- Set up export on the Output & export tab.
- Try it on the Test tab, then Release it.
See Testing a Batch Setup. If you would like help planning a migration, contact support.