Yes, we’re already mapping into CONTACT_ATTEMPT_FACT,
For example, we are storing the output of 6 questions we ask customers, (Q1_Outcome, Q2_Outcome… Q6_Outcome)
These are written back to the Calling List into Fields - Q1_Outcome, Q2_Outcome, etc.
The configuration for Q1_Outcome is:
[default]
icon_attribute=1
send_attribute=Q1_Outcome
[gim-etl-mapping]
column-name=RECORD_FIELD_1
table-name=CONTACT_ATTEMPT_FACT
[interaction-workspace]
display=false
And Q2_Outcome… Q6_Outcome are all similar, except with different values for send_attribute, and using RECORD_FIELD_2 - 6 in CONTACT_ATTEMPT_FACT.
I have created some additional Fields - Q7_Outcome… Q15_Outcome, and I have updated the Agent Script and Calling List in order to populate these on the completion of the call.
RECORD_FIELD_1 through to 10 are “numeric” (specifically Precision 14, Scale 4) in the database, 11-30 are “int” and 31-40 are varchar(255).
Ideally I want to store the results of Q7_Outcome… Q15_Outcome in the same field type (numeric) as we are already using for 1-6, but there is already not enough numeric fields available in CONTACT_ATTEMPT_FACT.
And we are also using a lot of the other columns in CONTACT_ATTEMPT_FACT - so how can I add extras?
RECORD_FIELD_GROUP_1 is also a different data type (varchar(255) and is also heavily used, and RECORD_FIELD_GROUP_2 likewise.
(Yes, we capture a lot of OCS reporting data, with multiple campaigns and lots of reporting…)