Problem Note 43029: After you close a campaign diagram in SAS® Customer Intelligence Studio, the connections from a cell to a campaign group disappear
When you save and close a campaign that has multiple connections in SAS Customer Intelligence Studio, the connections between the nodes might disappear.
Consider the following example: You create a campaign with a group of nodes that consists of multiple Select nodes that are connected to multiple Cell nodes. Then, you connect another Cell node, for example from a Split node in the group. When you expand the group, the connections are made from the Cell node to each of the Select nodes. Then you save the campaign and close it, but you do not exit SAS Customer Intelligence Studio.
When you reopen that campaign, the connection between the Cell node and the group is lost, but there is nothing in the log that indicates a problem.
A similar issue can occur when you connect the group to a Communication node. Not all of the Cell nodes are connected to the Communication node. A connection line might not be connected to a cell.
To work around this problem, perform the following steps:
- Expand the group and connect from the Cell node to each of the Select nodes individually.
- Collapse the group.
- Save and close the campaign.
Click 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 Studio | Microsoft Windows XP Professional | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 for x64 | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2008 | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 for x64 | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Standard Edition | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Datacenter Edition | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft® Windows® for x64 | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows Vista for x64 | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows Vista | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Ultimate x64 | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Ultimate 32 bit | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Professional x64 | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Professional 32 bit | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Home Premium x64 | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Home Premium 32 bit | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Enterprise x64 | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Windows 7 Enterprise 32 bit | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
Microsoft Windows Server 2003 Enterprise Edition | 5.4_M1 | 5.41 | 9.2 TS2M3 | 9.3 TS1M1 |
*
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: | medium |
Date Modified: | 2012-01-04 10:21:36 |
Date Created: | 2011-04-21 14:52:47 |