These methods are globally defined
Document Review scripts that are configured to check whether
documents are correctly classified and separated. These methods augment the predefined and configurable rules to enable project
administrators to perform more complex checks than the
predefined or
configurable rules.
In order for a
Document Review method to work, it needs to be added to the
project script. Each added method is available in the Object list where it can be added to the script and modified as necessary.
You can configure a
Document Review method that specifies that a document of class
"Attachment" always follows a document of class
"Application Form."
Another example is a batch that needs to contain either one document classified as
"Opening Letter" or one document classified as
"Closing Letter." The batch cannot contain both.
Documents classified as an
"Application Form" always contain an even number of pages.
Another example is looking at documents classified as
"Purchase Order 2008." These documents are only valid if their batch is scanned during or after the year 2008. A
Document Review method can be created to check a custom storage
string containing the batch scan date to determine if the document is valid.
Search results
Search tips
The search returns topics that contain terms you enter. If you type more than one term, an OR is assumed, which returns topics where any of the terms are found. Enclose your search terms in quotes for exact-phrase matching.
The search also uses fuzzy matching to account for partial words (such as install and installs). The results appear in order of relevance, based on how many search terms occur per topic. Exact matches are highlighted.
To refine the search, you can use the following operators:
Type + in front of words that must be included in the search or - in front of words to exclude. (Example: user +shortcut –group finds shortcut and user shortcut, but not group or user group.)
Use * as a wildcard for missing characters. The wildcard can be used anywhere in a search term. (Example: inst* finds installation and instructions.)
Type title: at the beginning of the search phrase to look only for topic titles. (Example: title:configuration finds the topic titled “Changing the software configuration.”)
For multi-term searches, you can specify a priority for terms in your search. Follow the term with ^ and a positive number that indicates the weight given that term. A higher number indicates more weight. (Example: shortcut^10 group gives shortcut 10 times the weight as group.)
To use fuzzy searching to account for misspellings, follow the term with ~ and a positive number for the number of corrections to be made. (Example: port~1 matches fort, post, or potr, and other instances where one correction leads to a match.)
Note that operators cannot be used as search terms: + - * : ~ ^ ' "
