IBM Datacap Taskmaster Capture Product Fundamentals Technical Mastery Test v1

Actions only return TRUE or FALSE. ✘ It is decoupled from Taskmaster so it can be used with other applications. ✘ It is the only capture product with claims of being rule driven. ✘ It is open source. ✔

Taskmaster Server pushes work to machines dedicated to a specific task. ✘ Taskmaster clients ask Taskmaster server if there is any work to be done. ✘ Only one Taskmaster client may perform a given Task. ✘ Batch routing depends on the Taskmaster server configuration. ✔

Forms filled out in both handprint and machine print, such as tax forms. ✘ Highly structured documents, such as medical claims. ✘ Indexing of photographs. ✘ Highly variable documents, such as invoices. ✔

Apache for Linux servers and IIS for Windows servers. ✘ Any web server that will run in Windows or UNIX/Linux. ✘ Apache only. ✘ IIS only. ✔

Scan and Verify in a single task. ✘ Reading an image from a disk. ✘ Reading an EDI format and converting to an image. ✘ Any validated scan technique. ✔

Position and OCR. ✘ OCR and Pattern Match. ✘ Pattern Match and Intellocate. ✘ Barcodes and Position. ✔

Ruleset ✘ Function ✘ Application ✘ Task Profile ✔

The databases can be run on the same machine as Taskmaster Server. ✘ To add new clients, the Taskmaster Server Administration Resource (TSAR) may be run from the client machine. ✘ The most critical consideration for a background machine is dual-homed networking. ✘ You should add a Taskmaster Server for roughly every 40,000 pages per day. ✔

The data is discarded. ✘ The operator is informed. ✘ Processing jumps to the next Function, if any exist. ✘ The Task immediately completes. ✔

Manual page identification. ✘ The technology/interface used for writing custom actions. ✘ The core technology that allows Taskmaster to run Rules. ✘ A series of technologies that, together, help to recognize new document formats at runtime. ✔