Skip to main content
Extraction Rules activity debugging entails checking and correcting the activity properties. Once an element is created, we recommend compiling the activity and matching it to each test image. Make sure that the activity does not contain any errors, and that all required objects are matched. Sometimes objects will not be detected because they were not located in the search region or because they did not satisfy the element properties. As such, debugging consists of discovering images with match errors, hypothesis analysis, correction of element properties, and a second matching attempt. Once the activity has been corrected, its needs to be matched to problem pages a second time in order to make sure that the errors have been fixed, as well as to all other pages (to make sure that the corrections have not interfered with the matching of other pages). In general, matching results are viewed multiple times during the creation of an Extraction Rules activity. Matching is performed only for the active elements and fields. Its duration is directly related to the number of active elements. To reduce matching time while debugging, you can temporarily disable the elements that don’t affect the results for the element you’re currently working on. You can change the state of an element using its context menu. You can also select several elements and change their state simultaneously.
Note: Remember to disable fields linked to the disabled elements, otherwise matching will not be started.