SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 40244: You cannot schedule a second Communication node after the first Communication node executes in SAS® Customer Intelligence Studio 5.1

DetailsHotfixAboutRate It

If you create a campaign in SAS Customer Intelligence Studio that has multiple Communication nodes (in the same flow and with associated Response nodes), after the first Communication node executes, the second Communication node is set to Not Ready. As a result, you cannot execute the second Communication node.

For example, consider this flow: SelectNode ► Cell Node ► Communication Node 1 ► Response Node ► Cell Node ► Communication Node 2.

Given the explanation above, if you schedule Communication Node 1 to run and it runs successfully, you cannot subsequently schedule Communication Node 2 to run.

As a workaround, double-click the Response node from within SAS Customer Intelligence Studio, and then click OK in the Response node. This action sets the second Communication node so that it has a status of Ready, and then you can schedule the node.

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



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Customer Intelligence StudioMicrosoft Windows 2000 Advanced Server5.19.1 TS1M3 SP4
Microsoft Windows 2000 Datacenter Server5.19.1 TS1M3 SP4
Microsoft Windows 2000 Server5.19.1 TS1M3 SP4
Microsoft Windows 2000 Professional5.19.1 TS1M3 SP4
Microsoft Windows NT Workstation5.19.1 TS1M3 SP4
Microsoft Windows Server 2003 Datacenter Edition5.15.3_M19.1 TS1M3 SP49.2 TS2M0
Microsoft Windows Server 2003 Enterprise Edition5.15.3_M19.1 TS1M3 SP49.2 TS2M0
Microsoft Windows Server 2003 Standard Edition5.15.3_M19.1 TS1M3 SP49.2 TS2M0
Microsoft Windows XP Professional5.15.3_M19.1 TS1M3 SP49.2 TS2M0
Windows Vista5.15.3_M19.1 TS1M3 SP49.2 TS2M0
Windows Vista for x645.15.3_M19.1 TS1M3 SP49.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.