Problem Note 34332: Contact History for the last occurrence in a recurring campaign might be overwritten if the number of occurrences is changed by the Administrator
SAS® Customer Intelligence creates contact history for each scheduled occurrence of a recurring campaign identified by the occurrence number. However, if the number of expected occurrences defined in SAS Customer Intelligence Studio is less that the number of occurrences actually scheduled, then contact history could be compromised and contact history lost.
This problem occurs when the SAS Customer Intellegence Studio user requests that a number of occurrences (let us say 5) are required for a recurring campaign. This request is then submitted to the Scheduling Administrator.
The Administrator then decides that more occurrences are, in fact, needed (say 10) and changes the schedule in SAS® Management Console to reflect this before committing the campaign to the scheduler.
The contact history will be updated correctly up to and including (in this example) the fifth occurrence. However, when the sixth or subsequent occurrences are executed, if creating new contact history, the contact history for the 5th occurrence will be overwritten instead.
The original data is lost and the seventh occurrence will overwrite the fifth and sixth, and so on.
In order to avoid this problem, ensure that the schedules in SAS Customer Intelligence Studio and SAS Management Console are kept synchronized.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | SAS Customer Intelligence Core Mid-Tier | Microsoft® Windows® for x64 | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows 2000 Advanced Server | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Standard Edition | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows XP Professional | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Windows Vista | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| 64-bit Enabled AIX | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| 64-bit Enabled Solaris | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| HP-UX IPF | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
*
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.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2009-03-02 16:18:41 |
| Date Created: | 2009-01-02 11:16:20 |
