You can configure Rulerunner to monitor the job queue and run background tasks like PageID, Profiler, and Export automatically whenever batches are pending.
The manual workflow processing was linear so far. You moved each batch from task to task in the same sequence, VScan > PageID > Profiler, Export. The one exception was when a batch was diverted out of the standard workflow and into the FixUp task to address document integrity problems. You can also do conditional routing, which can route a batch to a specific job if it requires special handling. The example that is used is manual page identification, which works if the automated identification methods fail to recognize a page.
The last new task you to cover is automatic fingerprint generation. Automatic fingerprint generation is useful when you want operators to add new page types to the fingerprint library automatically, instead of defining them by using Datacap Studio. This way the fingerprint and recognition zones are saved and can be used next time that you need to process a page of the same type.
Then, you can configure the TravelDocs application to use Rulerunner for background task processing. You can also update the application to handle unidentified pages by routing the batch to a new web client interface called ProtoId for manual page identification. You add a function to automatically generate fingerprints for the pages.
