COMM_TRACE_HX
Description:
The history of a communication trace.

Primary Key
Column Name Ordinal Position
COMM_TRACE_ID 1
CONTACT_DATE_REAL 2
LINE 3

Column Information
Name Type Discontinued?
1 COMM_TRACE_ID NUMERIC No
The unique identifier (.1 item) for the outreach record.
2 CONTACT_DATE_REAL FLOAT No
A unique contact date in decimal format. The integer portion of the number indicates the date of contact. The digits after the decimal distinguish different contacts on the same date and are unique for each contact on that date. For example, .00 is the first/only contact, .01 is the second contact, etc.
3 LINE INTEGER No
The line number for the information associated with this contact. Multiple pieces of information can be associated with this contact.
4 COMM_ACTION_UTC_DTTM DATETIME (UTC) No
Table of audit events logged against a trace. This item stores the UTC of the event.
5 COMM_ACTION_C_NAME VARCHAR No
Table of audit events logged against a trace. This item stores the action taken on this trace. This can be from the system, or user intervention.
May contain organization-specific values: No
Category Entries:
Create
Sidetrack
Re-Queue
Defer
To Interconnect
To Cloud
Sent
Receive
Update
Cancel
Expire
Text / Close 2Way
Auto-Invite / Invite Queue
Auto-Invite / Hold Tank
Auto-Invite / Send Queue
Auto-Consent / Send Queue
MO / Processed
MO / Processing Failed
Agent / Chat Ended
Agent / Processing Failed
Voice / Error Retry
6 COMM_ACTION_STATUS_C_NAME VARCHAR No
Table of audit events logged against a trace. This item stores status of the trace at the time the audit happened. NOT the status that resulted.
May contain organization-specific values: No
Category Entries:
Created
Queued
Sidetracked
Session Active
To Interconnect
To Cloud
Pending
Sent
Delivered
Canceled
Expired
Failed
Unknown
Auto-Invite Tank
Auto-Invite Queue
Ended
Multiple Statuses
Temporary Failure - Waiting for Resolution
Temporary Failure - No Resolution
Voice Transient Error
ECS Not In Use
7 COMM_ACTION_COMMENT VARCHAR No
Table of audit events logged against a trace. This item stores comments about the event. Initial use case was to store the true status string from cloud since it may change with vendors / cloud changes where cache may not have a chance to update in time.