| F60008 |
| SAS Digital Marketing 5.41 |
| Issue(s) Addressed: | Introduced: |
| 43869 | The database user name and password in the SAS® Digital Marketing web.xml file are in plaintext |
F60001 |
| 44663 | SAS® Digital Marketing fails to write e-mail opt out requests to the opt-out table |
F60001 |
| 44665 | SAS® Digital Marketing does not render dynamic broadcast content correctly when the underlying field contains HTML scripting |
F60001 |
| 44199 | An ASP broadcast fails to deliver if you view the properties of the broadcast in SAS® Digital Marketing |
F60002 |
| 45041 | SAS® Digital Marketing does not increment the ID number when you add entries to an existing category in the Reply Manager |
F60002 |
| 45247 | SAS® Digital Marketing e-mail content might not be delivered to the recipients when you use a style in the body tag of your html |
F60002 |
| 45248 | SAS® Digital Marketing broadcasts of text only e-mails return the error "java.rmi.RemoteException... (The system cannot find the file specified)" |
F60002 |
| 45287 | Editing a previously created SAS® Digital Marketing broadcast in TinyMCE causes all links in the broadcast HTML to be tracked |
F60002 |
| 45433 | The SAS® Digital Marketing ebtool interface causes a NullPointerException in SAS® Digital Marketing broadcasts that do not contain a tracked link |
F60002 |
| 45464 | SAS® Digital Marketing truncates the CI_RESPONSE_HISTORY Subject ID in the SAS® Customer Intelligence Reporting Common Data Model to 32 characters |
F60002 |
| 45467 | SAS® Digital Marketing Web Studio does not enable you to return to a previous folder when you are browsing folders |
F60002 |
| 45472 | The folder view in SAS® Digital Marketing Web Studio incorrectly shows broadcasts within the folder rather than showing the properties of the folder |
F60002 |
| 45473 | SAS® Digital Marketing broadcasts might not send e-mails to all intended recipients |
F60002 |
| 45505 | The values of included variables might be missing in the Web View version of e-mails that are generated by SAS® Digital Marketing |
F60002 |
| 45550 | SAS® Digital Marketing e-mail content might be displayed incorrectly |
F60002 |
| 45774 | ALERT - When SAS® Digital Marketing uses RMI CustomSocketFactory port connectivity, the SAS® Digital Marketing client and server cannot connect to each other |
F60002 |
| 46051 | SAS® Digital Marketing might perform slowly when rendering e-mail as a web page |
F60003 |
| 46259 | SAS® Digital Marketing might fail to update the SAS® Customer Intelligence Response and Contact History when broadcast properties are amended |
F60003 |
| 46451 | SAS® Digital Marketing ignores the -Djava.rmi.server.hostname parameter during start-up |
F60003 |
| 46716 | E-mail recipients might receive a "bad link" error message when they click the Web link in a broadcast e-mail from SAS® Digital Marketing. |
F60003 |
| 46718 | In SAS® Digital Marketing, the ASPRequest column in the SDMAudit file does not hold the complete ASP request information |
F60003 |
| 46720 | The ASPRequest field in the SDMAudit file does not hold any information to allow re-sending of messages |
F60003 |
| 46970 | An XSL error occurs when you save a SAS® Digital Marketing Studio broadcast |
F60003 |
| 46977 | E-mail broadcasts imported into SAS® Digital Marketing do not render correctly |
F60003 |
| 46998 | Personalized variable information might not be displayed in e-mails that are created in SAS® Digital Marketing |
F60003 |
| 47003 | SAS® Digital Marketing might stop processing replies |
F60003 |
| 46657 | "No statements may be issued when any streaming result sets are open ..." occurs when using SAS® Digital Marketing JDBC Table Viewer to add a row |
F60004 |
| 47015 | SAS® Digital Marketing click events might not be recorded in the Digital Marketing response table |
F60004 |
| 47138 | In SAS® Digital Marketing, tracked links with a variable might fail to resolve correctly if they are generated using XSL |
F60004 |
| 47241 | The SAS® Digital Marketing response table or opt-out table might lose information |
F60004 |
| 41478 | Tracked links do not redirect correctly if the tracking variable contains an ampersand and an Internal Server Error occurs |
F60005 |
| 47934 | Security improvements for SAS® Digital Marketing |
F60005 |
| 48680 | Hard bounces are not always recorded as a failed contact in the contact history |
F60005 |
| 49264 | Throttled e-mails fail to be delivered when SMTP server authentication is not used in SAS® Digital Marketing |
F60006 |
| 46918 | Throttled SAS® Digital Marketing messages are processed very slowly |
F60007 |
| 48204 | Using the EBTOOL command in SAS® Digital Marketing to duplicate or replicate an ASP type broadcast fails to generate correct XML and XSL files |
F60007 |
| 48637 | ALERT - An SMS message that contains Arabic type text cannot be sent from SAS® Digital Marketing |
F60007 |
| 48771 | E-mail replies in the SAS® Digital Marketing Reply Manager lose the correct content when the replies are sorted |
F60007 |
| 49202 | The opt-out table is not being updated with the e-mail addresses from hard bounce notifications |
F60007 |
| 49265 | Entries for hard bounces in the SAS® Digital Marketing replies table might appear multiple times and other types of replies might be missing |
F60007 |
| 49742 | HTML code that is imported into a SAS® Digital Marketing broadcast might become corrupted |
F60007 |
| 49743 | Problems occur when you activate verbose logging on the e-mail server that is used by SAS® Digital Marketing to handle hard bounces |
F60007 |
| 49762 | Authentication fails if you log on to SAS® Digital Marketing Studio using the option to prompt for the password |
F60007 |
| 45751 | SAS® Digital Marketing continues to check for responses to broadcasts after the maximum number of days set in the CIModelPeriod is exceeded |
F60008 |
| 47832 | The use of the SMS column in the SAS® Digital Marketing ASP recipient and phone number variables are not allowed |
F60008 |
| 49036 | Enabling an additional debugging option when you have problems sending e-mails or SMS messages in SAS® Digital Marketing |
F60008 |
| 49079 | The SAS® Digital Marketing Server stops responding and might close with a "no such object in table" error message |
F60008 |
| 49892 | SAS® Digital Marketing preview broadcasts fail to resolve links |
F60008 |
| 49946 | SAS® Digital Marketing replies that are held in a Teradata database fail to update the Common Data Model Response and Contact History tables |
F60008 |
| 50020 | SAS® Digital Marketing e-mails received with tracked variables might not be able to resolve the link if there is a port reference in the URL |
F60008 |
| 50444 | SAS® Digital Marketing broadcasts fail to complete, resulting in the system becoming unresponsive and a server reboot being necessary |
F60008 |
| 50612 | The SAS® Digital Marketing opt-out table is vulnerable to malicious corruption |
F60008 |
| NOTE: JBoss 5.1 is supported but requires manual updates, see SAS Note 50888 |
|
| D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
General Information about Hot Fixes