Views:

Situation:
You have documents with various dashes or other symbols that are not searchable via Fulltext. 

Solution:
The reason for this is that Fulltext filters out most symbols by default. We have the option to configure Fulltext to not filter certain values.

Please follow steps detailed in this article to properly configure your Fulltext to read special characters:

Note: This solution is only applicable to on-premise DocuWare systems.

   1. Verify that the system is on version 7.2 or higher. This functionality did not exist until version 7.2.

   2. Navigate to "dwmachine.config" located in "%ProgramData%\DocuWare\ServerConfig"


   3. Add the following value listed below to this .config file:
<Setting Key="FulltextConfigPath" Value="%ProgramData%\DocuWare\ServerConfig\DocuWare.Fulltext.settings" Encrypted="false"/> on all servers.

   4.Create a new Text file, copy and paste the following content, save the file with name "DocuWare.Fulltext.settings", place the file in the following path: %ProgramData%\DocuWare\ServerConfig
Note: If the desired character is not included in the below list, you may alter the file to include it.

<configuration>
<configSections>
<section name="SpecialSymbolsConfiguration" type="DocuWare.Fulltext.SpecialSymbolsConfigSection, DocuWare.FulltextCommon" />
</configSections>
<SpecialSymbolsConfiguration>
<SymbolsIncluded>
<symbol value="-"/>
<symbol value="—"/>
<symbol value="–"/>
<symbol value="‒"/>
<symbol value="-"/>
<symbol value="−"/>
<symbol value="("/>
<symbol value=")"/>
<symbol value="<"/>
<symbol value=">"/>
<symbol value="{"/>
<symbol value="}"/>
<symbol value="+"/>
<symbol value="="/>
<symbol value="!"/>
<symbol value="#"/>
<symbol value="%"/>
</SymbolsIncluded>
</SpecialSymbolsConfiguration>
</configuration>

   5. After previous sets are completed, reboot the server and you should be able to use special characters that Fulltext can now read.

KBA applicable for On-premise Organizations ONLY.