Nuance Management Center

Chapter 12: Working with Command Sets
Note: You can only view the top level search result objects. For example, if a site is found
and displayed in the search results, you cannot click on the site to view it's groups.
Viewing Command Set details in the Nuance
Management Center
1. Perform the steps described in Searching for Command Sets, sites, or groups.
Considerations before creating or importing commands
or command sets
Recommended naming conventions for a command set
When you create a command set, give the command set a descriptive name that indicates
the organization, group, application, or department it is meant for:
OrgID_Department_App_Commands
Where:
--OrgID is the organization ID for the overall organization
--Department is the specific department the Command Set is meant for
--App is the application that the commands apply to.
For example: 123456_Radiology_EMR_Commands
Recommended naming conventions for a list
When you create a new list, give it a name that is specific to its deployment context.
During a Dragon Group dictation session, active command set commands, custom
commands, and built-in commands are loaded into memory.
For commands with lists, if two lists have the same name but are from different command
sets, then they could potentially conflict. To minimize list name conflicts, it is recommended
that lists within each command set have their own prefix or extension.
The complexity of the prefix or extension depends on the context of the intended deployment
and parent command set.
Recommended naming conventions for a command
Check for naming conflicts between commands and especially conflicts between lists used
by commands, both in the name of the lists and the contents of the lists.
Try to make command names very unique and specific, especially if they are likely to conflict
with other commands.
To avoid conflicts between Command Sets and with custom and built-in commands, it is
important that the name (and spoken form) of the command be different from other
commands that are at the same availability level (global, application-specific, window-
specific).
Try to avoid generic command names, especially for global commands where the chance of
unintended conflicts is higher.
132