Writing to contact history
To record contact history, users configure one or more contact processes, such as a Call List or Mail List, then run a flowchart in production (not test) mode. Contact history is written to the tables related to the audience levels that are used in the flowchart.
*
The settings discussed in this topic do not affect eMessage and Interact. Those products use their own ETL processes to extract, transform, and load data into the Campaign contact and response history tables.
The ability to write to contact history depends on the contact history logging options, which administrators can use to either allow or prohibit logging. These global configuration settings affect the contact processes as well as the Track process:
*
The logToHistoryDefault configuration setting determines whether the Log to Contact History Tables option is checked or cleared by default in a contact or Track process box. If logToHistoryDefault is enabled, Log to Contact History Tables is checked by default, meaning contact history updates are allowed.
*
The overrideLogToHistory configuration setting controls whether users with the appropriate permissions can change the Log to Contact History Tables setting when they configure a contact or Track process.
To make all flowchart production runs always write to contact history, enable logToHistoryDefault and disable overrideLogToHistory.
When contact history is logged, offer and treatment history are written as well.
*
If a process is configured to log contact history, but the process runs on a cell with no selected targets, history records are not written.
For more information, see the Campaign User's Guide.
Copyright IBM Corporation 2015. All Rights Reserved.