Problem Note 51327: Updating a SAS® Real-Time Decision Manager treatment clears its mapped custom details in decision campaign Reply nodes without warning
SAS Real-Time Decision Manager campaigns often use treatments that have dynamic custom details. These custom details are mapped in the Reply node of the treatment campaign. If you update a treatment that is used in a treatment campaign, then you are asked to accept treatment changes when you edit the associated treatment campaign. When you accept these changes, the mapped dynamic variables are cleared in the campaign's Reply node without any notification. In order to use the dynamic variables after this update, you must remap the variables.
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 | Microsoft® Windows® for 64-Bit Itanium-based Systems | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft Windows XP 64-bit Edition | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft® Windows® for x64 | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Standard Edition | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft Windows Server 2003 for x64 | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft Windows Server 2008 R2 | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft Windows Server 2008 for x64 | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Microsoft Windows XP Professional | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Windows Vista | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Windows Vista for x64 | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| 64-bit Enabled AIX | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| 64-bit Enabled Solaris | 5.4 | 5.4_M1 | | 9.2 TS2M0 |
| Linux for x64 | 5.4 | 5.4_M1 | | 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: | 2013-10-14 10:18:56 |
| Date Created: | 2013-10-11 09:51:43 |
