User guide

Appendix A, Using the Flex Processor Rules Manager
A-28 Ipro eCapture User Guide www.iprotech.com
Q1 2014 877-324-4776
If Advanced Duplicate Checking is enabled, then MD5 hash matches are veri-
fied with bit-by-bit comparison before being flagged as a match.
File Name Match requires that the filenames of the two files (loose files only,
not e-mails) must be the same. Bit-by-bit comparison and file name compari-
son does not occur for e-mail types.
(If de-duplication is selected all other criteria is not available.)
A file is checked for duplication when a job starts. At this time, the Selection-
IDs are assigned to the documents. These SelectionIDs are closely tied with
the order that the documents were discovered. Documents are distributed to
workers; and it is at this time, that the document is checked against all previ-
ously ‘processed’ documents (the originals) in line with the selected scope and
duplication options.
Ensure the appropriate Action is selected. See the section Defining Actions for
a Flex Processor Rule on page A-15. If necessary, determine whether or not a
de-duplication flag should be set.
There are two scope options available when using Duplicates:
a) Maintain Compound Document Structure: The action will be performed
on a file if the criteria match the file or the file's parent. To look at it from the
other direction, if a parent file matches a Rule's criteria, the action of that Rule
will be applied to that parent document and all of its children. Only an entire
family of documents are considered duplicates. If a parent document is not
identified as a duplicate, but its child document is, no documents would be
identified as a duplicate and hence no documents removed.
The Allow Child Originals option is selected by default and controls how child
documents are compared during de-duplication when the option Maintain
Compound Document Structure is selected. This allows documents, including
loose files, to de-duplicate against child documents predicated on order they
are processed. For example, if two Word documents exist with the same
MD5Hash value; one as child attachment to an Email parent, the other as a
loose Parent, the loose Parent (Word document) is removed. However, if the
loose Parent (Word document) is encountered before the Email (parent) and
its Word (child attachment) the Word (child attachment) is not removed.
Deselect this option to force duplicate checks at the parent level only. Note: A
system-level default can be set by updating the DedupAllowChildOriginals col-
umn in the ConfigurationProperties table in the CONFIG database to either
true or false. However, the setting in the Flex Processor rule takes precedence.