Consider the following when working with ACD groups:
Availability
When you add an ACD group, you need to log out of CMS Supervisor and log back in to see the new group.
Capacities/Performance
A maximum of 12 ACD groups can exist on an AvayaCMS server.
Each ACD group can contain up to eight ACDs.
CMS must be in single-user mode to administer ACD groups.
Roles/Definitions
An ACD group cannot serve as the CMS master ACD.
An ACD group cannot be deleted if it is set as the current ACD.
When you create ACD groups, CMS automatically assigns an ACD ID number, which you cannot change.
Pseudo-ACDs cannot be a member of an ACD group.
When an ACD group is deleted, all synonyms assigned to its member ACDs will remain.
Synonyms
Entity synonyms must be unique for an ACD group and across all ACDs that are members of the ACD group.
In overlapping ACD groups with common ACD members, entity IDs must be mutually exclusive. Otherwise, a synonym conflict can occur.
Other
User permissions are administered separately for an ACD group and its member ACDs.
CMS real-time custom reports are only displayed if data collection is enabled and the ACD link status is up for at least one member ACD in the specified ACD group. An error message will be displayed if these conditions are not met.
Custom reports that are created with the single ACD option enabled cannot be run for an ACD group and vice versa.
If a backup is created on a CMS server where the Global Dictionary feature is authorized, the data can only be restored on a CMS server that also has this feature authorized. If the Global Dictionary authorizations between a backup and the target CMS server do not match, an error is displayed, a message is written to the error log, and the restore or migration fails.
