Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Troubleshooting
- Button options are not displaying properly
- File variables not passed into wizard flow
- Format not found
- JavaScript syntax errors
- Query failed to provide correct results
- Query returned a list of records rather than a single record
- RAD expression syntax errors
- Records are not sorted properly
- Wizard stops with "Could not continue" errors
- Run a trace
Run a trace
If you receive an error message, use the following to trace the error to get more detail on the message you receive. You can also run a trace when the wizard flow does not take the expected path.
To run a trace, follow these steps:
- Enter the RTM:3 and debugdbquery:999 parameters in the Service Manager sm.ini file.
-
Start a new client connection.
For complete details, see the instructions in the Diagnostics and Tuning white paper.
- Within the trace, search for the first call to the wizard.run RAD application.
- Next, follow the flow of the wizard, checking the dbquery statements against the wizard table to see which wizard is called next.
- Follow the trace to the error message if one was received, or follow the trace to understand which path the application took through the wizard flow.
-
Use print statements in the JavaScript expressions within the wizard panels, to write additional information to the log file. For example, the content of variables that will influence which wizard will be run next or statements as to which wizard is executed at the time.
Note Remember to remove these debug statements before putting the wizard into production.