| Z77027 |
| SAS Marketing Automation 6.5 |
| Issue(s) Addressed: | Introduced: |
| 58618 | SAS® Real-Time Decision Manager stand-alone installations might prompt for a valid SAS® Customer Intelligence Studio license |
Z77001 |
| 58713 | Group membership in the Customer Intelligence Basic Campaign Designer does not enable users to create campaigns |
Z77001 |
| 58779 | You cannot stage treatments from a selection campaign in SAS® Marketing Automation |
Z77001 |
| 58584 | Extracting campaigns that contain attached documents can cause an out-of-memory error in SAS® Customer Intelligence Integration Utilities |
Z77002 |
| 58969 | Saving a date custom detail in SAS® Customer Intelligence Studio changes the date to -1 day when you use UTC time zones |
Z77002 |
| 59043 | Changes to the delimiter in an export definition in SAS® Customer Intelligence Studio do not persist |
Z77002 |
| 58899 | The export preview might not display correct values for a Communication custom detail |
Z77002 |
| 58909 | Displaying properties for a Split node might take a long time in SAS® Customer Intelligence Studio |
Z77002 |
| 59012 | You are unable to run a decision campaign that includes one or more Stage nodes |
Z77002 |
| 59016 | Performance problems occur when SAS® Customer Intelligence builds indexes on uploaded MATABLES tables |
Z77002 |
| 58991 | The renaming of a treatment in SAS® Customer Intelligence Studio is not reflected in the CI_TREATMENT table |
Z77003 |
| 58442 | Changing the "From subject" and "To subject" fields in a Process node changes those fields in all Process nodes that have a Type value of Code |
Z77003 |
| 58966 | Relative date expressions do not work when the Polish locale is used in SAS® Marketing Automation |
Z77003 |
| 59201 | Changing the "From subject" and "To subject" fields in a Process node changes those fields in all Process nodes that have a Type value of Process |
Z77003 |
| 58399 | The communication status code is incorrect in the CI_Communication table for SAS® Marketing Automation |
Z77003 |
| 59078 | Flash-based components can be manipulated by an external configuration file |
Z77003 |
| 59190 | A "Permission denied" error occurs when you try to add a seed list to the Exports page of the Communication Properties dialog box |
Z77003 |
| 59328 | SAS® Real-Time Decision Manager prompts you with a message saying that you do not have a valid license for SAS® Customer Intelligence Studio |
Z77003 |
| 59443 | An error occurs when you try to schedule a SAS® Customer Intelligence campaign that has dependent communications |
Z77004 |
| 59490 | You cannot re-enter the name of a Cell node that is created with a Split node in SAS® Customer Intelligence Studio |
Z77004 |
| 59417 | Extracted treatments are not available to the "Select Offers" functionality after they are uploaded into SAS® Customer Intelligence 360 |
Z77004 |
| 58986 | Russian Cyrillic characters are ignored in a document PDF file for a campaign |
Z77005 |
| 59193 | Incorrect dates are published to the CI_TREATMENT_DATE_UDF table and are displayed in the export preview in SAS® Customer Intelligence Studio |
Z77005 |
| 59316 | The remainder cell does not contain all records when the cell is used with a "Split" node in SAS® Marketing Automation |
Z77005 |
| 59338 | The page-status check box and flag disappears in SAS® Customer Intelligence Studio |
Z77005 |
| 59913 | The dropped count for a Select node persists after you change the rule from "No value meets these criteria" to "Any value meets these criteria" |
Z77005 |
| 59646 | Non-existent Cell nodes appear in the "Select cell" list when you import linked campaigns from earlier releases of SAS® Marketing Automation |
Z77005 |
| 58518 | Exporting date-time custom details from the Communication node modifies the format of the date-time value |
Z77005 |
| 59339 | The "Package Summary" tab (in the "Selection Summary" window) in SAS® Customer Intelligence Studio does not display the pie and bar charts |
Z77005 |
| 58372 | The count might be incorrect when you use SAS® web services to modify a SAS® Customer Intelligence Studio "Select" node |
Z77005 |
| 59020 | The Dropped count shown in a Select node properties dialog box is not updated when the criteria for the Select node changes |
Z77005 |
| 59302 | A memory leak might occur in SAS® Marketing Automation |
Z77005 |
| 59467 | Copying and pasting a group of nodes generates extra connecting arrows between nodes in SAS® Marketing Automation |
Z77005 |
| 59633 | An index-out-of-bounds exception occurs when you change selection criteria in a Split node in SAS® Customer Intelligence Studio |
Z77005 |
| 59634 | Executing several sasmalauncher sessions in a clustered, middle-tier environment might fail |
Z77005 |
| 59654 | Custom details are not displayed for a staged treatment in SAS® Real-Time Decision Manager |
Z77005 |
| 59741 | A Filter node fails validation when it is used with a Data Item criteria value of 'not (Missing)' |
Z77005 |
| 59988 | The date value for Custom Details in a SAS® Customer Intelligence Studio treatment is incorrect |
Z77005 |
| 60037 | The Date and Time control for a date custom field displays the incorrect time when you click OK |
Z77005 |
| 59674 | Export files that are created by Communication nodes in SAS® Marketing Automation contain incorrect Control Group codes |
Z77005 |
| 59734 | Refreshing SAS® Marketing Optimization input data in a campaign group fails when the underlying database is Microsoft SQL |
Z77005 |
| 58788 | Widened, exported MATables are orphaned in the operating environment when you close the browser by clicking the Close (X) button |
Z77006 |
| 58823 | Descriptive text fields change to text boxes when they are included in a group container in SAS® Customer Intelligence Studio |
Z77006 |
| 59636 | Custom Detail values for a dynamic list do not render correctly in a campaign PDF document in SAS® Customer Intelligence Studio |
Z77006 |
| 60022 | You cannot extract treatments with treatment code when you use SAS® Marketing Automation Integration utilities |
Z77006 |
| 60214 | The Load Treatments utility does not update the Treatment custom detail "Check box" type field |
Z77006 |
| 60230 | The sasmaimport command adds a duplicate output cell when you import a diagram with SAS® Customer Intelligence Integration Utilities |
Z77006 |
| 60423 | The business context fails to validate the connection details when you use a proxy server that requires authentication |
Z77006 |
| 60449 | Incorrect datetime values are exported when you use tags to reference the Date-Time Range custom field in a treatment |
Z77006 |
| 60453 | No data is exported when you have multiple treatments with custom "Date and time" fields that share the same tag |
Z77006 |
| 60544 | The sasmaimport command in SAS® Customer Intelligence Integration Utilities does not import static list values used in a Process node |
Z77006 |
| 59128 | An export definition is imported into the wrong business context in SAS® Marketing Automation |
Z77006 |
| 60073 | Scheduling many operating system scheduler jobs causes the operating system to use a large quantity of resources and affects performance |
Z77006 |
| 60249 | The SAS® Management Console Schedule Manager plug-in cannot handle flows with 1_ as a prefix when you schedule campaigns or communications |
Z77006 |
| 60660 | The status for the DELETED_FLG column is updated incorrectly in the CI_CELL_PACKAGE table in SAS® Marketing Automation |
Z77006 |
| 58585 | The SAS® Customer Intelligence LoadTreatment utility does not load labels |
Z77006 |
| 58980 | Variables filtered out in a SAS® Real-Time Decision Manager "SAS Process" node definition appear to be deleted |
Z77006 |
| 59488 | Attachments that are added to a campaign manually in SAS® Marketing Automation do not render correctly when you view them with Google Chrome |
Z77006 |
| 59819 | A broadcast property page is displayed in error when you open a campaign communication in SAS® Customer Intelligence Studio |
Z77006 |
| 60248 | LEVEL=ID data items are filtered out as selectable fields in the export inside a Communication node in SAS® Customer Intelligence Studio |
Z77006 |
| 60620 | An error occurs when you try to reorder input variables in a SAS® process definition that has a value of SAS DS2 for "Code type" |
Z77006 |
| 55325 | Executing more than one communication in SAS® Customer Intelligence might fail with a java.util.ConcurrentModificationException |
Z77006 |
| 58987 | You receive an error when SAS® Marketing Automation integration web services are requested |
Z77006 |
| 59340 | Generating SAS® Marketing Optimization input data fails when you refine data on different subject levels |
Z77006 |
| 59576 | Special characters are not displayed in the table NEIGHBOR when you use the &MATableForMacro macro in SAS® Customer Intelligence |
Z77006 |
| 59944 | "Criteria variable" operators for a Process node change unexpectedly in SAS® Real-Time Decision Manager |
Z77006 |
| 59959 | Campaign validation fails and errors occur when you use a Data Grid identifier in the ARRAYUTILS.JOINSTRINGS function |
Z77006 |
| 60225 | Enabling the option "Use the most current data when referenced by a link" only returns current data when a campaign is executed |
Z77006 |
| 60327 | An error occurs when you attempt to open the properties for a flow that is sent by SAS® Customer Intelligence |
Z77006 |
| 60350 | Request variable values in a Subdiagram node are reset after the identifier in the Event definition is changed |
Z77006 |
| 60398 | An error occurs when the reporting library for a business context is changed and you run a test case for a decision campaign |
Z77006 |
| 60422 | A SAS® Real-Time Decision Manager test case fails if the event has a reply variable of type Data Grid |
Z77006 |
| 60432 | SAS® Customer Intelligence Studio displays the incorrect time when you change the Time value manually in the custom details |
Z77006 |
| 60621 | Running the RHUPDATE DS2 activity generates the error "tap_array.boundsCheck(): Index 1 out of bounds. Must be between 1 and 0 inclusive" |
Z77006 |
| 60682 | Previously published campaign information might be deleted when the latest version is executed |
Z77006 |
| 60704 | Incorrect counts might appear in an Or node in SAS® Customer Intelligence when the underlying database is Microsoft SQL Server |
Z77006 |
| 60760 | Previously existing JAR Files in the . . .WEB-INF/lib directory are not removed when you upgrade SAS® Marketing Automation |
Z77006 |
| 57561 | Teradata deadlock issues occur when you concurrently publish multiple SAS® Customer Intelligence campaigns to the Common Data Model |
Z77006 |
| 60426 | Treatement tags with values of 0 or 9 (or 0 and 9) are not exported properly in SAS® Customer Intelligence |
Z77006 |
| 60429 | Executing a campaign in SAS® Customer Intelligence fails when you use case-sensitive collation |
Z77006 |
| 60435 | Concurrent exports to a single Teradata table fail with a duplicate, unique prime-key error |
Z77006 |
| 60451 | Incorrect dates are exported when you have multiple treatments with custom date fields that share the same tag |
Z77006 |
| 60520 | An error occurs when you update counts in a Response node and the subject key consists of more than one column |
Z77006 |
| 60680 | A Teradata deadlock occurs and generates an error when you publish multiple campaigns to the SAS® Customer Intelligence Common Data Model |
Z77006 |
| 60686 | ALERT - SAS® Customer Intelligence Studio is no longer available after you upgrade the platform to SAS® 9.4 TS1M5 |
Z77007 |
| 58970 | You cannot disable the "Required" flag in the Custom Details Groups in SAS® Customer Intelligence Studio |
Z77008 |
| 60431 | The sasmaextract utility in SAS® Customer Intelligence does not mask the ampersand (&) character correctly |
Z77008 |
| 61005 | The warning "A valid directory was not found in log4j.properties" is generated when you use SAS® Marketing Automation Integration Utilities |
Z77008 |
| 61240 | Counts are not updated when you execute a campaign multiple times in the same SAS® Customer Intelligence Studio session |
Z77008 |
| 61006 | The error "java.util.NoSuchElementException" is displayed in the import log when you import decision campaigns |
Z77008 |
| 61183 | The initial loading of a large number of campaigns into the SAS® Customer Intelligence Studio Selection Campaigns category is slow |
Z77008 |
| 60101 | Certain Cyrillic characters are rendered with trailing spaces when you produce campaign document PDF files |
Z77008 |
| 59578 | Custom details (of type Hyperlink) that are used in SAS® Customer Intelligence Studio do not work for shared folders |
Z77008 |
| 59995 | The maximum value count does not refresh in SAS® Customer Intelligence Studio when you change Custom Detail labels |
Z77008 |
| 60717 | Searching for campaigns that contain non-standard Latin characters is very slow in SAS® Customer Intelligence Studio |
Z77008 |
| 61007 | An incorrect time is published when you use a custom-written stored process in SAS® Customer Intelligence Studio |
Z77008 |
| 60450 | SAS® Marketing Automation campaign custom details are not populated when you use the Review Campaign web service |
Z77008 |
| 60961 | Hebrew characters are ignored when you create a campaign document in SAS® Customer Intelligence Studio |
Z77008 |
| 61072 | Records are not written to the CI_DYNAMIC_TREATMENT_ATTR_EXT table when the same treatment is assigned more than once |
Z77008 |
| 61093 | The assigned eligibility in a Decision Treatment Campaign disappears when you update the treatment |
Z77008 |
| 61173 | You do not see a count for a selected value after you click "Update Counts" |
Z77008 |
| 61241 | Applying Hot Fix Z77007 (in SAS Note 60704) to correct counts in an OR node does not work when a driver name contains a period (.) |
Z77008 |
| 60850 | The export file contains a different (and incorrect) position for a field than the position that is specified in the export definition |
Z77008 |
| 61182 | Performance is slow when you publish a small number of treatments to a Teradata database |
Z77008 |
| 61596 | The refine-output functionality fails when you use it with a numeric field that is defined as "Nominal" |
Z77009 |
| 61609 | You cannot split the input data and optimization process into two separate processes when you execute the task from the Launcher application |
Z77009 |
| 61679 | The sasmaimport command in SAS® Customer Intelligence Integration Utilities does not import custom details for treatments properly |
Z77009 |
| 61278 | Executing a campaign group in SAS® Customer Intelligence executes only a small number of concurrently running processes |
Z77009 |
| 61289 | The ContentCheck parameter in the SAS® Customer Intelligence SASCIUTILS utility does not work when HTTPS is configured for SAS® Content Server |
Z77009 |
| 61628 | When you try to select a numeric data item in SAS® Customer Intelligence Studio, the action fails and "Value must be a number" is displayed |
Z77009 |
| 60227 | An incorrect command is generated when you add a campaign to a SAS® Customer Intelligence campaign group |
Z77009 |
| 60376 | Treatment custom-detail values are not maintained after you update a treatment in SAS® Customer Intelligence Studio |
Z77009 |
| 61404 | An error occurs in SAS® Marketing Automation when you execute or update counts in a campaign with a Map node that feeds a Select node |
Z77009 |
| 61576 | Optimizing MOMA input data fails and generates the error "Not able to optimize the campaign group" in SAS® Customer Intelligence Studio |
Z77009 |
| 61610 | "TypeError: Error #1009" occurs in SAS® Customer Intelligence Studio when you create a treatment |
Z77009 |
| 61671 | Static Link nodes do not use the correct counts when you use layers of linked campaigns in SAS® Customer Intelligence Studio |
Z77009 |
| 61726 | SAS® Customer Intelligence Studio contains a security vulnerability |
Z77009 |
| 60853 | An error occurs and the contact-history insert step fails when you optimize campaign groups in SAS® Marketing Automation |
Z77010 |
| 60940 | The execution of a campaign group in SAS® Customer Intelligence fails when you use case-sensitive collation |
Z77010 |
| 62204 | Incorrect SQL code is generated when you use a missing (null) value in combination with a logical OR in a Select node |
Z77011 |
| 62187 | An error occurs when you select an "Identifier" field in the "Output variables" category of a Business Rules node |
Z77011 |
| 62244 | An export definition type of "SAS Customer Intelligence 360" is incorrectly available in SAS® Customer Intelligence Studio |
Z77011 |
| 59859 | Date values are recorded incorrectly for the locale when you enter a data value in a Select node in SAS® Marketing Automation |
Z77011 |
| 61238 | An error occurs and no responses or contacts are available in SAS® Real-Time Decision Manager |
Z77011 |
| 61352 | An "illegal character" error occurs when you use a Process node in SAS® Customer Intelligence Studio |
Z77011 |
| 61808 | An error occurs when you attempt to validate a decision campaign after you assign a treatment to the campaign |
Z77011 |
| 62070 | Multiple imported lists are created in SAS® Customer Intelligence 360 when a SAS® Customer Intelligence campaign is re-executed |
Z77011 |
| 62101 | The error "MAIQService:executeFastPath" occurs when you update counts inside a Link node in SAS® Customer Intelligence Studio |
Z77011 |
| 62175 | The contact history's OPTIMIZATION_BACKFILL_FLG column in SAS® Marketing Automation displays incorrect values when you execute a campaign group |
Z77011 |
| 62250 | SAS® Customer Intelligence Studio contains a security vulnerability |
Z77011 |
| 62264 | You cannot programmatically extract campaign documentation PDF files and save them to the file system |
Z77011 |
| 62265 | The campaign status is set to "successful" even when publishing of the dynamic treatment UDF fails in SAS® Customer Intelligence |
Z77011 |
| 62351 | An error occurs when you have multiple tasks with the same name during input-data generation for a campaign group |
Z77011 |
| 62407 | SAS® Customer Intelligence Studio contains a security vulnerability |
Z77011 |
| 62601 | You cannot delete multiple campaigns quickly in SAS® Customer Intelligence Studio |
Z77011 |
| 61277 | Date and time values are truncated in an export table in SAS® Marketing Automation |
Z77011 |
| 61611 | The error "Transaction Aborted due to deadlock" occurs on the CI_CELL_PACKAGE table when you execute multiple SAS® Customer Intelligence campaigns |
Z77011 |
| 62308 | You cannot export to an XML file when you use SAS® Customer Intelligence Studio |
Z77011 |
| 60232 | The sasmaimport command in SAS® Customer Intelligence Integration Utilities fails when two Communication nodes are connected to a Process node |
Z77012 |
| 62679 | The campaign Start column is blank in SAS® Customer Intelligence Studio |
Z77012 |
| 62100 | Incorrect counts appear in a Select node when you select "Any value meets this criteria" from the Rule list in SAS® Customer Intelligence Studio |
Z77012 |
| 62502 | Generating input data for a MOMA campaign group might fail in a clustered, middle-tier environment |
Z77012 |
| 62630 | The Selection Campaigns Approval page displays an incorrect user name for the 'Last modified by' field in SAS® Customer Intelligence Studio |
Z77012 |
| 62727 | Date values in Custom Detail date fields shift by -2 days in SAS® Customer Intelligence Studio |
Z77012 |
| 62721 | Performance issues and high CPU usage occur when you use complex Link node campaigns in SAS® Customer Intelligence Studio |
Z77012 |
| 62788 | You cannot export to a database table when you use SAS® Customer Intelligence Studio |
Z77012 |
| 62815 | The error "Session context has been destroyed" has been observed during execution of a campaign from the SAS® Marketing Automation Launcher |
Z77013 |
| 62102 | The error "The table MATables does not exist" occurs when you execute static Link nodes in SAS® Customer Intelligence Studio |
Z77014 |
| 62161 | Integration with SAS® Customer Intelligence 360 fails because a data descriptor cannot be created when you execute a campaign |
Z77014 |
| 63030 | SAS® Customer Intelligence Studio contains a security vulnerability with attachments |
Z77014 |
| 59057 | Selection-group custom details do not work in SAS® Customer Intelligence Studio |
Z77014 |
| 60718 | The time or datetime values in a user-defined format incorrectly changes when they are used in a SAS® Customer Intelligence Studio campaign |
Z77014 |
| 62631 | Datetime values in a Communication node's custom details are incorrect when they are used in a SAS® Customer Intelligence selection campaign |
Z77014 |
| 60545 | Values for the date-and-time range are displayed incorrectly in SAS® Customer Intelligence Studio |
Z77014 |
| 62912 | An error occurs when you attempt to open diagram tools in SAS® Customer Intelligence Studio |
Z77014 |
| 62980 | ALERT - An error occurs when a Self Learner process that uses identifiers fails to retrain in SAS® Real-Time Decision Manager |
Z77014 |
| 63046 | Viewing custom details from the Treatments page for a SAS® Real-Time Decision Manager campaign takes a long time in SAS® Customer Intelligence Studio |
Z77014 |
| 63116 | Marketing Integration Web Services does not handle dynamic custom lists with more than 1,000 elements |
Z77014 |
| 62737 | SAS® Customer Intelligence Web Services do not pre-populate numeric custom-detail values |
Z77015 |
| 63265 | Selection-group custom details do not export correctly in SAS® Customer Intelligence Studio |
Z77015 |
| 62962 | Access control templates (ACTs) for SAS® Marketing Automation 6.5 do not prevent users from seeing campaigns |
Z77015 |
| 63362 | You cannot open campaigns that have assigned treatments after you apply Hot Fix Z77014 or Hot Fix U53019 |
Z77015 |
| 61010 | Incorrect values are stored for the common data model when it is used in a SAS® Customer Intelligence Studio campaign |
Z77015 |
| 61860 | A Gantt chart on the Execution page in SAS® Customer Intelligence Studio shows incorrect date values |
Z77015 |
| 62053 | A flash error occurs when you use the table import function to create a new SAS® Real-Time Decision Manager event definition |
Z77015 |
| 63288 | Static date-range values for treatment custom details in SAS® Customer Intelligence Studio do not retain the correct date |
Z77015 |
| 63304 | The message "TypeError: Error #1034" is displayed when you double-click an export folder in SAS® Customer Intelligence Studio |
Z77015 |
| 63309 | You cannot delete existing input or output variables in a SAS process definition in SAS® Real-Time Decision Manager |
Z77015 |
| 63355 | An incorrect date (-1 day) is passed when you use a custom-written stored process in SAS® Customer Intelligence Studio |
Z77015 |
| 63400 | Blocked Teradata sessions occur when you use SAS® Contact Rule DS2 Activity processing in SAS® Real-Time Decision Manager |
Z77015 |
| 63043 | An error occurs when you select a project from the SAS® Model Manager projects list and click "OK" in SAS® Real-Time Decision Manager |
Z77015 |
| 63054 | The error "Could not find process" occurs in SAS® Real-Time Decision Manager when a scheduled Self Learner process runs incorrectly |
Z77015 |
| 63287 | The error "The table MATables does not exist" occurs when you execute dynamic Link nodes in SAS® Customer Intelligence Studio |
Z77015 |
| 63419 | Campaign communication occurrences are set to minus one (-1) in SAS® Customer Intelligence |
Z77015 |
| 63313 | Publish behavior for communication definitions in SAS® Customer Intelligence Studio is not consistent when you use radio buttons |
Z77015 |
| 63356 | Deletion of the MATables data set is slow when you execute campaigns in SAS® Customer Intelligence Studio |
Z77015 |
| 60521 | An error is generated when you use SAS® Management Console to export a SAS® Marketing Automation communication definition to a SAS® package |
Z77016 |
| 62680 | You cannot use the BULKLOAD=YES and PARALLEL=TRUE options when you append to a table in SAS® Customer Intelligence Studio |
Z77016 |
| 63652 | Performance degradation occurs when you load or save campaigns in SAS® Customer Intelligence Studio |
Z77016 |
| 63740 | Incorrect counts are shown in some nodes when you use static Link nodes in SAS® Customer Intelligence Studio |
Z77016 |
| 63889 | Duplicate values are shown in a custom detail after the custom detail has been updated from SAS® Customer Intelligence Web Services |
Z77016 |
| 58650 | An Adobe Flex memory leak occurs when you open and then close a campaign in SAS® Customer Intelligence Studio |
Z77016 |
| 59586 | No error message occurs when you add invalid characters in a campaign diagram in SAS® Marketing Automation |
Z77016 |
| 61744 | An error occurs when the maxdate field in a Custom Details group is populated automatically with the default value of 'December 31, 19900' |
Z77016 |
| 61769 | You receive an error when you search for a communication definition in SAS® Customer Intelligence Studio |
Z77016 |
| 63619 | The error "TypeError: Error #1009" occurs in SAS® Customer Intelligence Studio when you select a date value in a custom-detail field |
Z77016 |
| 60373 | Campaign PDF documents do not render Cyrillic characters correctly in SAS® Customer Intelligence Studio |
Z77016 |
| 61544 | You cannot place a Process node after another Process node that follows an Export node in a SAS® Marketing Automation campaign |
Z77016 |
| 63620 | Slow performance occurs when you use campaigns in SAS® Customer Intelligence Studio |
Z77016 |
| 63653 | A task-sequence error occurs when you generate or refresh optimization data in SAS® Customer Intelligence Studio |
Z77016 |
| 64217 | ALERT - An error occurs when you execute or optimize a campaign group in SAS® Customer Intelligence |
Z77017 |
| 63298 | You receive an HTTP 500 error in SAS® Customer Intelligence Studio when you try to create a PDF document for a campaign |
Z77018 |
| 63303 | The incorrect channel name is displayed in SAS® Customer Intelligence Studio after you add a new channel |
Z77018 |
| 63534 | The SAS® Customer Intelligence Custom Details tags are not included in the SPK file as a dependent object when exporting from SAS® Management Console |
Z77018 |
| 64006 | The error "MATables does not exist" occurs in SAS® Customer Intelligence when you use dynamic Link nodes with the "Exclude these subjects" property |
Z77018 |
| 64008 | Defining selection groups within custom details in SAS® Customer Intelligence accidentally requests a value |
Z77018 |
| 64136 | The "Duration of Event" value cannot be specified when you send a campaign schedule directly to the scheduler in SAS® Customer Intelligence Studio |
Z77018 |
| 64226 | Scheduled executions (via the mabatch command-line utility) fail intermittently in a SAS® Customer Intelligence vertical-cluster environment |
Z77018 |
| 64326 | The SAS® Customer Intelligence LoadTreatments utility does not populate the "Activation date" and "Expiration date" fields properly as datetime values |
Z77018 |
| 64351 | An MAIQService error occurs when you update counts in a Cell node when the upstream Select node's criteria value is a data item |
Z77018 |
| 61942 | SAS® Customer Intelligence campaigns fail and generate the error "Invalid option name XX_XX" in the stored-process server log |
Z77018 |
| 64068 | Performance issues occur when the SAS® Customer Intelligence common data model CI_COMMUNICATION table automatically updates |
Z77018 |
| 62623 | A Gantt chart shows an incorrect color for a successful campaign on the Execution Page in SAS® Customer Intelligence Studio |
Z77019 |
| 64309 | Export data that uses a semicolon as a delimiter outputs files that contain blanks instead of semicolons in SAS® Customer Intelligence 6.5 |
Z77019 |
| 61441 | You cannot generate input data for a campaign group when a cell code is blank |
Z77019 |
| 62531 | You cannot identify which campaign submits a query to the Oracle database from SAS® Customer Intelligence Studio |
Z77019 |
| 62695 | Decision campaigns open slowly in SAS® Customer Intelligence Studio when the arbitration method "Sort" is used with a large number of treatments |
Z77019 |
| 64506 | The error "[CELLNODENAME]: Error in the stored process or a called macro - vendor code: 1012" occurs when a SAS® Customer Intelligence campaign fails |
Z77019 |
| 64554 | You receive Deny permission for input data even though you have Grant permission to a campaign group in SAS® Customer Intelligence |
Z77019 |
| 62736 | Incorrect treatment assignments are published when you manually publish in SAS® Customer Intelligence Studio |
Z77019 |
| 63264 | SAS® Customer Intelligence Studio contains a session-fixation vulnerability |
Z77020 |
| 65075 | SAS® Customer Intelligence Studio is vulnerable to a reverse tabnabbing attack |
Z77021 |
| 63338 | Applications that use the comments service contain a security vulnerability with the use of comments |
Z77021 |
| 64415 | Validation of a campaign flow in SAS® Real-Time Decision Manager fails with an error when corrupted Filter nodes are in the decision flow |
Z77021 |
| 64681 | SAS® Customer Intelligence queries to the Oracle database take a long time to execute |
Z77021 |
| 64736 | Calculated items from a campaign that is contained in an imported SPK package cannot be viewed in SAS® Customer Intelligence Studio |
Z77021 |
| 64926 | The message "nested selection groups: One or more of the required reply variables does not have a value" is shown in SAS® Customer Intelligence Studio |
Z77021 |
| 64935 | The sasmaextract utility in SAS® Customer Intelligence fails when you use it inside a Process node in a diagram |
Z77021 |
| 64962 | SAS® Customer Intelligence Studio users can access treatments from other business contexts |
Z77021 |
| 65009 | A campaign execution fails when a Select node's criteria value is a data item |
Z77021 |
| 65148 | Scheduled campaign executions fail after you apply certain hot fixes (Z77018, Z77019, or Z77020) to SAS® Marketing Automation |
Z77021 |
| 65165 | SAS® Customer Inteligence Studio contains a version of the BlazeDS library that is vulnerable to the issue that is described in CVE-2017-3066 |
Z77021 |
| 65172 | SAS® Marketing Automation export fields that have numeric tags are converted to character fields when the field value is null |
Z77021 |
| 64941 | An error occurs and publishing to the Contact History fails in SAS® Customer Intelligence when you use SAS/ACCESS® Interface to Microsoft SQL Server |
Z77021 |
| 65312 | ALERT - A pop-up error occurs when you create a custom detail using the selection group and set up a required field in SAS® Customer Intelligence |
Z77022 |
| 64731 | Executing the SAS® Customer Intelligence utility -releasetables causes all campaigns to be republished |
Z77023 |
| 59992 | An incorrect validation message appears in SAS® Customer Intelligence Studio when you schedule campaigns that have monthly occurrences |
Z77023 |
| 64846 | Updates to the SAS® Customer Intelligence Common Data Model fail during an upgrade from SAS® Marketing Automation 6.4 to SAS® Marketing Automation 6.5 |
Z77023 |
| 64996 | The SAS® Marketing Automation command that is created by the metadata-generation process contains incorrect business-context name |
Z77023 |
| 65268 | Validation on Date_range input fields for the Custom Diagram tool generates shows an error in SAS® Customer Intelligence Studio |
Z77023 |
| 65459 | Duplicate arrows are displayed sporadically between a Prioritize node and cell nodes in SAS® Customer Intelligence Studio |
Z77023 |
| 65557 | A generated audit log for the "Create PDF Document" option is missing the first letter for Cyrillic and Hebrew characters |
Z77023 |
| 65671 | Using a semicolon character (;) as delimiter does not work when you export a file in SAS® Customer Intelligence after applying Hot Fix Z77019 |
Z77023 |
| 59932 | Zero results are returned when an A/B Test node has a Challenger size of 50% and the input population is an odd number |
Z77023 |
| 65659 | The backslash character ( \\ ) is lost if you publish to the SAS® Customer Intelligence Common Data Model and when the underlying database is Redshift |
Z77023 |
| 65664 | Deadlock issues might occur in SAS® Marketing Automation during simultaneous acquisitions and release of information maps |
Z77024 |
| 65888 | Using date-and-time or time ranges in custom-detail fields in SAS® Customer Intelligence Studio changes the time unexpectedly |
Z77025 |
| 64963 | A SAS® Real-Time Decision Manager Filter node with Boolean criteria automatically has the "(Missing)" value added to it |
Z77025 |
| 65661 | The error "File MATABLES.xxx.DATA does not exist" is generated when you optimize a campaign group in SAS® Customer Intelligence |
Z77025 |
| 65841 | Dynamic metadata generation does not display a picklist for a Select node in a SAS® Customer Intelligence Studio |
Z77025 |
| 65843 | The SAS® Customer Intelligence campaign PDF document contains an incorrect data-item name |
Z77025 |
| 65890 | Using Link nodes with the "Exclude these subjects" option selected displays incorrect counts in SAS® Customer Intelligence Studio |
Z77025 |
| 65910 | The most current data is not used when you generate or refresh campaign-group input data SAS® Marketing Automation |
Z77025 |
| 66145 | The option "Dcom.sas.ci.staticlinknode.owntable=true" causes performance issues in SAS® Customer Intelligence |
Z77026 |
| 66165 | A "java.lang.StackOverflowError" error occurs when you run the Release Tables utility with the -releasetables option in SAS® Customer Intelligence |
Z77026 |
| 66318 | The Edit Size dialog box is not displayed in SAS® Customer Intelligence Studio 6.5 |
Z77026 |
| 66335 | The width for a text field in a selection group is not displayed properly in SAS® Customer Intelligence Studio 6.5 |
Z77026 |
| 66138 | Users and groups in a SAS® Marketing Automation campaign with Link nodes receive permission of the underlying campaign instead of its own permission |
Z77026 |
| 66263 | You cannot set up the Customer Intelligence Basic Campaign Designer user ID to use a Process node and deny an Export node |
Z77026 |
| 66497 | Not all Turkish characters are displayed in a campaign document that you create in SAS® Customer Intelligence Studio |
Z77026 |
| 60703 | A Write lock occurs when you publish multiple campaigns to the SAS® Customer Intelligence Common Data Model that resides in the Teradata database |
Z77026 |
| 66169 | Numeric treatment tags that are attached to one "Cell" node in SAS® Customer Intelligence are not exported properly |
Z77026 |
| 67002 | SAS® Customer Intelligence Studio displays a blank window when you open the Custom Detail page in a Communication node |
Z77027 |
| 67120 | Date and time values that you select from a dynamic list are displayed incorrectly in SAS® Customer Intelligence |
Z77027 |
NOTE: If you install this hot fix and have SAS Marketing Optimization 6.5 installed, you must also install hot fix Z82026 for SAS Marketing Optimization.
NOTE: If you install this hot fix and have SAS Digital Marketing 6.5 installed, you must also install hot fix Z69024 for SAS Digital Marketing.
NOTE: If you install this hot fix, are still on SAS 9.4M3 and need the fix documented in SAS Note 62540, you must also install hot fix W43008. Please follow the instructions in W43008 carefully.
|
|
| 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