Usage Note 43630: The campaign-group schedule date overwrites a campaign schedule date
If you add a campaign to a campaign group in SAS® Customer Intelligence Studio, the campaign schedule date is not used. Instead, the campaign schedule date is overwritten by the campaign-group schedule date.
Click the Hot Fix tab in this note to access the hot fix for this issue.
After applying the hot fix, you can specify that the campaign schedule date is used by adding the following line to the sasasmaclient.ini file:
javaArgs_9=-Dsas.ci.RetainMemberCampaignSchedules
The sasasmaclient.ini file is located on the client machine.
EXAMPLE
Supposed that your sasasmaclient.ini file is in the following location:
C:\Program Files\SAS\SASCustomerIntelligenceStudio\5.4\sasmaclient.ini
This code uses the campaign schedule date instead of the campaign-group schedule date.
[properties]
MASTERPROP=C:\Program Files\SAS\sassw.config
[default]
startdir=
applogloc=
launchercmd=
JavaArgs_1=-Xms50m
JavaArgs_2=-Xmx1024m
JavaArgs_3=-Djava.system.class.loader=com.sas.app.AppClassLoader
JavaArgs_4=-Dsas.app.class.dirs="C:\Program
Files\SAS\SASCustomerIntelligenceStudio\5.4"
JavaArgs_5=-Dsas.app.class.path=.
JavaArgs_6=-Dsas.ext.config=sas.java.ext.config
JavaArgs_7=-Dsas.app.launch.config=picklist
JavaArgs_8=-Dsas.app.repository.path="\eclipse"
javaArgs_9=-Dsas.ci.RetainMemberCampaignSchedules
Classpath=-cp "\eclipse\plugins\sas.launcher.jar"
MainClass=com.sas.analytics.crm.app.Client
Operating System and Release Information
SAS System | SAS Customer Intelligence Studio | Windows 7 Enterprise 32 bit | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Datacenter Edition | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft® Windows® for x64 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows XP Professional | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 for x64 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 for x64 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Standard Edition | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Enterprise Edition | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Enterprise x64 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Home Premium 32 bit | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Home Premium x64 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Professional 32 bit | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Professional x64 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Ultimate 32 bit | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Ultimate x64 | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows Vista | 5.4 | 6.1 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows Vista for x64 | 5.4 | | 9.2 TS2M3 | |
*
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.
Date Modified: | 2011-09-19 09:09:34 |
Date Created: | 2011-06-30 11:44:22 |