| K78015 for Solaris for x64 |
| SAS Marketing Automation 6.1_M1 |
| Issue(s) Addressed: | Introduced: |
| 50361 | User groups contained within user groups are not visible on the Business Context Properties Users tab or in the Campaign Permissions dialog box |
K78001 |
| 49638 | The SAS® Real-Time Decision Manager utility for publishing promoted activity and model code does not continue after it encounters an error |
K78001 |
| 49641 | The SAS® Real-Time Decision Manager sasciutils script does not load data and web processes for imported decision campaigns |
K78001 |
| 49221 | Temporary tables are not deleted after SAS® Customer Intelligence updates to Contact History, Response History, or Presented Treatment tables |
K78001 |
| 50348 | A Map node returns incorrect counts if the underlying tables are connected with an outer join |
K78001 |
| 50351 | SAS® Customer Intelligence campaigns do not execute |
K78001 |
| 50355 | Communications with percent-based holdouts enabled fail and an exception occurs |
K78001 |
| 50359 | Score columns are missing in optimized campaigns that are imported into SAS® Customer Intelligence 6.1 from earlier releases |
K78001 |
| 50425 | The SAS® Customer Intelligence Migration Utility does not import Multi-Select and Exclude criteria correctly |
K78001 |
| 50426 | An application exception might occur when migrating to SAS® Customer Intelligence Studio 6.1 |
K78001 |
| 50428 | The status of nodes downstream might not change when you change a Process node in SAS® Customer Intelligence Studio 6.1 |
K78001 |
| 50431 | An error occurs when you save two campaigns concurrently in SAS® Customer Intelligence Studio |
K78001 |
| 50550 | The counts for downstream Cell nodes do not clear when you change the priority in a Prioritize node in SAS® Customer Intelligence Studio |
K78001 |
| 50613 | All SAS® Real-Time Decision Manager reply variables are included by default when you create test cases by importing a data set |
K78001 |
| 50615 | Model definitions are not fully migrated when you migrate from SAS® Real-Time Decision Manager 5.41 M1 to SAS® Real-Time Decision Manager 6.1 |
K78001 |
| 50617 | SAS® Customer Intelligence Studio fails to clear previous request variable values when you enter a new test case for SAS® Real-Time Decision Manager |
K78001 |
| 50619 | "XXX does not exist" occurs with concurrent SAS® Real-Time Decision Manager requests in SAS® Customer Intelligence Studio or SAS® Management Console |
K78001 |
| 50620 | SAS® Real-Time Decision Manager campaigns open slowly in SAS® Customer Intelligence Studio |
K78001 |
| 50878 | An error message indicates that the web process does not exist when you open a campaign in SAS® Customer Intelligence Studio 6.1 |
K78001 |
| 50899 | You are unable to log on to SAS® Customer Intelligence Studio 6.1 |
K78001 |
| 50900 | Executing an Export or Process node in SAS® Customer Intelligence Studio 6.1 results in publishing to the common data model |
K78001 |
| 51098 | ALERT - Input data might seem as if it did not migrate successfully after migrating from SAS® Marketing Automation 5.41 to SAS® Marketing Automation 6.1 |
K78001 |
| 51103 | Customer attributes in SAS® Marketing Optimization fail to optimize |
K78001 |
| 51198 | SAS® Real-Time Decision Manager might follow incorrect branch when large numbers are used in branch criteria |
K78001 |
| 51567 | A "server location is already registered for use..." error occurs when you create a new project |
K78001 |
| 50869 | A validation error occurs when you add date fields in SAS® Customer Intelligence 6.1 |
K78002 |
| 51440 | The message "TypeError: Error #1009..." occurs when you modify a schedule in SAS® Customer Intelligence Studio using the German locale |
K78002 |
| 51547 | A validation error occurs when you use the Calendar icon to add a date field in a non-English locale of SAS® Customer Intelligence Studio |
K78002 |
| 51541 | An error occurs when you refresh data for a campaign group in SAS® Customer Intelligence Studio |
K78002 |
| 51519 | The message "ERROR 20 Unable to log onto application server" occurs when a SAS® Customer Intelligence scheduled campaign is launched |
K78002 |
| 51977 | The SAS® Customer Intelligence suite of products does not have the ability to suppress attachments |
K78003 |
| 52007 | ALERT - The product IDs for SAS® Customer Intelligence products are not updated |
K78003 |
| 51966 | Updates to the common data model can fail during the initial start up of the SAS® Customer Intelligence Reporting middle-tier application |
K78003 |
| 51992 | SAS® Real-Time Decision Manager does not always republish when you add new treatments, triggering integrity constraint errors when you run campaigns |
K78003 |
| 51960 | "Data Modify stmt error while attempting to update TREATMENT_CAMPAIGN_SET" occurs when deploying a decision treatment campaign set |
K78003 |
| 51990 | Associations between SAS® Real-Time Decision Manager objects might be lost if you import them using separate SPK files |
K78003 |
| 51986 | Imported SAS® Real-Time Decision Manager campaigns do not find DS2 code for activities and scoring unless you open and resave each model definition |
K78003 |
| 49633 | SAS® Real-Time Decision Manager might not populate the value for a decision campaign's custom details correctly |
K78003 |
| 49634 | SAS® Real-Time Decision Manager returns "Treatment campaign cannot be opened" when you execute an imported campaign that uses a treatment set |
K78003 |
| 49955 | Custom detail values are incorrectly blank or unavailable in SAS® Real-Time Decision Manager campaigns |
K78003 |
| 51014 | Values of a decision campaign's static custom details are not available for use in a treatment or sub-diagram |
K78003 |
| 51637 | ALERT - SAS® Decision Services Monitor fills its temporary space or database, preventing SAS® Customer Intelligence Studio from opening activated campaigns |
K78003 |
| 51805 | SAS® Real-Time Decision Manager campaigns sometimes vary in repeated tests despite the use of identical input |
K78003 |
| 51965 | The error "NullValueEvaluationException" occurs when a treatment campaign returns a standard reply in a decision campaign |
K78003 |
| 51970 | SAS® Real-Time Decision Manager returns "Activity... does not exist" after importing and running a decision campaign and its scoring model |
K78003 |
| 51971 | Changing the variable type of a decision campaign custom detail tag causes the error "identifier is not defined" in SAS® Customer Intelligence Studio |
K78003 |
| 52269 | SAS® Customer Intelligence Studio returns the error "java.lang.StackOverflowError" when you schedule a campaign that has no end date |
K78004 |
| 51498 | SAS® Marketing Automation might fail to delete temporary tables |
K78004 |
| 52380 | In SAS® Customer Intelligence Studio, a new Response Definition might incorrectly use an existing Response Code |
K78004 |
| 52415 | Saving a Communication Definition that contains an Export Definition might fail in SAS® Customer Intelligence Studio |
K78005 |
| 52411 | Opening a newly created business context in SAS® Customer Intelligence Studio might result in a PersistenceException error |
K78006 |
| 52458 | An error occurs after you change SAS® Digital Marketing parameters |
K78006 |
| 52863 | A thread exception occurs when you run the premigration utility (sasciutils -useraction ContentCheck) on a SAS® Customer Intelligence 6.1 installation |
K78006 |
| 52413 | Error messages are not displayed when the copy_files.bat script does not run successfully |
K78006 |
| 53004 | Problems can occur with SAS® Marketing Automation when a space is used as the thousands separator for a numeric value |
K78006 |
| 50622 | Changing the order of parameters in a treatment set event triggers "Event definition _TS_XXXX ...does not exist" when executing a parent campaign |
K78006 |
| 51972 | Changes to text fields in an Export node or the Export section of Communication node do not appear in the export file |
K78006 |
| 52036 | Changes to an export file type within an export definition are not honored in SAS® Customer Intelligence Studio |
K78006 |
| 53290 | Using the "Missing" functionality in the Select node of a SAS® Marketing Automation campaign might generate incorrect results |
K78006 |
| 51110 | sasmalauncher is not able to handle special characters in the Business Context Name |
K78006 |
| 50742 | The error "Transaction ABORTed due to deadlock issue" occurs when you use various SAS® Marketing Automation macros |
K78006 |
| 51337 | One or more nodes incorrectly return a zero count |
K78006 |
| 51536 | The error "Could not serialize - transaction aborted" occurs when you update the CI_CELL_PACKAGE_TREATMENT_CNT table |
K78006 |
| 52412 | "Apparent invocation of the macro MO_DELETE_FILE_ITEM is not resolved" occurs when you generate MAMetadata in SAS® Customer Intelligence Studio |
K78006 |
| 49627 | The response time for a SAS® Real-Time Decision Manager campaign increases with each added treatment custom detail tag that is used in a Reply node |
K78006 |
| 49629 | SAS® Customer Intelligence Studio returns "java.lang.Integer cannot be cast to java.lang.Double" when you use an integer in an imported test case |
K78006 |
| 50632 | A "java.lang.Integer cannot be cast to java.lang.Double" exception occurs when you import a test case into SAS® Real-Time Decision Manager 6.1 |
K78006 |
| 51816 | The SAS® Customer Intelligence stored process &MATableForMacro data set does not contain campaign UDF values |
K78006 |
| 52414 | Executing a campaign in SAS® Customer Intelligence results in performance issues |
K78006 |
| 52837 | Custom details might be truncated in the MOMA Communications table in SAS® Customer Intelligence Studio |
K78006 |
| 53667 | Dynamic treatments that use custom detail tags do not remove blank values when you export to a file or database table |
K78007 |
| 53718 | When you select multiple values from a dynamic list for a user-defined field, the values are not trimmed before they are published to the _EXT tables |
K78007 |
| 53822 | You are unable to open a decision diagram that contains a Subdiagram node |
K78007 |
| 53662 | Exporting custom detail tags in SAS® Customer Intelligence might result in huge files that can cause out-of-disk-space conditions |
K78007 |
| 52831 | Running the migration scripts for the common data model in SAS® Marketing Automation 6.1 and 6.3 might result in errors |
K78007 |
| 53222 | The error "A lock is not available for MATABLES" might occur when you execute a campaign |
K78007 |
| 53394 | Common Data Model tables do not update correctly when a campaign execution fails to publish in SAS® Customer Intelligence Studio |
K78007 |
| 53806 | Executing a SAS® Marketing Automation campaign that generates a SAS® Digital Marketing broadcast fails with an error |
K78007 |
| 53823 | SAS® Customer Intelligence export data might be appended to the existing export files instead of the export files that are being replaced |
K78007 |
| 54202 | The SAS® Customer Intelligence Studio client IP address is not available in the log files |
K78008 |
| 54177 | SAS® Customer Intelligence Studio users might experience instability problems when the architecture includes SAS® Digital Marketing |
K78008 |
| 54377 | An error occurs when you attempt to use SAS® Customer Intelligence Marketing Integration web services |
K78008 |
| 53046 | The incorrect END_DTTM entry in the CI_COMMUNICATION table is published to the common data model when you are executing communications separately |
K78010 |
| 55430 | The domain ID is not honored when you schedule a campaign group in SAS® Customer Intelligence |
K78010 |
| 55324 | Executing a campaign in SAS® Customer Intelligence might fail with the error "java.util.ConcurrentModificationException" |
K78010 |
| 55433 | Executing a campaign in SAS® Customer Intelligence might fail with a java.util.ConcurrentModification exception |
K78010 |
| 54578 | An incorrect date is returned when you enter a date value or use the calendar in SAS® Customer Intelligence Studio |
K78010 |
| 55429 | Updating the Contact History table takes excessive time when you generate input data from a campaign group in SAS® Marketing Automation |
K78010 |
| 55432 | The execution of an optimization group in SAS® Customer Intelligence Studio might fail when one communication contains a control group |
K78010 |
| 53264 | Special characters in the name of a Cell or Communication node are not displayed in the MATableForMacro table in SAS® Customer Intelligence |
K78010 |
| 54570 | An incorrect date is published to the common data model when you select "1st January" in a Custom Detail group |
K78010 |
| 54571 | An incorrect date is returned when you select "1st January year-number" in a process node in SAS® Customer Intelligence Studio |
K78010 |
| 54696 | The error "Invalid Expression" occurs when you create a calculated variable in an expression that includes multiple variable names that are similar |
K78010 |
| 54816 | The CI_CONTACT_HISTORY table might contain incorrect RESPONSE_TRACKING_CD values under some circumstances in SAS® Marketing Automation |
K78010 |
| 54972 | Special characters in the name of a Cell or Communication node are not displayed when you use %MASPINIT(XMLSTREAM=MACROVAR NEIGHBOR) |
K78010 |
| 55443 | An error occurs when you define numeric-only code formats in SAS® Customer Intelligence Studio |
K78010 |
| 55363 | Security vulnerability scanners might report cross-site scripting vulnerabilities in Flex-based SAS® web applications |
K78011 |
| 55598 | An error occurs when you select missing values for a Select node and you use a German localization of SAS® Customer Intelligence Studio |
K78011 |
| 55998 | Time values are not displayed when you export date and time values for a custom detail in SAS® Customer Intelligence |
K78011 |
| 55158 | The byte-order mark (BOM) signature is missing when you export data to a file in SAS® Customer Intelligence |
K78011 |
| 55244 | CI_COMMUNICATION_EXT records are not written each time a campaign or communication is executed |
K78011 |
| 56065 | Migrating a Custom Details date field from an earlier release of SAS® Marketing Automation shows the value as one day earlier (-1 day) |
K78012 |
| 56906 | Importing or exporting a SAS® Marketing Automation package fails and returns a null pointer exception error |
K78012 |
| 56103 | The Load Treatments utility in SAS® Customer Intelligence does not update the treatment custom details |
K78012 |
| 56708 | A Custom Details date field shows the value as one day earlier (-1 day) when you run the Load Treatments utility in SAS® Customer Intelligence Studio |
K78012 |
| 57145 | An incorrect date is returned when you enter a date value in treatments that are used in SAS® Customer Intelligence Studio |
K78012 |
| 56566 | Executing optimized communications with holdout groups does not update the SAS® Customer Intelligence Common Data Model |
K78012 |
| 57068 | Invalid dates are inserted into the contact history after the initial contact history insert fails |
K78012 |
| 56883 | Column selections are not saved in the Selection Campaigns workspace for SAS® Marketing Automation |
K78012 |
| 57631 | Executing a campaign in SAS® Marketing Automation results in the error "ServiceException in IODavUtil:getFolder" |
K78013 |
| 56618 | Custom drop-down lists do not transfer to SAS® Customer Intelligence from SAS® Marketing Operations Management |
K78014 |
| 57703 | The SAS® Customer Intelligence Integration Utilities extract utility (Sasmaextract) might fail when you extract a field that has a datetime format |
K78014 |
| 58239 | SAS® Customer Intelligence contains security vulnerabilities that have been identified by IBM Security AppScan |
K78014 |
| 56294 | The scripts that are used for migrating the SAS® Customer Intelligence Common Data Model take a long time to execute |
K78014 |
| 57558 | Failing scheduled-campaign execution shows an incorrect Exit code in IBM Platform LSF or SAS® Marketing Automation Launcher |
K78014 |
| 58023 | A "java.lang.NullPointerException" error occurs when you select the "Cell represents a control group" option in SAS® Customer Intelligence Studio |
K78014 |
| 58372 | The count might be incorrect when you use SAS® web services to modify a SAS® Customer Intelligence Studio "Select" node |
K78014 |
| 58487 | SAS® Marketing Automation custom date fields show the date input as two days earlier when the date is updated via SAS® web services |
K78014 |
| 58617 | ALERT - Optimizations fail after you make changes to a business context |
K78015 |
| 58618 | SAS® Real-Time Decision Manager stand-alone installations might prompt for a valid SAS® Customer Intelligence Studio license |
K78015 |
NOTE: If you install this hot fix and have SAS Marketing Optimization installed, you must also install hot fix:
K84013 for SAS Marketing Optimization.
NOTE: If you install this hot fix and have SAS Digital Marketing installed, you must also install hot fix:
K90014 for SAS Digital Marketing. |
|
| 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