Campaign | partitions | partition[n] | server | flowchartConfig
Properties in this category specify the behavior of the Campaign Generated Field, whether duplicate cell codes are allowed, and whether the Log to Contact History option defaults to enabled.
allowDuplicateCellcodes
- Description
The allowDuplicateCellcodes property specifies whether the cell codes in the Campaign Snapshot process can have duplicate values.
If the value is FALSE, the Campaign server enforces unique cell codes.
If the value is TRUE, the Campaign server does not enforce unique cell codes.
- Default value
TRUE
- Valid Values
TRUE | FALSE
allowResponseNDaysAfterExpiration
- Description
The allowResponseNDaysAfterExpiration property specifies the maximum number of days after all offer expiration dates that responses can tracked. These late responses can be included in performance reports.
- Default value
90
agfProcessnameOutput
- Description
The agfProcessnameOutput property specifies the output behavior of the Campaign Generated Field (UCGF) in the List, Optimize, Response, and Snapshot processes.
If the value is PREVIOUS, the UCGF contains the process name associated with the incoming cell.
If the value is CURRENT, the UCGF holds the process name of the process in which it is used.
- Default value
PREVIOUS
- Valid Values
PREVIOUS | CURRENT
logToHistoryDefault
- Description
The logToHistoryDefault property specifies whether the Log to Contact History and Tracking Tables option in the Log tab of the Campaign contact processes defaults to enabled.
If the value is TRUE, the option is enabled.
If the value is FALSE, the option is disabled in any newly created contact processes.
- Default value
TRUE
- Valid Values
TRUE | FALSE
overrideLogToHistory
- Description
- This property 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
- Default value
-
TRUE
- Valid Values
-
TRUE | FALSE
defaultBehaviorWhenOutputToFile
- Description
Specifies the behavior for contact processes in Campaign when outputting to a file. This property applies only within the current partition. This default behavior (if set) is only applied for processes when they are newly added to flowcharts; once a process is added to a flowchart, the output behavior can be changed in the process configuration.
- Default value
Replace All Records
- Valid Values
Append to Existing Data
Create New File
Replace All Records
defaultBehaviorWhenOutputToDB
- Description
Specifies the behavior for contact processes in Campaign when outputting to a database table. This property applies only within the current partition. This default behavior (if set) is only applied for processes when they are newly added to flowcharts; once a process is added to a flowchart, the output behavior can be changed in the process configuration.
- Default value
Replace All Records
- Valid Values
Append to Existing Data
Replace All Records
replaceEmbeddedNames
- Description
When replaceEmbeddedNames is TRUE, Campaign replaces user variable and UCGF names embedded in query text with actual values, although these names must be separated by a non-alphanumeric character, such as an underscore (for example, ABC_UserVar.v1 will be substituted but ABCUserVar.v1 will not). Set this property to TRUE for backwards compatibility with Campaign 7.2 and earlier.
When set to FALSE, Campaign replaces only distinct user variable and UCGF names with actual values (in both IBM® EMM and raw SQL expressions). Set this property to FALSE for backwards compatibility with Campaign 7.3 and higher.
- Default value
FALSE
- Valid Values
TRUE | FALSE
legacyMultifieldAudience
- Description
In most cases, you can leave this property set to the default value of FALSE. Campaign v8.5.0.4 and newer name multifield Audience ID fields according to the audience definition, regardless of the source of the fields. When you configure processes to use multifield Audience ID fields, you now see the new Audience ID naming convention for multifield audiences. Already-configured processes in flowcharts created in previous Campaign versions should continue to work. However, if old flowcharts fail because of the change in the naming convention, you can revert Campaign behavior by setting this property toTRUE.
- Default value
FALSE
- Valid Values
TRUE | FALSE