This content has been marked as final. Show 5 replies
The Webhelp search tool is not a Natural Language Search. Perhaps you're thinking of Webhelp Pro. It has the NLS.
Your Webhelp search parses your search string, ignores the common terms, and assumes the rest of the words are required to be part of the topic. It's some compact client-side scripting that loads with a minimum of overhead.
You can use multiple ORs to widen your search range.
You're right. I am using WebHelp Pro. I just can't seem to get the NLS to work correctly, even using synonym groups and directional synonyms.
The online help doesn't do a very good job of explaining how to use NLS, either. It would be helpful to understand what WebHelp Pro looks for in the text when someone types in a question. Does it look at key words, groupings of words, etc? I don't understand why adding the words "What are my" reduces the search results.
I'm going to bet that you're testing the NLS feature on a project that you generated but did not publish to a RoboEngine server. The NLS feature will not work on a project generated to your local drive; it must be published first. So if you generate your project and then view it, the behavior you describe--questions don't return results, but terms do--will occur. (Actually, it's not a "question" issue; it's the result of entering too many terms into the search field.)
On the off chance that you're testing the feature from the RoboEngine server, check your RoboEngine search settings. It's possible that they're set too high, which lowers the number of search results.
To check the engine's search settings:
1. Open the Configuration Manager.
2. Open the engine.
3. Click the Projects icon.
4. Check the number in the Relevance Threshold field. The higher the number, the fewer search results the engine returns.
I have actually published the help file to the server and the Relevance Threshold is set to 80%. Any lower and I get a lot of irrelevant results.
So you generated the project, published it to the server, accessed the help system hosted on the server, and still couldn't get the NLS feature to work? If so, I'm stumped--I see the behavior you describe only when I try to use NLS feature without going to the RoboEngine-hosted output. Perhaps someone here will be able to lead you down a better path.