| 51MA10 |
| Issue(s) Addressed : | Introduced: |
| SN-032469 | Business-context objects in the SASŪ Marketing Automation plug-ins for SASŪ Management Console cannot be changed while metadata is being generated | 51MA01 |
| SN-030980 | SASŪ Campaign Studio only allows users to select one value from a code node stored process variable list | 51MA01 |
| SN-019806 | Populating SASŪ Marketing Optimization with input data from SASŪ Marketing Automation generates incorrect Eligible Offers counts | 51MA01 |
| SN-019175 | Incorrect counts might be returned when the multi-select node "Excludecustomers that meet these criteria" check box is selected | 51MA01 |
| SN-019399 | Multiple tasks have the same name error when you schedule or execute campaigns in SASŪMarketing Automation 4.4 or SASŪCustomer Intelligence 5.1 | 51MA01 |
| SN-032465 | An incorrect count might be returned if you use an Or node of type "meets any conditions" to combine multiple And nodes | 51MA01 |
| SN-030967 | Unable to delete a link from a SASŪ Marketing Automation campaign user-defined field | 51MA01 |
| SN-032467 | An error occurs when you update counts in a SASŪ Marketing Automation Or node and the first upstream Select node has a zero count | 51MA01 |
| SN-016310 | Select node counts reset after executing a subsequent node | 51MA01 |
| SN-030566 | Counts are not being returned for text fields that contain blank values | 51MA01 |
| SN-030443 | Dates display incorrectly in the SASŪ Campaign Studio Communication Gantt chart if more than 50 occurrences are scheduled | 51MA01 |
| SN-030989 | A zero count is returned after manually changing the values in a multi-select node | 51MA01 |
| SN-032466 | Items that have been selected in SASŪ Campaign Studio cannot be deleted if the underlying information map has changed | 51MA01 |
| SN-032554 | Only one response is reported when multiple treatments share the same response code | 51MA01 |
| SN-030973 | Refining an export on an and node where a preceding select is using wildcards might result in a zero count | 51MA01 |
| SN-030968 | Selection criteria might disappear after you change the rule in a SASŪ Campaign Studio select node | 51MA01 |
| SN-030991 | Disk space is being used up because scheduled campaign and diagram exports do not always delete their underlying temporary tables in MATABLES | 51MA01 |
| SN-032460 | An error occurs if you use SASŪ Marketing Automation Integration Utilities to import a campaign or diagram | 51MA01 |
| SN-030990 | SASŪ Campaign Studio encountered a problem error when using an or node set to "Meets any conditions defined by input node" | 51MA01 |
| SN-030972 | The SASŪ Campaign Studio refine functionality might return incorrect counts when used on an and node | 51MA01 |
| SN-030969 | "Error executing query. The and node, or another node upstream from it, has failed to execute successfully" | 51MA01 |
| SN-030986 | SASŪ Campaign Web Studio allows the Offer Group and Offer Sub group fields to have the same value | 51MA01 |
| SN-030985 | "ERROR 20 Unable to log onto application server" error occurs when a scheduled campaign or diagram is launched | 51MA01 |
| SN-032468 | SASŪ Campaign Studio diagram nodes are marked incorrectly as Ready when underlying processes fail | 51MA01 |
| SN-032458 | An error occurs in SASŪ Marketing Automation if the name of a field that is being exported is exactly 32 characters long | 51MA01 |
| SN-032555 | SASŪ Digital Marketing Response Codes are not available in SASŪ Customer Intelligence Studio when using Response Channel Codes | 51MA01 |
| SN-033176 | When using Select nodes to create an implied AND, SAS® Marketing Automation might be forced into a infinite loop | 51MA02 |
| SN-033179 | Running concurrent SAS® Marketing Automation campaigns can cause Java Messaging Service errors | 51MA02 |
| SN-033057 | The Treatments tab is missing from the Business Context Properties window | 51MA02 |
| SN-030988 | SASŪ Campaign Studio select node calculated-data items appear twice after using the "save as" function | 51MA02 |
| SN-032738 | Changes to calculated data items in a copy of a campaign cause unexpected changes to the original campaign, or varInfold is not found error | 51MA02 |
| SN-033183 | SAS® Marketing Automation diagrams or campaigns might fail if they contain links with multiple outputs | 51MA02 |
| SN-032492 | SASŪ Marketing Automation campaigns might fail when multiple campaigns are run together and are deployed against IBM Websphere | 51MA02 |
| SN-032429 | A long delay occurs between when you submit a SASŪ Marketing Automation campaign or diagram for execution and the start of activity on the database | 51MA02 |
| SN-032732 | Links in user defined fields are missing from Common Data Model | 51MA02 |
| SN-032728 | Records are missing from the common data model | 51MA02 |
| SN-032428 | Performance issues occur when you work with large diagrams in SASŪ Campaign Studio | 51MA02 |
| SN-033046 | Select node remains in state "Not Ready" | 51MA02 |
| SN-032246 | A scheduled SASŪ Marketing Automation campaign never completes | 51MA02 |
| SN-032736 | Select node counts remain when an upstream node is added, which should cause them to be reset to "ready to update counts" | 51MA02 |
| SN-033047 | Limit node shows 'Not Ready' | 51MA02 |
| SN-033175 | The Treatments tab in the SASŪ Customer Intelligence Business Context plug-in for SASŪ Management Console might not be available | 51MA02 |
| SN-032735 | URL or link address is missing from Common Data Model | 51MA02 |
| SN-032733 | User defined fields are missing from Common Data Model when copying a campaign | 51MA02 |
| SN-033178 | SASŪ Real-Time Decision Manager general I/O activities are unable to read, but can update and modify | 51MA02 |
| SN-033048 | An error occurs when a Cell code contains a hyphen(â) or a dash (â) | 51MA02 |
| SN-033181 | Some fields in the SAS® Customer Intelligence common data model might not be populated | 51MA02 |
| SN-033182 | ALERT - Executing a communication in SAS® Marketing Automation clears the value of the Campaign folder in the Campaign Table of the Common Data Model | 51MA02 |
| SN-033567 | Removing the limit criteria from a SASŪ Customer Intelligence Prioritize node causes an error | 51MA03 |
| SN-033566 | Diagrams in SASŪ Customer Intelligence Studio take a long time to open | 51MA03 |
| SN-033857 | Communication codes might not be unique when you use the âSave Asâ feature to create a new campaign | 51MA04 |
| SN-034329 | The Common Data Model in SAS® Customer Intelligence does not contain communication budget information | 51MA05 |
| SN-032710 | SASŪ Campaign Web Studio user-defined field list selections are not reflected when reviewing the campaign or communication in SAS Campaign Studio | 51MA05 |
| SN-034340 | Communication estimated-response rates are not being reflected in the SASŪ Customer Intelligence Reporting Common Data Model | 51MA05 |
| SN-018904 | Counts might be incorrect if a diagram contains a map node with an underlying left join that is defined between the tables in the information map | 51MA05 |
| SN-032713 | Cannot change shared user permissions once a campaign has been saved | 51MA05 |
| SN-036366 | SASŪ Customer Intelligence Response and Contact History performance improvements | 51MA05 |
| SN-034417 | The Summary procedure and SQL methods of metadata generation return different counts | 51MA05 |
| SN-034333 | Incorrect counts are returned when priorities are changed in a split node | 51MA05 |
| SN-034419 | An error occurs and all other fields in the dialog box are blanked out when editing the treatment field manually in a Communication node | 51MA05 |
| SN-034515 | Cells that are created by a Prioritize or Split node are not distributed correctly on the diagram | 51MA05 |
| SN-034342 | An incorrect count is returned when updating counts on a Select node referencing an interval item | 51MA05 |
| SN-032488 | SASŪ Marketing Automation campaigns fail and an out-of-memory error occurs when you execute many complex campaigns in a 24-hour period | 51MA05 |
| SN-034327 | Contact History is not mapped for this subjectID error when updating contact history | 51MA05 |
| SN-034492 | Today's date is not exported correctly when rows are appended to an Oracle table | 51MA05 |
| SN-034338 | Campaigns created from campaign templates that were migrated from SASŪ Marketing Automation 4.4 cannot be approved as the approval link is not active | 51MA05 |
| SN-034335 | Missing MATABLES file error occurs when combining the output from response nodes to a select node | 51MA05 |
| SN-034339 | Scroll bars are missing from the diagram tool parameter dialog box when the underlying stored process contains many input fields | 51MA05 |
| SN-034331 | Historical user-defined field contents are overwritten in the SAS® Customer Intelligence Common Data Model when a campaign is manually published | 51MA05 |
| SN-034341 | A SASŪ Customer Intelligence campaign export might fail with an error when appending to or replacing an Oracle table | 51MA05 |
| SN-034337 | SAS® Customer Intelligence fails to update contact history when using bulkload against a Teradata database | 51MA05 |
| SN-034330 | Netezza Data Definition Language (DDL) scripts are not included with SAS® Customer Intelligence | 51MA05 |
| SN-034334 | An error occurs when creating an Audit Log from a diagram that contains a split node using the "values from a data item" split criteria | 51MA05 |
| SN-034336 | SAS Customer Intelligence Studio might be slow to load complex diagrams that contain communications or exports using the refine functionality | 51MA05 |
| SN-034416 | Incorrect counts are returned in a split node cell when splitting on date values | 51MA05 |
| SN-034516 | An Exception error occurs when attempting to open or create a Business Context | 51MA05 |
| SN-034332 | Contact History for the last occurrence in a recurring campaign might be overwritten if the number of occurrences is changed by the Administrator | 51MA05 |
| SN-034420 | Refine criteria are not being applied when implicit or explicit AND processing feeds directly into an export node | 51MA05 |
| SN-034518 | Cannot produce Audit Documentation when a campaign contains a split node | 51MA05 |
| SN-034328 | Prioritize node Limit functionality does not obey the same random rules as a Limit node | 51MA05 |
| SN-035514 | SASŪ Customer Intelligence is performing slower than anticipated | 51MA06 |
| SN-036425 | A java.lang.NullPointerException occurs when using the Save As function for a scheduled diagram | 51MA07 |
| SN-017377 | Async execution failure when update counts in Campaign Studio | 51MA07 |
| SN-036317 | An error occurs when you close a campaign with a calculated data item without saving the campaign | 51MA07 |
| SN-035245 | It is not possible to change the status of a campaign after the campaign is approved | 51MA07 |
| SN-035160 | An incorrect count is returned when using an export node in SASŪ Customer Intelligence | 51MA07 |
| SN-036407 | Values in the selection lists of a stored process are missing when imported via Integration Utilities | 51MA07 |
| SN-032746 | An exception error occurs when attempting to save a recurring campaign | 51MA07 |
| SN-036596 | Slow performance occurs when viewing a report that is built from a SASŪ Information Map that contains a large number of data items | 51MA07 |
| SN-036424 | Reference to a multi-select node still appears in the macore.log file even after the node is deleted from the diagram | 51MA07 |
| SN-036432 | Link node shows ready-to-update count message instead of an actual count | 51MA07 |
| SN-036312 | Cell and And nodes might not display counts and might generate an error message in the macore log | 51MA07 |
| SN-036362 | SASŪ Customer Intelligence Concurrency performance improvements | 51MA07 |
| SN-036423 | A communication node shows a status of "Ready" rather than showing the actual counts | 51MA07 |
| SN-035237 | Changes that are made to the Schedule Time will not show up in the Schedule Manager in the SASŪ Management Console | 51MA07 |
| SN-034178 | Large SASŪ Marketing Automation diagrams take a long time to redraw after making changes | 51MA07 |
| SN-035246 | An error indicating that MATABLES does not exist occurs when the "Use most current data" check box is selected | 51MA07 |
| SN-035247 | The CAMPAIGN_STATUS field is set to blank when a communication is executed | 51MA07 |
| SN-036211 | Exporting to the same file from multiple export or communication nodes can cause unpredictable results | 51MA07 |
| SN-035244 | Only a description for the link is published in SASŪ Customer Intelligence Studio when specifying a brief type of "link" in the export definition | 51MA07 |
| SN-035239 | You might have a campaign or diagram without an owner if you use an operation system or Regional Setting other than English | 51MA07 |
| SN-036406 | Error "Have run out of response numbers - just generated number 1000(+)" occurs when trying to add a new Response node | 51MA07 |
| SN-036422 | The Integration utility sasmaimport fails when you use it to import a diagram with two split nodes | 51MA07 |
| SN-035242 | Original values for calculated data items are retained in SASŪ Customer Intelligence Studio when you use the Save As function when saving a campaign | 51MA07 |
| SN-035240 | List values for Reporting Data are always separated by a blank space regardless of any changes that are made to settings in SASŪ Management Console | 51MA07 |
| SN-035251 | CELL_PACKAGE_SK is not updated when using the "Save as" function for a campaign with more than one occurrence | 51MA07 |
| SN-036421 | The Integration utility sasmaimport fails when you move SASŪ Real-Time Decision Manager Flows between environments | 51MA07 |
| SN-036310 | Updating the Contact History might produce unpredictable results when you have a communication node exporting into two tables in Oracle | 51MA07 |
| SN-036428 | Concurrent processing of campaign diagrams is sometimes slow | 51MA07 |
| SN-036430 | When performing a Save As on a Campaign in SASŪ Customer Intelligence, the Refine Output check box is cleared | 51MA07 |
| SN-036482 | ALERT - Incorrect results, based on prior counts, might be returned when you execute a campaign for a second or a subsequent time | 51MA08 |
| SN-036486 | ALERT - SASŪ Marketing Automation metadata fails for all tables and generates an error message | 51MA08 |
| SN-036614 | An error occurs when when using the Structured Query Language (SQL) method to generate date histogram metadata from an Oracle database | 51MA09 |
| SN-036615 | Optimized count is cleared in communications and exports when campaigns are executed after applying the 51MA08 hot fix | 51MA09 |
| SN-036995 | ALERT - Contact history and export files do not reflect the most current information when campaigns are re-executed at the campaign level | 51MA10 |
| |
| Windows | Released: Sep 2009 |
| Install Instructions: 51MA10wn.pdf |
| Download: 51MA10 for Windows (file size: 175.9M) |
|
NOTE: This hot fix is compatible with SAS Marketing Optimization hot fix 51mo07. If you are using SAS Marketing Automation in conjunction with SAS Marketing Optimization please ensure that both 51MA10 and 51mo07 are loaded.
|
| |
| HPUX 64bit | Released: Sep 2009 |
| Install Instructions: 51MA10h6.pdf |
| Download: 51MA10 for HPUX 64bit (file size: 175.9M) |
|
NOTE: This hot fix is compatible with SAS Marketing Optimization hot fix 51mo07. If you are using SAS Marketing Automation in conjunction with SAS Marketing Optimization please ensure that both 51MA10 and 51mo07 are loaded.
|
| |
| Solaris 64bit | Released: Sep 2009 |
| Install Instructions: 51MA10s6.pdf |
| Download: 51MA10 for Solaris 64bit (file size: 212.7M) |
|
NOTE: This hot fix is compatible with SAS Marketing Optimization hot fix 51mo07. If you are using SAS Marketing Automation in conjunction with SAS Marketing Optimization please ensure that both 51MA10 and 51mo07 are loaded.
|
| |
| AIX 64bit | Released: Sep 2009 |
| Install Instructions: 51MA10r6.pdf |
| Download: 51MA10 for AIX 64bit (file size: 212.7M) |
|
NOTE: This hot fix is compatible with SAS Marketing Optimization hot fix 51mo07. If you are using SAS Marketing Automation in conjunction with SAS Marketing Optimization please ensure that both 51MA10 and 51mo07 are loaded.
|
| |
| HPUX for Itanium | Released: Sep 2009 |
| Install Instructions: 51MA10hx.pdf |
| Download: 51MA10 for HPUX for Itanium (file size: 212.7M) |
|
NOTE: This hot fix is compatible with SAS Marketing Optimization hot fix 51mo07. If you are using SAS Marketing Automation in conjunction with SAS Marketing Optimization please ensure that both 51MA10 and 51mo07 are loaded.
|
