|
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 |
COMM_CHANNEL_C_NAME |
VARCHAR |
No |
|
|
|
| Communication channel used to send this trace. |
| May contain organization-specific values: No |
| Category Entries: |
| SMS |
| Email |
| Voice |
| MMS |
| Web |
| Push Notification |
| RCS for Business |
|
|
| 4 |
RELATED_CAL_COMM_ID |
VARCHAR |
No |
|
|
|
| Stores a related CAL record associated with a specific trace. |
|
|
| 5 |
COMM_AI_STATUS_C_NAME |
VARCHAR |
No |
|
|
|
| Whether the content was generated using AI. |
| May contain organization-specific values: No |
| Category Entries: |
| None |
| All |
| Some |
|
|
| 6 |
SIBLING_GROUP |
VARCHAR |
No |
|
|
|
| Messages sent at the same time, or messages that are fallback to other channels may all share a sibling grouper value. This is likely one RCH CSN from the group. |
|
|
| 7 |
REPLACED_BY_COMM_TRACE_CSN_ID |
NUMERIC |
No |
|
|
|
| Contains a link to the CSN of the trace contact that this message was replaced by. |
|
|
