Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Configuring spelling checker settings

Updated on March 11, 2021

By using the spelling checker, you can categorize the text with a greater confidence score, making the analysis more accurate and reliable.

The spelling checker feature is available only for categorization analysis. You can use English, Spanish, French, and German default dictionaries. You can also upload custom dictionaries that best suit your business needs. Checking spelling is available only when categorization analysis is enabled on the Select Analysis tab. Each Spell checker Decision Data rule can have multiple language dictionaries associated with it. Each dictionary decision data has the following properties:
  • Language – Indicates the language of the dictionary.
  • Spell Checker Property – Contains text files with dictionary entries. The text files can be classified into different categories (for example, Main, Supplemental, and so on).
  1. In the Records panel, click DecisionText Analyzer.
  2. Click the Advanced tab.
  3. In the Topic settings section, select the Enable spell checking check box.
  4. In the Spell checker field, select a spelling checker decision rule.
    Note: The default spelling checker decision data rule is pySpellChecker.
  5. If you modified an instance of a Spell checker Decision Data rule that your application is currently using, perform one of the following actions:
    • Save the property to a different branch.
    • Save the property to a different rule set version.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us