Problem Note 60350: Request variable values in a Subdiagram node are reset after the identifier in the Event definition is changed
If your decision campaign includes more than one Subdiagram node, you might find that the request variable values in some of the subdiagrams change unexpectedly under circumstances similar to the following:
- A decision campaign called Main Diagram includes two Subdiagram nodes called Sub1 and Sub2. Both Sub1 and Sub2 reference the same subdiagram called Subdiagram A.
- Identifiers are assigned to one or more of the request variables in the Event definition for the Subdiagram Start node.
- The request variables in the Subdiagram nodes are updated with different values (for example, a value of 10 in the Sub1 Subdiagram node and a value of 20 in the Sub2 Subdiagram node).
- An identifier in the Event definition is then changed and the Event definition is saved.
- When you open Main Diagram again, the request variables in both Subdiagram nodes contain the same value: 10.
To work around this problem, manually change the request variable values in the Subdiagram nodes back to the original values.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Real-Time Decision Manager | Solaris for x64 | 6.4 | | 9.4 TS1M2 | |
Linux for x64 | 6.4 | | 9.4 TS1M2 | |
HP-UX IPF | 6.4 | | 9.4 TS1M2 | |
64-bit Enabled Solaris | 6.4 | | 9.4 TS1M2 | |
64-bit Enabled AIX | 6.4 | | 9.4 TS1M2 | |
Windows 7 Ultimate x64 | 6.4 | | 9.4 TS1M2 | |
Windows 7 Ultimate 32 bit | 6.4 | | 9.4 TS1M2 | |
Windows 7 Professional x64 | 6.4 | | 9.4 TS1M2 | |
Windows 7 Professional 32 bit | 6.4 | | 9.4 TS1M2 | |
Windows 7 Home Premium x64 | 6.4 | | 9.4 TS1M2 | |
Windows 7 Home Premium 32 bit | 6.4 | | 9.4 TS1M2 | |
Windows 7 Enterprise x64 | 6.4 | | 9.4 TS1M2 | |
Windows 7 Enterprise 32 bit | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2012 Std | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2012 R2 Std | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2012 R2 Datacenter | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2012 Datacenter | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2008 for x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2008 R2 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows Server 2008 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 10 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8.1 Pro x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8.1 Pro 32-bit | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8.1 Enterprise x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8.1 Enterprise 32-bit | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8 Pro x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8 Pro 32-bit | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8 Enterprise x64 | 6.4 | | 9.4 TS1M2 | |
Microsoft Windows 8 Enterprise 32-bit | 6.4 | | 9.4 TS1M2 | |
Microsoft® Windows® for x64 | 6.4 | | 9.4 TS1M2 | |
*
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: | 2017-06-02 10:05:36 |
Date Created: | 2017-04-25 11:15:38 |