Nuance Management Center
Table Of Contents
- Dragon_AdminGuideCover_20160929_v2
- Chapter 1: Introducing the Nuance Management Server
- Dragon Group Overview
- User Groups Worksheet
- Prerequisites for the Nuance Management Center
- Accessing NMS Server: Logging in through the Nuance Management Center
- Change the NMC Administrator password
- Accessing and adding to your organization data
- Turning on data collection for your site
- Privacy of your data and Nuance data collection
- Setting up Active Directory single sign-on
- Chapter 2: Overview of NMS in the cloud
- Chapter 3: Configuring sites
- Chapter 4: Configuring groups and user accounts
- Understanding groups
- Determining site or group settings for members of more than one site or group
- Creating Groups
- Setting Privileges for administrator groups
- Viewing, modifying, and deleting groups
- Setting Dragon Group voice command options for user groups
- Creating user accounts
- Configuring user accounts
- Configuring user account details and address settings
- Administrators can send messages to other administrators
- Enable sending messages to an administrator
- Assigning user accounts to groups
- Configuring Users for Active Directory Authentication
- Import multiple users into the NMS server
- XML schema for the user XML import file
- Setting user account Dragon Group client options
- Setting Auto-Formatting Dragon Group options
- Viewing User Profile settings
- Automatically log out an administrator after a period of inactivity
- Viewing, modifying, and deleting a user account
- Finding and viewing a user account
- Modifying a user account
- Applying Dragon Settings to organizations, sites, or groups
- Chapter 5: Managing licenses
- Managing licenses
- Types of license upgrades available
- Obtaining and applying licenses
- Importing licenses included with Dragon Group
- Purchasing and obtaining new licenses
- Viewing licenses
- Viewing license usage information
- Granting licenses
- Granting a license immediately after creating a user account
- Granting a license to an existing user account
- Receiving expiration alerts and renewing licenses
- Viewing messages about expired licenses
- Renewing the License
- Revoking licenses
- Dictating with Author licenses while disconnected from network
- Chapter 6: Configuring Dragon Group settings
- Chapter 7: Managing user profiles
- Creating a user profile
- Configuring the location of Roaming user profiles
- The SSL Settings tabs
- NMS Administrative Settings: Setting site HTTP connection settings for Roamin...
- NMS Administrative Settings: Setting site SSL connection settings for Roaming...
- NMS Administrative Settings: Setting Roaming User settings and Data settings
- Chapter 8: Managing Dragon Clients
- Chapter 9: Managing messages
- Chapter 10: Managing uploads to Nuance
- Chapter 11: Working with Text and Graphics/auto-texts and custom words
- Overview of managing Text and Graphics/auto-texts and custom words
- Overview of Text and Graphics/auto-texts
- Creating shared and personal Text and Graphics/auto-texts and custom words
- Defining Text and Graphics/auto-texts
- Creating Text and Graphics/auto-texts
- Editing Text and Graphics/auto-texts
- Using Text and Graphics/auto-texts
- Adding and managing keywords for auto-texts
- Delete Text and Graphics or auto-texts
- Cutting, copying, and pasting Text and Graphics/auto-texts or words
- Searching for auto-texts, sites, groups, or users
- Viewing Text and Graphics/auto-texts details
- Importing or exporting Text and Graphics/auto-text
- Chapter 12: Working with Command Sets
- Overview of Command Sets
- Searching for Command Sets, sites, or groups in the Nuance Management Center
- Viewing Command Set details in the Nuance Management Center
- Considerations before creating or importing commands or command sets
- How conflicts between commands are identified and displayed
- Viewing information about Command and Command Set conflicts
- Adding Command Sets in the Nuance Management Center
- Modifying Command Sets in the Nuance Management Center
- Deleting Command Sets in the Nuance Management Center
- Chapter 13: Working with custom words
- Chapter 14: Working with Lists
- Chapter 15: Troubleshooting issues
Chapter 12: Working with Command Sets
availability, type, and contents) can be identified using the ‘Purge Identical MyCommands’
tool in the Dragon Client. For details, see the Dragon Help.
When comparing commands from different command sets or with MyCommands, the
names of lists used by the command are ignored so that the keywords and ‘signature’ of the
command are compared. This avoids conflicts in cases where the only difference is the
values within the lists, which could have conflicting values and unintended results when
loaded into the vocabulary. This comparison is performed because list-value-level conflicts
can be expensive to determine, and this type of conflict detection is currently not supported.
Example 1:
CmdSet1: Do this <list1> then <list2>
CmdSet2: Do this <list3> then <list4>
CmdSet3: Do this then
CmdSet4: Do this
Dragon treats the commands as follows when comparing across Command Sets:
CmdSet1: Do this <> then <>
CmdSet2: Do this <> then <> // Conflicts with CmdSet1 command
CmdSet3: Do this then
CmdSet4: Do this
In this case, the command in CmdSet2 conflicts with the CmdSet1 command because the
only difference is the name of the lists.
If the first two commands were defined in the SAME command set then this restriction would
be loosened, as the chances for an unintended conflict are lower.
The goal is to avoid unexpected results when commands from different command sets
(including MyCmds) end up resulting in the same spoken form in the vocabulary due to
conflicting list values.
To avoid these problems the commands and lists from each command set need to be
distinct, as much as possible.
Example 2:
An important exception to the above comparison rules is the case when the commands are
list-only, and have no other keywords. For example:
CmdSet1: <list5> <list6>
CmdSet2: <list7> <list8>
CmdSet3: <list5> <list6>
These commands have no keywords other than the list values themselves. If the list names
are eliminated the command signatures would look like this:
CmdSet1: <> <>
CmdSet2: <> <>
134