Advanced tab
Use this tab to set the options for the search of a specified collection.
When a document or mail massage is to be routed to the server using Appended path functionality,
the component has to find the specified location and check if a document with the same name already exists at this location.
On this tab you can configure the parameters of the search which can improve component performance of the component and its reliability.
For most user scenarios, the default options are sufficient.
| Option | Description |
|---|---|
| Search compatibility options | This group of settings allows you to specify the search method for the component. |
| Scan through children list |
When you select this check box, the component will get the first level child collections and search for the first collection specified in the additional path,
then get the list of child collections of the collections found at the first step and search for the second collection
and so on until the last collection in the specified path.
This option is recommended in the case of a hierarchical structure of collections with relatively small number of child collections in each collection;
for example, if you use the following structure for the Appended path setting on the Document tab:
~XDS::%Y~/~XDS::%m~/~XDS::%D~/~XDS::%H~/~XDS::%M~/~XDS::%S~.
|
| Use indexed search |
When you select this check box, the component will use server indexed search to find a required collection.
This option is recommended in the situation of a non-hierarchical structure of collections on the server.
For example, if you use the following structure for the Appended path setting on the Document tab:
~XDS::%Y~_~XDS::%m~_~XDS::%D~_~XDS::%H~_~XDS::%M~_~XDS::%S~,
there will be only one level of collections and the number of collections may be rather big.
In this case, indexed search requests will be performed faster than direct search.
|
| Check parent in search request |
When you select this check box, the component makes a search request and instructs the server to check
if the requested collection has the required parent.
Old versions of DocuShare server (prior to 6.5.3) have an issue with indexed search:
the search returns all collections with a specified name that can be found on the server.
To work around, use Check parent in search results option.
|
| Check parent in search results |
When you select this check box, the component first executes the request and then verifies if the found collection
has the required parent.
Old versions of the DocuShare server (prior to 6.5.3) have an issue with indexed search:
the search returns all collections with a specified name found on the server. You might want to limit the number of search
results if you are absolutely sure that the restricted result will include the collections you need.
|
| Limit search results | Select this check box to limit the number of search results when the component checks the parent. |
| Items limit | Enter the number of items in the search results that will be checked for the parent. The minimum number of items in the search results is 2. This is necessary for the correct work of the Check for ambiguous collections names functionality. |
| Use JSP search script |
Select this option to use script-based search method.
This search method is preferable for any folder structure as it works faster and more correctly than other search methods.
In order to make this search method work, the administrator should deploy JSP script based on the Xerox sample dsfind.jsp into the DocuShare server folder:
C:\Xerox\Docushare\tomcat\webapps\docushare\jsp\extension\.
For DocuShare Server versions 4.0.1 and 5.0, use the following script: dsfindas.jsp. For DocuShare Server version 6.0 CPX, use the following script: dsfindas.jsp. When append/prepend/insert functionality is On, it is strongly recommended to use JSP search script as a search compatibility option.
In case of using another Search compatibility options there may appear the following situation:
any file may be uploaded as a new document (because indexing is not finished on the server) and
all other documents will be rejected since the component will be unable to determine to which document the input file should be appended.
|
| Check for ambiguous collections names | If this check box is selected, the component will check if there is more than one collection with the specified name on the server. If there are and this option is selected, the component will create a new collection with the specified name and the suffix "_Ambiguous" appended to it (or to the first collection in the path). The document will be stored in this collection. If this option is not selected and there is an ambiguity in the collection path, the component will go through the path and at each level select the collection that was created first. The document will be stored in the selected path. |