In SAS® Customer Intelligence Studio, you can enable the option Use the most current data when referenced by a link in the source campaign, which contains the linkable Cell node.
The target campaign that contains the Link node re-executes the source campaign under either of these two circumstances:
- when the entire target campaign is executed, either by clicking Execute now or when the execution is scheduled via the MAlauncher command
- when a communication is executed and the target campaign has the option Use the most current data when executing communications enabled
Just updating the counts on a Communication node or any other node inside the target campaign does not re-execute the source campaign with the linkable Cell node.
Even if you clear counts and then update counts in the target campaign, the source campaign does not re-execute.
This behavior is designed to increase performance if results from the most current data are not critical during campaign design.
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:
-Dcom.sas.ci.alwaysrunlinknode=true
This new argument gives you the option to force the source campaign to re-execute all nodes.
Note: If you are using SAS® Marketing Optimization campaign groups, you need to enable this option in order to receive the most current results.
- For Microsoft Windows operating environments (in which the servers are started as Windows services):
Navigate to the SAS-configuration-directory\Lev1\Web\WebAppServer\SASServer6_1\conf directory and add the new argument to the wrapper.conf file, as shown below:
wrapper.java.additional.XX=-Dcom.sas.ci.alwaysrunlinknode=true
In this argument, XX represents the next number in the sequence that already exists in the file. Modify XX to be the next number in that sequence.
- For Linux or other UNIX operating environments:
Add the option to setenv.sh file, as shown below:
JAVA_OPTS="$JAVA_OPTS -Dcom.sas.ci.alwaysrunlinknode=true"
The setenv.sh file is typically located in the SAS-configuration-directory/Lev1/Web/WebAppServer/SASServer6_1/bin directory.
After you add the argument, restart the middle tier so that the setting can take effect.
Operating System and Release Information
SAS System | SAS Customer Intelligence Core Mid-Tier | Microsoft® Windows® for x64 | 6.5 | | | |
64-bit Enabled AIX | 6.5 | | | |
64-bit Enabled Solaris | 6.5 | | | |
HP-UX IPF | 6.5 | | | |
Linux for x64 | 6.5 | | | |
Solaris for x64 | 6.5 | | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.