Updating the Recognize Page ruleset

You must update the Recognize ruleset to handle pages that are identified manually.

About this task

Currently, the ruleset works for pages that are identified by using fingerprint matching, text matching, or pattern matching.

For pages that are identified by using fingerprint matching or pattern matching, you use ReadZone and SnapCCOtoDCO to write the recognition data into the runtime hierarchy.
For rental agreement pages that are identified by using text matching. You can use various text-based matching actions to locate the recognition data and write it to the runtime hierarchy.

Recognize Page ruleset with a Recognition function that includes the Read Zone action and the Snap CCO to DCO action.

Datacap starts the Recognize Page rule on all page types, even though the rule works only when the current page has a valid matching fingerprint. With manual page identification, there is no matching fingerprint. When fingerprint matching fails, Datacap writes the ID of the closest match into the LC_TemplateID variable of the page. The ReadZones action uses the recognition zones from this low confidence fingerprint even though they are not valid. To work around this problem, you add an action to the Recognize Page rule to enable the rule to exit if the identification method is manual. Later, when you open the page for verification, you define the recognition zones manually.

Procedure

To update the Recognize Page ruleset:

In the Rulesets pane, select the Recognize ruleset and click Lock/Unlock ruleset. Then, expand the Recognize ruleset and the Recognize Page rule.
Add the following action and parameters to beginning of Recognize Page > Recognition: Page Function 1.
Library Action Parameter

rrunner rrCompareNot
object1 = @P.MatchType

object2 = Manual

The finished rule is shown in the following example:

If a page has a match type of Manual, the function exits without starting ReadZones.
In the Rulesets pane, click Save.
Click Lock/Unlock ruleset and choose Publish Ruleset.