SAS Customer Intelligence campaign treatments might contain dynamic treatment user-defined fields (UDF) that are published to the common data model (CDM) when the campaign is executed. 

If the publishing of the dynamic treatment UDF fails for some reason, the campaign execution status (available by selecting Execution ► Tab History) is updated to successful as shown in the example below:

Although the status indicates success, the campaign actually fails.

If the publishing process fails, you might see an error similar to the following in the SASCustIntelCore6.x.log file:

From a data and execution perspective, the campaign has failed, and it rolls back any postings and updates to the CDM. However, the status is still set to successful.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Note: After you apply the hot fix, the following new Java argument is introduced:

This new argument gives you the option to change the default behavior so that the execution status will show a status of failed.

You can add the new argument, as follows:

• In Microsoft Windows operating environments, open the wrapper.conf file, which is available in the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\conf directory. In wrapper.conf, add the argument as shown below:
  wrapper.java.additional.XX=-Dcom.sas.ci.setOccurrenceFailOnDTFail=true

  Note: In the wrapper.java.additional.XX property, XX specifies the next number in the sequence that already exists in the file. Modify XX to be the next number in that sequence.

• Under Linux and other UNIX operating environments, open the setenv.sh file, which is located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer6_1/bin directory. In setenv.sh, add the new argument as shown below: 
  JAVA_OPTS="$JAVA_OPTS =-Dcom.sas.ci.setOccurrenceFailOnDTFail=true"

After you add the arguments to the appropriate file for your operating system, restart the middle tier in order for the settings to take effect.

Operating System and Release Information

A fix for this issue for SAS Marketing Automation 6.5 is available at: