As of Friday October 16th, access to restricted content on this site now requires you to log in with your Genesys account. If you don't have an account, you can request one at these locations: Request MyPartner Portal Account or Request My Support Account.
Jump to: navigation, search

spellchecker.<media-type>.prompt-on-send

Section: interaction-workspace
Default Value: false
Valid Values: true, false
Changes Take Effect: At the next interaction.
Introduced: 8.5.105.12

Specify by media type whether you want agents to be prompted when they click Send if there are misspelled words in an email, chat, or SMS message. The following media names are supported: chat, email, sms.

spellchecker.corporate-dictionary-file

Section: interaction-workspace
Default Value:
Valid Values: Absolute or relative path to a text file.
Changes Take Effect: When the application is started or restarted.


Specifies the name and the path to your corporate dictionary file. The path can be relative to the Workspace working directory (for example: Dictionaries\CorporateDictionary.txt) or an absolute path (for example: C:\PathToDictionaries\CorporateDictionary.txt). The file must consist of a list of words (one word per line) with ANSI, Unicode, UTF-8 encoding (any encoding accepted by Microsoft .NET).

spellchecker.corporate-dictionary

Section: interaction-workspace
Default Value:
Valid Values: Comma-separated list of words
Changes Take Effect: When the application is started or restarted.


Specifies a comma-separated list of dictionary words that conform to the limitations of allowable characters in the configuration layer. Typically you would use this list to specify common words in your company, such as your company name or product name.

Spellchecker options

Tip
For the most up to date Workspace Desktop Edition configuration options, see the Genesys Configuration Option Database.

Related Resources

The following topic discusses the implementation of these options:

This page was last edited on July 23, 2020, at 12:24.

Feedback

Comment on this article:

blog comments powered by Disqus