Cisco Unified CCX Database Schema Guide, Release 8.5
Cisco Unified CCX Database Schema Guide, Release 8.5
February 2012
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/web/siteassets/legal/trademark.html. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not
imply a partnership relationship between Cisco and any other company. (1005R)
Preface i
Supervisor 1-49
Team 1-50
TeamCSQMapping 1-51
WorkflowTask 1-52
EEMActiveEmail 1-53
EEMContactEmailDetail 1-54
EEMEmailAgentStateDetail 1-56
EEMEmailStatusDescription 1-57
EEMQueueAgentDetail 1-57
EEMReasonCodeDescription 1-59
EEMStateDescription 1-59
EEMTablesVersion 1-59
INDEX
The Database Schema Guide for Cisco Unified Contact Center Express (Unified CCX) describes how
data is organized in the Unified CCX databases. This manual provides detailed description of the records
and fields in each database table and enables you to create your own reports.
Audience
This manual is intended for system managers, administrators, and developers who want to create custom
reports using the generally available third-party programs that create reports from databases.
Organization
The “Database Table Details” section on page 2 describes each table in the Unified CCX database. The
descriptions are arranged in the alphabetical order by table name. Each description includes a detailed
explanation of each record in the table. The Index helps you find information in this book.
Conventions
This manual uses the following conventions:
Convention Description
boldface font Boldface font is used to indicate commands, such as user entries, keys, buttons, and
folder and submenu names. For example:
• Choose Edit > Find.
• Click Finish.
italic font Italic font is used to indicate the following:
• To introduce a new term. Example: A skill group is a collection of agents who
share similar skills.
• For emphasis. Example:
Do not use the numerical naming convention.
• A syntax value that the user must replace. Example:
IF (condition, true-value, false-value)
• A book title. Example:
See the Cisco Unified CCX Installation Guide.
window font Window font, such as Courier, is used for the following:
• Text as it appears in code or that the window displays. Example:
<html><title>Cisco Systems,Inc. </title></html>
<> Angle brackets are used to indicate the following:
• For arguments where the context does not allow italic, such as ASCII output.
• A character string that the user enters but that does not appear on the window
such as a password.
Related Documentation
The following documents contain additional information about the Unified CCX database and the
information stored in the database:
• Cisco Unified CCX Administration Guide
• Cisco Unified CCX Historical Reports User Guide
• Cisco Unified CCX Historical Reporting Administrator and Developer Guide
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.
This manual describes how data is organized in the Unified CCX database. The Unified CCX database
stores the data in the following two types of databases:
• db_cra – Used to store information for historical and real-time reports, including Unified CCX
configuration information, stored procedures, and call statistics.
• db_cra_repository - Used to store information related to prompts, grammars, scripts, and
documents.
All the tables described in this document are in the above two databases.
Note SQL is case-insensitive and the queries written against the database can be in any case. However, you
might have to change the case for the column names depending on the third-party tool that you use for
querying the database. Refer to the documentation for these third-party tools for more information.
Fields
79415
3 1 Drum 1 NULL
Database tables and the number and names of their fields are constant. The number of records in a table
and the data that those records contain will vary according your system.
Table Relationships
Related tables in a database share one or more common fields. For example, both the Skill and the
SkillGroup tables include the skillID field. Each record in the Skill table is related to each record in the
SkillGroup table that shares the same skillID value.
Relationships between tables can be one-to-one or one-to-many. For example, because one skill can be
associated with many skill groups, the relationship between the Skill and SkillGroup tables is
one-to-many. On the other hand, each call or call leg has its own set of data about the agent who handled
the call and other information. Therefore, the relationship between the AgentConnectionDetail and
ContactCallDetail table is one-to-one.
Each database table description in this manual is followed by a Related Tables section. These sections
show the fields by which a table is related to other tables. If the fields have different names in each table,
these sections show the mapping.
Note For storage characteristics and limitations of the data types used for the fields in the databases
refer to "IBM Informix SQL Reference Guide". The date and time in the database fields are
stored in Coordinated Universal Time (UTC).
– Whether the NULL value is valid for the field. “NULL” if the NULL value is or “NOT NULL”
if the NULL value is not valid.
Note If the NULL value is valid, the database will record a value of -1 for a numeric field and an empty string
for other fields.
– “Primary Key” if the field is a primary key, or part of a primary key, in the database table.
Overview of Tables
The following tables are described in this guide:
• AgentConnectionDetail, page 4, contains records written for calls that are connected to an agent.
• AgentStateDetail, page 7, contains records written when an agent changes state.
• AreaCode, page 8, contains the area code and time zone information used for outbound calls.
• Campaign, page 9 contains records with campaign configuration information.
• CampaignCSQMap, page 11, provides a relationship between campaigns, and Contact Service
Queues (CSQs).
• ContactCallDetail, page 13, contains records written for every incoming, outgoing, or internal call.
• ContactQueueDetail, page 19, contains records written for calls that are queued for CSQs; one
record for each CSQ is queued.
• ContactRoutingDetail, page 21, contains records written for calls that are queued for CSQs; one
record for each call.
• ContactServiceQueue, page 22, contains records written for CSQs configured on the Unified CCX
Administration user interface.
• CrsApplication, page 24, contains records about applications that are uniquely identified by
application name.
• CrsGroup, page 26, contains records about groups that are identified by a combination of group
class name and group ID.
• CrsTrigger, page 28, contains records about triggers that are uniquely identified by trigger name.
• DialingList, page 29, contains records with outbound contacts that need to be dialed for a particular
campaign.
• MonitoredResourceDetail, page 33, contains records written for agents who are monitored by a
supervisor.
• ProfileIDMapping, page 34, contains records written for profiles defined on the Unified CCX
Administration user interface.
• RemoteMonitoringDetail, page 35, contains records written for remote monitoring calls made by a
supervisor.
• Resource, page 37, contains records written for resources (agents) that are configured on the Cisco
Unified Communications Manager (Unified CM) Administration user interface.
• ResourceGroup, page 39, contains records written for resource groups configured on the Unified
CCX Administration user interface.
• ResourceSkillMapping, page 40, is a relationship table between resources and skills.
• RmonCSQConfig, page 41, contains records written for CSQs configured for a supervisor’s remote
monitoring allowed list on the Unified CCX Administration user interface.
• RmonResConfig, page 42, contains records written for resources configured for a supervisor’s
remote monitoring allowed list on the Unified CCX Administration user interface.
• RmonUser, page 43, contains records written for remote monitoring supervisors configured on the
Unified CCX Administration user interface.
• RtCSQsSummary, page 44, contains real-time statistics for configured CSQs.
• RtICDStatistics, page 45, contains Unified CCX summary statistics.
• Skill, page 47, contains records written for skills configured on the Unified CCX Administration
user interface.
• SkillGroup, page 48, is a relationship table between skills and CSQs.
• Supervisor, page 49, contains records written for supervisors configured on the Unified CCX
Administration user interface.
• Team, page 50, contains records written for teams configured on the Unified CCX Administration
user interface.
• TeamCSQMapping, page 51, is a relationship table between teams and CSQs.
• WorkflowTask, page 52, contains records written for workflow tasks that are executed.
• EEMActiveEmail, page 53, contains one row for each email message being processed by an agent.
• EEMContactEmailDetail, page 54, contains one row for each email message currently in the system.
• EEMEmailAgentStateDetail, page 56, contains one row for each Email state change for an agent.
• EEMEmailStatusDescription, page 57, contains descriptive text (in English only) for each possible
email status.
• EEMQueueAgentDetail, page 57, (associates an agent and an email message, contains one record
for each email message an agent is working on.
• EEMReasonCodeDescription, page 59, contains descriptive text (in English only) for each possible
reason code.
• EEMStateDescription, page 59, contains descriptive text (in English only) for each email state.
• EEMTablesVersion, page 59, contains a single row indicating the version of the EEM database
tables. This is used when upgrading from a previous version.
AgentConnectionDetail
Database table name: AgentConnectionDetail
The Unified CCX system creates a new record in the AgentConnectionDetail table when an agent
disconnects a call or a leg by hanging up or by transferring the call. (A new call leg starts each time that
a call is transferred, except when a call is transferred from a Cisco Computer Telephony Interface [CTI]
port to an agent.)
An AgentConnectionDetail record contains information relating to the agent who handled the call or call
leg.
The AgentConnectionDetail table contains the fields shown Table 1-1.
Related Tables
• ContactCallDetail, page 13 (via sessionID, sessionSeqNum, nodeID, and profileID)
• ContactRoutingDetail, page 21 (via sessionID, sessionSeqNum, nodeID, profileID, and qIndex)
• ContactQueueDetail, page 19 (via sessionID, sessionSeqNum, nodeID, profileID, and qIndex)
• DialingList, page 29 (via dialingListID)
• MonitoredResourceDetail, page 33 (sessionSeqNum maps to monitoredSessionSeqNum, via
profileID, and nodeID)
• ProfileIDMapping, page 34 (via profileID)
• RemoteMonitoringDetail, page 35 (sessionID maps to monitoredSessionID, via profileID, and
nodeID)
AgentStateDetail
Database table name: AgentStateDetail
The Unified CCX system creates a new record in the AgentStateDetail table each time the state of an
agent changes. An AgentStateDetail record contains information about the agent and about the event that
caused the agent state change.
The AgentStateDetail table contains the fields shown in Table 1-2.
Related Tables
• ProfileIDMapping, page 34 (via profileID)
• Resource, page 37 (agentID maps to resourceID and via profileID)
AreaCode
Database table name: AreaCode
The AreaCode table contains a mapping of area codes and their time zones. This table is used as a
reference for populating the gmtPhone and dstPhone columns of the DialingList table. This table is
pre-populated by the Unified CCX system with the data for North America during the installation
process, using a SQL script that the installer invokes. If the Unified CCX is installed in a different
location, administrators can enter the area code and time zone information for that region using Unified
CCX Administration, and the data is stored in this table.
The AreaCode table contains the information shown in Table 1-3.
Related tables
• DialingList, page 29 (via gmtZonePhone01, gmtZonePhone02, and gmtZonePhone03)
• ProfileIDMapping, page 34 (via ProfileID)
Campaign
Database table name: Campaign
The campaign configuration information is stored in this table. A campaign is associated with one or
more CSQs. This mapping of Campaigns and CSQs is stored separately in CampaignCSQMap table.
The Campaign table contains the fields shown in Table 1-4
Related Tables
• CampaignCSQMap, page 11 (via campaignID)
• ContactCallDetail, page 13 (via campaignID and profileID)
• DialingList, page 29 (via campaignID)
• ProfileIDMapping, page 34 (via profileID)
CampaignCSQMap
Database table name: CampaignCSQMap
The CampaignCSQMap table shows the relationship between campaigns and contact service queues
(CSQs). A new record is created in the CampaignCSQMap table when a campaign is associated with a
CSQ in Unified CCX Administration.
The CampaignCSQMap table contains the fields shown in Table 1-5
Related Tables
• Campaign, page 9 (via campaignID)
• ContactServiceQueue, page 22 (csqID maps to contactServiceQueueID)
CampaignData
Database table name: CampaignData
If you have configured a campaign as an outbound IVR campaign and have chosen Predictive dialer
type, the number of lines per port along with the other parameters are stored in the CampaignData table
every half hour.
The CampaignData table contains the fields shown in Table 1-6.
Related Tables
• Campaign, page 9 (via campaignID)
ContactCallDetail
Database table name: ContactCallDetail
The Unified CCX system creates a new record in the ContactCallDetail table for each call or call leg
processed by the system. A new call leg starts each time that a call is transferred or redirected, except
when a call is transferred from a Cisco CTI port to an agent.
A ContactCallDetail record contains detailed information about the call or leg. At least one such record
will exist for each call.
The ContactCallDetail table contains the fields shown in Table 1-7.
Related Tables
• AgentConnectionDetail, page 4 (via sessionID, sessionSeqNum, nodeID, and profileID)
• Campaign, page 9 (via campaignID)
• ContactQueueDetail, page 19 (via session ID, sessionSeqNum, nodeID, profileID)
• ContactRoutingDetail, page 21 (via sessionID, sessionSeqNum, nodeID, and profileID)
• MonitoredResourceDetail, page 33 (sessionSeqNum maps to monitoredSessionSeqNum, via
sessionID, profileID, and nodeID)
• ProfileIDMapping, page 34 (via profileID)
• RemoteMonitoringDetail, page 35 (sessionID maps to monitoredSessionID, via sessionID,
sessionSeqNum, profileID, and nodeID)
• Resource, page 37 (via originatorID/destinationID maps to resourceID when
originatorType/destinationType is 1, via profileID)
ContactQueueDetail
Database table name: ContactQueueDetail
The Unified CCX system writes the record when the call is queued for CSQs; then one of the following
happens:
• Call is abandoned while queued for CSQs
• Call is being dequeued
• Caller is connected to an agent
The Contact Queue Detail table contains the fields shown in Table 1-8.
Related Tables
• AgentConnectionDetail, page 4 (via sessionID, sessionSeqNum, nodeID, profileID, and qIndex)
• ContactCallDetail, page 13 (via sessionID, sessionSeqNum, nodeID, and profileID)
• ContactRoutingDetail, page 21 (via sessionID, sessionSeqNum, nodeID, profileID, and qIndex)
• ContactServiceQueue, page 22 (targetID maps to recordID when targetType is 0, via profileID)
• MonitoredResourceDetail, page 33 (sessionSeqNum maps to monitoredSessionSeqNum, via
profileID, and nodeID)
ContactRoutingDetail
Database table name: ContactRoutingDetail
The Unified CCX system creates a new record in the ContactRoutingDetail table for each Unified CCX
call or call leg that is queued for one or more CSQs. A new call leg starts each time that a call is
transferred or redirected, except when a call is transferred from a Cisco CTI port to an agent. The system
also creates a new record in the ContactRoutingDetail table if a call is conferenced to a Unified CCX
script.
A ContactRoutingDetail record contains information about call priority and accumulated queue time.
This differs from the ContactQueueDetail record which shows individual queue time for each CSQ.
The Contact Routing Detail table contains the fields shown in Table 1-9.
Related Tables
• AgentConnectionDetail, page 4 (via sessionID, sessionSeqNum, nodeID, profileID, and qIndex)
• ContactCallDetail, page 13 (via sessionID, sessionSeqNum, nodeID, and profileID)
• ContactQueueDetail, page 19 (via sessionID, sessionSeqNum, nodeID, profileID, and qIndex)
• MonitoredResourceDetail, page 33 (sessionSeqNum maps to monitoredSessionSeqNum, via
profileID, and nodeID)
• ProfileIDMapping, page 34 (via profileID)
• RemoteMonitoringDetail, page 35 (sessionID maps to monitoredSessionID, via profileID, and
nodeID)
ContactServiceQueue
Database table name: ContactServiceQueue
The Unified CCX system creates a new record in the ContactServiceQueue table when a CSQ is set up
in Unified CCX Administration.
A ContactServiceQueue record contains information about the CSQ. One such record exists for each
active and inactive CSQ. When a CSQ is deleted (deactivated), its record still remains in the database
marked as inactive; that is, the active field value is “f”.
The ContactServiceQueue table contains the fields shown in Table 1-10.
Related Tables
• ContactQueueDetail, page 19 (recordID maps to targetID when targetType is 0, and via profileID)
• ProfileIDMapping, page 34 (via profileID)
• RemoteMonitoringDetail, page 35 (recordID maps to origMonitoredID when origMonitoredIDType
is 2, and via profileID)
• ResourceGroup, page 39 (via resourceGroupID and profileID)
• SkillGroup, page 48 (via skillGroupID and profileID)
• TeamCSQMapping, page 51 (contactServiceQueueID maps to csqID, and via profileID
CrsApplication
Database Table Name: CrsApplication
The CrsApplication table records application information. An application is uniquely identified by
applicationName. When an application is created, a new record is inserted into this table. When an
application is modified, the old record is marked as inactive, and a new record is inserted into the table
with a new recordID. When an application is deleted, the corresponding record is marked as inactive.
The CrsApplication table contains the information shown in Table 1-11
Related Table
• ProfileIDMapping, page 34 (via profileID)
CrsGroup
Database Table Name: CrsGroup table
The CrsGroup table describes group information. A group is uniquely identified by the combination of
groupClassName and groupID. When a group is created, a new record is inserted into this table. When
a group is modified, the old record is marked as inactive, and a new record is inserted into the table with
a new recordID. When a group is deleted, the corresponding record is marked as inactive.
The CrsGroup table contains the information shown in Table 1-12.
Related Table
• ProfileIDMapping, page 34 (via profileID)
CrsTrigger
Database table name: CrsTrigger
The CrsTrigger table describes trigger information. A trigger is uniquely identified by a trigger name
(triggerName). When a trigger is created, a new record is inserted into this table. When a trigger is
modified, the old record is marked as inactive, and a new record is inserted into the table with a new
recordID. When a trigger is deleted, the corresponding record will be marked as inactive.
The CrsGroup table contains the information shown in Table 1-13:
Related Table
• ProfileIDMapping, page 34 (via profileID)
DialingList
Database table name: DialingList
The DialingList table contains the outbound contacts that need to be dialed for a particular campaign.
This table is populated when a text file containing the outbound contacts is imported from the Campaigns
configuration page in the Unified CCX Administration.
When the outbound contacts are imported into the database from the Unified CCX Administration, the
callStatus field has the default value of 1 (Pending); that is, the contacts are yet to be dialed.
The DialingList table contains the information shown in Table 1-14.
Related Tables
• AgentConnectionDetail, page 4 (via dialingListID and profileID)
• AreaCode, page 8 (via gmtZone)
• Campaign, page 9 (via campaignID and profile ID)
• ContactCallDetail, page 13 (via campaignID and profileID)
• DialingList, page 29 (via campaignID)
• ProfileIDMapping, page 34 (via profileID)
MonitoredResourceDetail
Database table name: MonitoredResourceDetail
The MonitoredResourceDetail table records the actual agents who are monitored. The
RemoteMonitoringDetail table records the original agent or the CSQ that the supervisor plans to
monitor. Monitoring a CSQ involves monitoring the agents who handle calls for that CSQ. So the actual
agents (which can be more than one) that are monitored will be recorded in the MonitoredResourceDetail
table.
Related Tables
• AgentConnectionDetail, page 4 (monitoredSessionSeqNum maps to sessionSeqNum, via nodeID,
profileID)
• ContactCallDetail, page 13 (monitoredSessionSeqNum maps to sessionSeqNum, via sessionID,
nodeID, profileID)
• ContactQueueDetail, page 19 (monitoredSessionSeqNum maps to sessionSeqNum, via nodeID,
profileID)
• ContactRoutingDetail, page 21 (monitoredSessionSeqNum maps to sessionSeqNum, via nodeID,
profileID)
• RemoteMonitoringDetail, page 35 (via sessionID, profileID, nodeID, startMonitoringReqTime)
ProfileIDMapping
Database table name: ProfileIDMapping
The Unified CCX system creates a new record in the ProfileIDMapping table when a new profile is set
up in the Unified CCX Administration.
A ProfileIDMapping record shows the mapping of the profile name to its unique identifier.
The ProfileIDMapping table contains the information shown in Table 1-16.
Related Tables
• AgentConnectionDetail, page 4 (via ProfileID)
• AgentStateDetail, page 7 (via profileID)
• AreaCode, page 8 (via profileID)
• Campaign, page 9 (via profile ID)
• ContactCallDetail, page 13 (via profileID)
• ContactQueueDetail, page 19 (via profileID)
• ContactRoutingDetail, page 21 (via profileID)
• ContactServiceQueue, page 22 (via profileID)
• DialingList, page 29 (via profile ID)
• MonitoredResourceDetail, page 33 (via profileID)
• RemoteMonitoringDetail, page 35 (via profileID)
• Resource, page 37 (via ProfileID)
• ResourceGroup, page 39 (via profileID)
• ResourceSkillMapping, page 40 (via profileID)
• RmonCSQConfig, page 41 (via profileID)
• RmonResConfig, page 42 (via profileID)
• RmonUser, page 43 (via profileID)
• Skill, page 47 (via ProfileID)
• SkillGroup, page 48 (via profileID)
• Supervisor, page 49 (via profileID)
RemoteMonitoringDetail
Database table name: RemoteMonitoringDetail
The Remote Monitoring Detail Record provides information about sessions where remote monitoring is
used.
The RemoteMonitoringDetail table contains the fields shown in Table 1-17.
Related Tables
• AgentConnectionDetail, page 4 (monitoredSessionID maps to sessionID, via nodeID, profileID)
• ContactCallDetail, page 13 (monitoredSessionID maps to sessionID, via sessionID,
sessionSeqNum, nodeID, profileID)
• ContactQueueDetail, page 19 (monitoredSessionID maps to sessionID, via nodeID, profileID)
• ContactRoutingDetail, page 21 (monitoredSessionID maps to sessionID, via nodeID, profileID)
• ContactServiceQueue, page 22 (origMonitoredID maps to contactServiceQueueID when
origMonitoredIDType is 2, via profileID)
• MonitoredResourceDetail, page 33 (via sessionID, profileID, nodeID, startMonitoringReqTime)
Resource
Database table name: Resource
The Unified CCX system creates a new record in the Resource table when the Unified CCX system
retrieves agent information from the Unified CM.
A Resource record contains information about the resource (agent). One such record exists for each
active and inactive resource. When a resource is deleted, the old record is flagged as inactive; when a
resource is updated, a new record is created and the old one is flagged as inactive.
The Resource table contains the fields shown in Table 1-18.
Related Tables
• AgentConnectionDetail, page 4 (via resourceID, profileID)
• AgentStateDetail, page 7 (resourceID maps to agentID, via profileID)
• ContactCallDetail, page 13 (resourceID maps originatorID/destinationID when
originatorType/destinageType is 1, via profileID)
• ContactQueueDetail, page 19 (resourceID maps to targetID when targetType is 1, via profileID)
• MonitoredResourceDetail, page 33 (resourceID maps to monitoredRsrcID, via profileID)
• ProfileIDMapping, page 34 (via profileID)
• RemoteMonitoringDetail, page 35 (resourceID maps to origMonitoredID when
origMonitoredIDType is 1, via profileID)
• ResourceGroup, page 39 (via resourceGroupID, profileID)
• ResourceSkillMapping, page 40 (via resourceSkillMapID, profileID)
• Supervisor, page 49 (via resourceLoginID, profileID)
• Team, page 50 (assignedTeamID maps to teamID, via profileID)
ResourceGroup
Database table name: ResourceGroup
The Unified CCX system creates a new record in the ResourceGroup table when a resource group is set
up in the Unified CCX Administration.
A ResourceGroup record contains information about the resource group. One such record exists for each
active and inactive resource group.
The Resource Group table contains the fields shown in Table 1-19.
Related Tables
• ContactServiceQueue, page 22 (via resourceGroupID, profileID)
• ProfileIDMapping, page 34 (via profileID)
• Resource, page 37 (via resourceGroupID, profileID)
ResourceSkillMapping
Database table name: ResourceSkillMapping
The Unified CCX system creates a new record in the ResourceSkillMapping table when an agent is
associated with a skill in the Unified CCX Administration.
A ResourceSkillMapping record contains information about all of the skills that are assigned to
resources.
The ResourceSkillMapping table contains the fields shown in Table 1-20.
Related Tables
• ProfileIDMapping, page 34 (via profileID)
• Resource, page 37 (via resourceSkillMapID and profileID)
• Skill, page 47 (via skillID and profileID)
RmonCSQConfig
Database table name: RmonCSQConfig
The Remote Monitoring Contact Service Queue Configuration table contains the CSQs that a remote
monitoring supervisor is allowed to monitor (the supervisor’s allowed list). This table is updated when
you configure the Unified CCX system through the Unified CCX Administration pages.
The RmonCSQConfig table contains the fields shown in Table 1-21.
Related Tables
• ContactServiceQueue, page 22 (via contactServiceQueueID, and profileID)
• ProfileIDMapping, page 34 (via profileID)
• RmonResConfig, page 42 (via rmonID and profileID)
• RmonUser, page 43 (via rmonID and profileID
RmonResConfig
Database table name: RmonResConfig
The Remote Monitoring Resource Configuration table contains the list of the agents (resources) that a
remote monitoring supervisor is allowed to monitor (the supervisor’s allowed list). This table is updated
when you configure the system through the Unified CCX Administration pages.
The RmonResConfig table contains the fields shown in Table 1-22.
Related Tables
• ProfileIDMapping, page 34 (via ProfileID)
• Resource, page 37 (via resourceLoginID, profileID
• RmonCSQConfig, page 41 (via rmonID, profileID)
• RmonUser, page 43 (via rmonID, profileID)
RmonUser
Database table name: RmonUser
The Remote Monitoring User table provides information about the supervisor who is logged in to
remotely monitor agents.
The RmonUser table contains the fields shown in Table 1-23.
Related Tables
• ProfileIDMapping, page 34 (via profileID)
• RemoteMonitoringDetail, page 35 (loginID maps to remoteLoginID, via profileID, and rmonID
• RmonCSQConfig, page 41 (via rmonID and profileID)
RtCSQsSummary
Database table name: RtCSQsSummary
The rtcsqssummary table contains real-time statistics about all configured Contact Service Queues in the
system. This table gets updated automatically when real-time snapshot data writing for this table is
enabled through the Unified CCX Administration pages (Tools > Real-time snapshot configuration
menu option). The updating frequency is based on the configured data writing interval.
The RtCSQsSummary table contains the fields shown in Table 1-24.
Related Tables
None.
RtICDStatistics
Database table name: RtICDStatistics
The RtICDStatistics table contains real-time summary statistics about Unified CCX. This table gets
updated automatically when real-time snapshot data writing for this table is enabled through the Unified
CCX Administration pages (Tools > Real-time snapshot configuration menu option.) The updating
frequency is based on the configured data writing interval.
The RtICDStatistics table contains the fields shown in Table 1-25.
Related Tables
None.
Skill
Database table name: Skill
The Unified CCX system creates a new record in the Skill table when a skill is set up in the Unified CCX
Administration.
A Skill record contains information about a skill. One such record exists for each configured skill.
The Skill table contains the fields shown in Table 1-26.
Related Tables
• ProfileIDMapping, page 34 (via profileID)
• ResourceSkillMapping, page 40 (via skillID and profileID)
• SkillGroup, page 48 (via skillID and profileID)
SkillGroup
Database table name: SkillGroup
The Unified CCX system creates a new record in the SkillGroup table when skills are associated with a
CSQ in the Unified CCX Administration.
A SkillGroup record describes each skill that is associated with the CSQ.
The SkillGroup table contains the fields shown in Table 1-27.
Related Tables
• ContactServiceQueue, page 22 (via skillGroupID and profileID)
• ProfileIDMapping, page 34 (via profileID)
• Skill, page 47 (via skillID and profileID)
Supervisor
Database table name: Supervisor
The Supervisor table contains the information about the supervisor.
The Supervisor table contains the fields shown in Table 1-28.
Related Tables
• Resource, page 37 (via resourceLoginID and profileID
• ProfileIDMapping, page 34 (via ProfileID)
• Team, page 50 (managedTeamID maps to teamID, via profileID)
Team
Database table name: Team
The Team table contains information about specific teams.
The fields in the Team table are shown in Table 1-29.
Related Tables
• ProfileIDMapping, page 34 (via ProfileID)
• Resource, page 37 (teamID maps to assignedTeamID and via profileID
• Supervisor, page 49 (teamID maps to managedTeamID and via profileID)
• TeamCSQMapping, page 51 (via teamID and profileID)
TeamCSQMapping
Database table name: TeamCSQMapping
The TeamCSQMapping table shows the relationship between Teams and CSQs; for example, Team 1 is
CSQ3, Team 4 is CSQ10.
The TeamCSQMapping table contains the fields shown in Table 1-30.
Related Tables
• ContactServiceQueue, page 22 (csqID maps to contactServiceQueueID, and via profileID)
• ProfileIDMapping, page 34 (via ProfileID)
• Team, page 50 (via teamID and profileID)
WorkflowTask
Database table name: WorkflowTask
A WorkflowTask record contains information about a task or a subtask that runs on the Unified CCX
system.
The Workflow Task table contains the fields shown in Table 1-31.
Related Tables
• AgentConnectionDetail, page 4 (applicationServerID maps to nodeID)
• ContactCallDetail, page 13 (applicationServerID maps to nodeID)
• ContactQueueDetail, page 19 (applicationServerID maps to nodeID)
• ContactRoutingDetail, page 21 (applicationServerID maps to nodeID)
• MonitoredResourceDetail, page 33 (applicationServerID maps to nodeID)
• RemoteMonitoringDetail, page 35 (applicationServerID maps to nodeID)
EEMActiveEmail
When an email is being processed by an agent, a record for that email is created in the EEMActiveEmail
table. The columns in the table are updated as the agent works on the email. When the email is terminated
(sent, deleted, requeued), the record is deleted.
The EEMActiveEmail table contains one row for each email message being processed by an agent
Database table name: EEMActiveEmail
Related Tables
• EEMEmailStatusDescription, page 57 (via emailStatusFK)
• EEMContactEmailDetail, page 54 (via emailUIDOnMailServer)
EEMContactEmailDetail
When an email message is placed into a CSQ, a record for that email message is created in this table.
When the email is assigned to an agent, the agent name column is updated. When the email is terminated
(sent, deleted, requeued), the finalDisposition columns are updated.
The EEMContactEmailDetail table contains one row for each email message currently in the system.
Database table name: EEMContactEmailDetail
Related Tables
• EEMReasonCodeDescription, page 59 (via receivedReasonFK)
• EEMEmailStatusDescription, page 57 (via finalDispositionTypeFK)
EEMEmailAgentStateDetail
When an agent makes an email-related state change, the state change is recorded in the
EEMEmailAgentStateDetail table. For each state change, there is an "eventStart" and an "eventEnd".
The times for these are recorded in the corresponding eventStartDateTime and eventEndDateTime
columns. Human-readable descriptions of states and reason codes are found in the
EEMReasonCodeDescription and EEMStateDescription tables. Some events (login and logout) have a
zero length duration, as the agent immediately moves to another state.
The EEMEmailAgentStateDetail table contains one row for each Email state change for an agent.
Database table name: EEMEmailAgentStateDetail
Related Tables
• EEMContactEmailDetail, page 54 (via emailUIDOnMailServer)
• EEMReasonCodeDescription, page 59 (via reasonCodeFK)
• EEMStateDescription, page 59 (via stateFK)
EEMEmailStatusDescription
The EEMEmailStatusDescription table contains descriptive text (in English only) for each possible
email status.
Database table name: EEMEmailStatusDescription
EEMQueueAgentDetail
When an email is assigned to an agent, a record is created in the EEMQueueAgentDetail table. It
associates the agent and the email message that the agent is working on. The agent can enter a processing
state, and later exit the processing state. The elapsed time the agent is in the processing state, is
accumulated in the inProcessTimeSeconds column. When the email is terminated (sent, deleted,
requeued), the "endDateTime", endTypeFK, and wrapupData columns are updated.
The human-readable descriptions of the receivedReasonFK and endTypeFK columns are found in
EEMReasonCodeDescription and EEMEmailStatusDescription tables.
The EEMQueueAgentDetail table associates an agent and an email message and contains one record for
each email message an agent is working on.
Database table name: EEMQueueAgentDetail
Related Tables
• EEMContactEmailDetail, page 54 (via ContactEmailDetailFK)
• EEMReasonCodeDescription, page 59 (via receivedReasonFK)
• EEMEmailStatusDescription, page 57 (via endTypeFK)
EEMReasonCodeDescription
The EEMReasonCodeDescription table contains descriptive text (in English only) for each possible
reason code.
Database table name: EEMReasonCodeDescription
EEMStateDescription
The EEMStateDescription table contains descriptive text (in English only) for each e-mail state.
Database table name: EEMStateDescription
EEMTablesVersion
The EEMTablesVersion table contains a single row indicating the version of the EEM database tables.
This is used when upgrading from a previous version.
Database table name: EEMTablesVersion
in CrsApplication table 25
A
applicationName field
accountNumber field in ContactCallDetail table 16
in ContactCallDetail table 17 in CrsApplication table 25
in DialingList table 30 in CrsTrigger table 28
active field applicationServerID field
in AreaCode table 8 in WorkflowTask table 52
in CampaignCSQMap table 12 applicationTaskID field
in Campaign table 10, 13 in ContactCallDetail table 16
in ContactServiceQueue table 23 applicationType field
in CrsApplication table 26 in CrsApplication table 25
in CrsGroup table 27 areaCode field
in CrsTrigger table 29 in AreaCode table 8
in DialingList table 33 AreaCode table 8
in ResourceGroup table 40 assignedTeamID field
in ResourceSkillMapping table 41 in Resource table 39
in Resource table 38 autoAvail field
in RmonUser table 43 in Resource table 38
in SkillGroup table 49 autoWork field
in Skill table 48 in ContactServiceQueue table 23
in Supervisor table 50 availableAgents field
in TeamCSQMapping table 52 in RtCSQsSummary table 44
in Team table 51 in RtICDStatistics table 46
AgentConnectionDetail table 4 avgTalkDuration field
agentID field in RtCSQsSummary table 44
in AgentStateDetail table 7 in RtICDStatistics table 46
AgentStateDetail table 7 avgWaitDuration field
ansMachineRetry field in RtCSQsSummary table 44
in Campaign table 10 in RtICDStatistics table 46
applicationEnabled field
in CrsApplication table 25
applicationID field
B
in ContactCallDetail table 16 badCallTag field
F I
in CrsApplication table 25
R
in CrsTrigger table 28
in DialingList table 30 reasonCode field
in MonitoredResourceDetail table 34 in AgentStateDetail table 7
in ProfileIDMapping table 26, 35 record, database 1
in RemoteMonitoringDetail table 37 recordID field
in ResourceGroup table 40 in AreaCode table 8
in ResourceSkillMapping table 41 in CampaignCSQMap table 11, 12
in Resource table 38 in Campaign table 9
in RmonCSQConfig table 42 in ContactServiceQueue table 23
in RmonResConfig table 42 in CrsApplication table 25
in RmonUser table 43 in CrsGroup table 26
in SkillGroup table 48 in CrsTrigger table 28
in Skill table 47 in DialingList table 30
in Supervisor table 49 in Supervisor table 49
in TeamCSQMapping table 51 in TeamCSQMapping table 51
in Team table 50 redirect field
profilename field in ContactCallDetail table 18
in ProfileIDMapping table 35 regionCode field
prompt field in AreaCode table 8
in ContactServiceQueue table 24 remoteLoginID field
in RemoteMonitoringDetail table 36
RemoteMonitoringDetail table 35
Q reservedAgents field
qIndex field in RtCSQsSummary table 45
in AgentConnectionDetail table 5 in RtICDStatistics table 46
in ContactQueueDetail table 20 resourceFirstName field
in ContactRoutingDetail table 21 in Resource table 39
queueAlgorithm field resourceGroupID field
in ContactServiceQueue table 23 in ContactServiceQueue table 23
queueOrder field in ResourceGroup table 40
in ContactQueueDetail table 20 in Resource table 38
queueTime field resourceGroupName field
in ContactQueueDetail table 20 in ResourceGroup table 40
queueTime field, in ContactRoutingDetail table 22 ResourceGroup table 39
resourceID field
in AgentConnectionDetail table 5
in Resource table 38
resourceLastName field
U
T
unavailableAgents field
talkingAgents field in RtCSQsSummary table 44
in RtCSQsSummary table 45 in RtICDStatistics table 46
in RtICDStatistics table 46
talkTime field
V
in AgentConnectionDetail table 5
targetID field version field
in ContactQueueDetail table 20 in CrsApplication table 25
targetType field in CrsGroup table 27
in ContactQueueDetail table 20 in CrsTrigger table 28
taskID field
in WorkflowTask table 52
TeamCSQMapping table 51
W
teamID field WorkflowTask table 52
in TeamCSQMapping table 51 workingAgents field
in Team table 50 in RtCSQsSummary table 45
teamName field in RtICDStatistics table 46
in Team table 50 workTime field
Team table 50 in AgentConnectionDetail table 6
totalCalls field wrapUpTime field
in RtCSQsSummary table 44 in ContactServiceQueue table 24
in RtICDStatistics table 46
totalCSQs field
in RtICDStatistics table 46
transfer field
in ContactCallDetail table 18
triggerEnabled field
in CrsTrigger table 28
triggerLocale field
in CrsTrigger table 29
triggerName field
in CrsTrigger table 28