› AutoStore › Route Components › Hummingbird/Open Text eDOCS › Restrictions and limitations
Restrictions and limitations
This component works with the Hummingbird/Open Text eDOCS DM server and client versions 5.1.0.5, 5.3.0, 5.3.1, 6.0.1, and 10.
The component does not work on Windows Server 2008 with the Hummingbird/Open Text eDOCS DM client version 5.1.0.5 or 6.0.1
since these versions of the client do not support this operating system. It does work, however,
on Windows Server 2008 with the Hummingbird/Open Text eDOCS DM client v5.3.0.
You may add a document to one library at a time. You cannot select multiple libraries.
The component sends only the documents with extensions specified in the File extensions list.
Only Profiles that have the ”TYPIST_ID” field are supported when you are working with the server version 5.1.0.5.
Other profiles, such as search profiles, cannot be used.
Certain fields are excluded from the listing of fields. This is because they are used on the dialogs themselves.
An example includes DOCNAME, which refers to the documents name. If this field actually exists on the profile form,
its value is either the original name of the document or the value of the Rename schema.
Other excluded fields are AUTHOR, AUTHOR_ID, SECURITY, TYPIST, APP_ID, TYPIST_ID, and APPLICATION.
The Profile type functionality is available only when you are working with the Hummingbird/Open Text eDOCS DM server version 6.0.1.
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: + - * : ~ ^ ' "
