R60017 for Windows for x64 |
SAS Marketing Automation 6.3 |
Issue(s) Addressed: | Introduced: |
53667 | Dynamic treatments that use custom detail tags do not remove blank values when you export to a file or database table |
R60001 |
54079 | An error occurs and campaign execution fails when you use migrated Communication nodes with custom detail tags in SAS® Customer Intelligence 6.3 |
R60001 |
54080 | Counts might be incorrect when you use custom details in the Select nodes in SAS® Customer Intelligence Studio 6.3 |
R60001 |
53002 | SAS® Real-Time Decision Manager might return "java.lang.ClassCastException" when you map a character to a character list in a custom detail tag |
R60001 |
53315 | The error "File MATABLES.xxx file does not exist" occurs when you use the Refine functionality in a SAS® Customer Intelligence export definition |
R60001 |
53394 | Common Data Model tables do not update correctly when a campaign execution fails to publish in SAS® Customer Intelligence Studio |
R60001 |
53415 | Response time for a SAS® Real-Time Decision Manager campaign increases significantly with each additional treatment when you use sort arbitration |
R60001 |
53760 | An error occurs when you update the count on a Communication node that has multiple input cells with a common immediate ancestor |
R60001 |
54061 | You cannot use migrated channels in a Communication node in SAS® Customer Intelligence 6.3 |
R60001 |
54226 | An error occurs when you update counts on diagram nodes using Link and Cell nodes in SAS® Customer Intelligence Studio |
R60001 |
54509 | The error "no contact history input table after execution of campaign" occurs when you execute a campaign in SAS® Customer Intelligence Studio |
R60001 |
54569 | Decision treatment campaign validation returns "diagram failed to generate correctly" for a calculated treatment presentation date |
R60001 |
54572 | Changes to calculated variables in one decision sub-diagram might affect other sub-diagrams in SAS® Real-Time Decision Manager |
R60001 |
54576 | Arbitration of decision treatment campaigns returns incorrect results when the arbitration relies on sorting custom detail values |
R60001 |
55805 | Staged treatments might be presented on incorrect dates in SAS® Real-Time Decision Manager campaigns |
R60001 |
54403 | Errors occur in SAS® Customer Intelligence Studio when you modify a field format in an Export properties window of a campaign |
R60002 |
55811 | SAS® Real-Time Decision Manager sasciutils -loadtreatments returns errors when LIST_DISPLAY_VALUE_COLUMN or LIST_VALUE_COLUMN is null |
R60002 |
55039 | SAS® Customer Intelligence Studio stops responding when a campaign contains a text box, an image, or both |
R60002 |
55304 | The CI_DYNAMIC_TREATMENT_ATTR_EXT table in SAS® Customer Intelligence does not honor the specified environment-variable separator |
R60003 |
55316 | A delay occurs before the value appears in the field when you enter a value in a Select node in SAS® Customer Intelligence Studio |
R60004 |
55326 | Re-executing a communication in SAS® Customer Intelligence after a failed execution does not update the COMMUNICATION_OCCURRENCE_NO table correctly |
R60004 |
55598 | An error occurs when you select missing values for a Select node and you use a German localization of SAS® Customer Intelligence Studio |
R60005 |
55676 | The CHANNEL_CD field in the CDM CI_CELL_PACKAGE table is not populated when you execute and publish migrated campaigns |
R60005 |
53264 | Special characters in the name of a Cell or Communication node are not displayed in the MATableForMacro table in SAS® Customer Intelligence |
R60005 |
54816 | The CI_CONTACT_HISTORY table might contain incorrect RESPONSE_TRACKING_CD values under some circumstances in SAS® Marketing Automation |
R60005 |
54972 | Special characters in the name of a Cell or Communication node are not displayed when you use %MASPINIT(XMLSTREAM=MACROVAR NEIGHBOR) |
R60005 |
55085 | An error occurs when you execute a campaign with more than one communication and you use the MALauncher command |
R60005 |
55443 | An error occurs when you define numeric-only code formats in SAS® Customer Intelligence Studio |
R60005 |
55545 | A linked diagram does not execute when the "Use the most current data when referenced by a link" check box is selected |
R60005 |
55618 | ALERT - Certain options do not work when you execute communications in SAS® Customer Intelligence |
R60005 |
55650 | Activation might fail for SAS® Real-Time Decision Manager contact history flows that use DS2 |
R60005 |
55775 | DS2 History processing causes uncontrolled growth in memory usage in SAS® Real-Time Decision Manager |
R60005 |
56023 | An error occurs when you review a scheduled campaign in SAS® Customer Intelligence Studio |
R60005 |
54578 | An incorrect date is returned when you enter a date value or use the calendar in SAS® Customer Intelligence Studio |
R60005 |
55040 | SAS® Marketing Automation treatment date tag values export incorrectly |
R60005 |
55429 | Updating the Contact History table takes excessive time when you generate input data from a campaign group in SAS® Marketing Automation |
R60005 |
55432 | The execution of an optimization group in SAS® Customer Intelligence Studio might fail when one communication contains a control group |
R60005 |
54405 | Extracting campaigns using the SAS® Marketing Automation Integration Utilities might fail with an error message |
R60006 |
55998 | Time values are not displayed when you export date and time values for a custom detail in SAS® Customer Intelligence |
R60006 |
56065 | Migrating a Custom Details date field from an earlier release of SAS® Marketing Automation shows the value as one day earlier (-1 day) |
R60006 |
56100 | User sessions remain locked when you use SAS® Customer Intelligence utilities |
R60006 |
56102 | The data set that is generated by the &MATableForMacro stored process does not contain the value CI_CELL_PACKE_SK |
R60006 |
56236 | SAS® Customer Intelligence Studio returns an error when you try to save a modification to a Reply definition |
R60006 |
56347 | The error "Unable to save treatment" occurs when you use the SAS® Customer Intelligence Integration Utilities to load treatments |
R60006 |
55355 | The Custom Details tab is missing when you add a migrated communication definition that has custom details to a communication node |
R60006 |
56406 | ALERT - Names are incorrectly assigned to IN_CHAR variables when you import campaigns into SAS® Real-Time Decision Manager |
R60006 |
56516 | ALERT - No values are returned when one custom attribute value is missing from a treatment in SAS® Marketing Automation |
R60006 |
56103 | The Load Treatments utility in SAS® Customer Intelligence does not update the treatment custom details |
R60006 |
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 |
R60006 |
55721 | Formatted values disappear in SAS® Customer Intelligence when you select the same value more than once |
R60006 |
55999 | Relative dates or date ranges in custom stored processes do not work in SAS® Customer Intelligence |
R60006 |
56218 | The SAS® Customer Intelligence Studio search option does not find all relevant campaigns |
R60006 |
56313 | SAS® Customer Intelligence Studio stops responding and Adobe Flash player's gray circle/exclamation mark icon is shown |
R60006 |
56210 | Duplicated rows appear in the CI_CELL_PACKAGE_COUNT work table after you run the %CICOUNT macro |
R60006 |
55244 | CI_COMMUNICATION_EXT records are not written each time a campaign or communication is executed |
R60006 |
56072 | Executing a campaign in SAS® Customer Intelligence might fail with the error "Invalid occurrenceID xxx. . ." |
R60007 |
56344 | Duplicate values for the RESPONSE_CD table column appear in the Common Data Model when you import response SPK files |
R60007 |
56380 | Hierarchical grouped prompts might fail in SAS® Customer Intelligence Studio |
R60007 |
56558 | The execution/scheduling page does not open for a campaign group in SAS® Customer Intelligence Studio |
R60007 |
56566 | Executing optimized communications with holdout groups does not update the SAS® Customer Intelligence Common Data Model |
R60007 |
56618 | Custom drop-down lists do not transfer to SAS® Customer Intelligence from SAS® Marketing Operations Management |
R60007 |
55597 | The createCampaign web service causes an exception when the campaign definition has no Custom Detail pages |
R60007 |
56294 | The scripts that are used for migrating the SAS® Customer Intelligence Common Data Model take a long time to execute |
R60007 |
56382 | You cannot copy and paste Map nodes and Cell nodes in SAS® Customer Intelligence Studio |
R60007 |
56695 | Rows from the CI_CELL_PACKAGE table are deleted in the SAS® Customer Intelligence Common Data Model when you optimize or publish a campaign group |
R60007 |
55599 | Using German characters in an export file in SAS® Customer Intelligence might distort the positional output |
R60007 |
56863 | Performance issues occur in SAS® Customer Intelligence Studio |
R60008 |
57443 | Certain Eastern European national characters are ignored in a campaign document PDF file |
R60009 |
57120 | An error occurs when you start too many campaigns at the same time with SAS® Marketing Automation Launcher |
R60009 |
57703 | The SAS® Customer Intelligence Integration Utilities extract utility (Sasmaextract) might fail when you extract a field that has a datetime format |
R60009 |
55303 | Previewing a Communication node export might fail with the error "The SAS Digital Marketing configuration is either not available or not valid" |
R60009 |
57275 | A Cell node continues to be available even after you clear the "Make the cell available for linking" check box |
R60009 |
57338 | Rows in the common data model CI_CELL_PACKAGE table are deleted after you save a campaign group |
R60009 |
57399 | The SAS® Customer Experience Personalization 6.3 interface for Celebrus 8.0.13 is available |
R60009 |
57415 | The preview of output from an Export node fails after a campaign is optimized |
R60009 |
55361 | Number values that you enter into Select node properties criteria in SAS® Customer Intelligence Studio are changed to 'unset' |
R60009 |
56954 | SAS® Customer Intelligence Studio does not respond when you add Export definitions, change Output Names, or add Seeds lists in a Communication node |
R60009 |
57092 | SAS® Customer Intelligence Studio stops responding and shows the Adobe Flash Player gray circle when you open large Process nodes or large campaigns |
R60009 |
57281 | Displayed dates differ in the Treatment Date window (from the View treatment icon) and the Custom Details page in SAS® Customer Intelligence Studio |
R60009 |
57369 | Communication definitions with a large number of external list values might cause a #1502 error in SAS® Customer Intelligence Studio |
R60009 |
57394 | Search functionality is limited to seven characters on the Campaign Execution History page in SAS® Customer Intelligence Studio |
R60009 |
57447 | Unexpected behavior occurs when you move a column heading in the Matrix view of a Treatment Assignment page in SAS® Customer Intelligence Studio |
R60009 |
57693 | Usability issues in the Assignment Matrix view for SAS® Customer Intelligence Studio Decision Campaigns Treatments |
R60009 |
56955 | Statistics for the CELL_CNTRL_GRP_TYPE do not show correct values in the Preview Export window in SAS® Customer Intelligence Studio |
R60009 |
57068 | Invalid dates are inserted into the contact history after the initial contact history insert fails |
R60009 |
57632 | An error occurs when you write contact history in SAS® Real-Time Decision Manager |
R60009 |
57562 | Executing a campaign via sasmalauncher might fail when you use a proxy server |
R60010 |
56408 | The first occurrence of a campaign that is scheduled to recur multiple times per day might occur earlier than the scheduled start time |
R60010 |
57280 | SAS® Marketing Automation Launcher generates an incorrect return code when a cluster is restarted and a scheduled campaign is executed |
R60010 |
57310 | An error occurs when the mamolib library is not available and the error prevents the generation of SAS® Marketing Automation metadata |
R60010 |
57539 | A user exception error occurs when you update counts on diagram nodes using Link and Cell nodes in SAS® Customer Intelligence Studio |
R60010 |
57558 | Failing scheduled-campaign execution shows an incorrect Exit code in IBM Platform LSF or SAS® Marketing Automation Launcher |
R60010 |
57663 | The Campaign status incorrectly shows as Complete for a SAS® Marketing Automation campaign that has multiple communications |
R60010 |
57664 | Using different locales in SAS® Customer Intelligence Studio might cause decision campaigns to fail validation and execution |
R60010 |
57662 | Stored process nodes with long prompt-field text cause display issues in SAS® Customer Intelligence Studio |
R60010 |
49221 | Temporary tables are not deleted after SAS® Customer Intelligence updates to Contact History, Response History, or Presented Treatment tables |
R60010 |
56885 | SAS® Customer Intelligence campaigns fail and return a syntax error when you connect to the common data model |
R60010 |
57287 | The Seeds list is not added when you select "Cell represents a control group" and you enable holdouts in SAS® Customer Intelligence Studio |
R60010 |
57561 | Teradata deadlock issues occur when you concurrently publish multiple SAS® Customer Intelligence campaigns to the Common Data Model |
R60010 |
57777 | The publishing of a campaign might fail when the LIBNAME statement option DBCONINIT= is part of the common data model's library definition |
R60010 |
58013 | Numeric fields are blank in an export file in SAS® Customer Intelligence when you use "Positional file" as the output type |
R60010 |
57900 | An error occurs when you schedule a campaign group with member campaigns in SAS® Customer Intelligence |
R60011 |
58239 | SAS® Customer Intelligence contains security vulnerabilities that have been identified by IBM Security AppScan |
R60011 |
59193 | Incorrect dates are published to the CI_TREATMENT_DATE_UDF table and are displayed in the export preview in SAS® Customer Intelligence Studio |
R60011 |
57362 | Custom Detail Groups modifications do not stick in SAS® Customer Intelligence Studio |
R60011 |
57386 | Nodes appear to continue processing even when a campaign that contains Link and Prioritize nodes appears to execute successfully |
R60011 |
57788 | All nodes in a diagram might disappear in SAS® Customer Intelligence Studio when you delete a selection-dependent group |
R60011 |
57805 | Character functions are missing from the function list when you create a calculated variable in Russian in SAS® Customer Intelligence Studio |
R60011 |
58023 | A "java.lang.NullPointerException" error occurs when you select the "Cell represents a control group" option in SAS® Customer Intelligence Studio |
R60011 |
58068 | A calculated item that includes the INTNX function fails validation in SAS® Customer Intelligence Studio |
R60011 |
58119 | Numeric custom details are truncated in SAS® Customer Intelligence Studio when the regional number format contains blanks |
R60011 |
58372 | The count might be incorrect when you use SAS® web services to modify a SAS® Customer Intelligence Studio "Select" node |
R60011 |
58534 | Errors are generated when scheduled campaigns fail to launch in SAS® Customer Intelligence |
R60011 |
58713 | Group membership in the Customer Intelligence Basic Campaign Designer does not enable users to create campaigns |
R60011 |
59078 | Flash-based components can be manipulated by an external configuration file |
R60011 |
56995 | The _SAS_RHUPDATE_DS2_ACTIVITY code in SAS® Real-Time Decision Manager retrieves an incorrect channel response code on first execution |
R60011 |
57145 | An incorrect date is returned when you enter a date value in treatments that are used in SAS® Customer Intelligence Studio |
R60011 |
57288 | Treatment and campaign Custom Details dates that you change to one day ahead cannot be saved in SAS® Customer Intelligence Studio |
R60011 |
57360 | You cannot log on to SAS® Customer Intelligence Studio after you remove the configuration for other SAS® Customer Intelligence components |
R60011 |
57527 | Records are not written to the CI_DYNAMIC_TREATMENT_ATTR_EXT table in SAS® Real-Time Decision Manager |
R60011 |
57741 | Treatment Custom Details date and time values in SAS® Customer Intelligence Studio show an incorrect value after you save them |
R60011 |
57767 | The error "The value must be less than or equal to the maximum value" might occur when you you change a Time value in a Treatment |
R60011 |
58012 | The date selection in the calendar control is different from the date value that is displayed in the custom date field |
R60011 |
58518 | Exporting date-time custom details from the Communication node modifies the format of the date-time value |
R60011 |
58542 | Date values for treatment Custom Details in SAS® Customer Intelligence Studio do not retain the correct date |
R60011 |
58644 | The export-preview window appears twice in SAS® Customer Intelligence Studio after you re-open it |
R60011 |
58862 | Date and time values for Custom Details in a communication definition are incorrect after you save them in SAS® Customer Intelligence Studio |
R60011 |
59139 | The Prioritize node in SAS® Customer Intelligence Studio has an incorrect value for the "Input Count" total |
R60011 |
59192 | The Choose a Date dialog box does not highlight the correct date when the dialog box is opened |
R60011 |
59931 | The Date type prompt in a custom node or a Process node displays a value that is one day earlier if your browser's time zone is set to UTC+1 |
R60011 |
58741 | ALERT - An incorrect offer count occurs when you use priority optimization in SAS® Customer Intelligence |
R60011 |
59483 | ALERT - You cannot deploy SAS® Real-Time Decision Manager 6.3 decision campaigns after you install Hot Fix R60011 |
R60012 |
58281 | The Champion/Challenger type for the A/B Test node generates an incorrect cell code for the control group |
R60013 |
59904 | Communication nodes contain incorrect holdout codes |
R60013 |
59908 | Holdout names are incorrect in Communication nodes after you change the A/B Test node type |
R60013 |
59912 | Communication holdout code is blank after you copy and paste a flow that contains an A/B Test node |
R60013 |
57298 | Background session IDs are lost when you execute campaigns or when you leave SAS® Customer Intelligence Studio sessions open |
R60014 |
58788 | Widened, exported MATables are orphaned in the operating environment when you close the browser by clicking the Close (X) button |
R60014 |
59301 | A selection campaign fails to write new dynamic-treatment records to the Netezza Common Data Model |
R60014 |
59634 | Executing several sasmalauncher sessions in a clustered, middle-tier environment might fail |
R60014 |
58081 | An error occurs when you execute a campaign with dynamic custom details in treatments in SAS® Customer Intelligence |
R60014 |
58986 | Russian Cyrillic characters are ignored in a document PDF file for a campaign |
R60014 |
59159 | The value for the CI_CONTACT_HISTORY_STATUS_CD table column is incorrect when the option 'Cell represents a control group' is enabled |
R60014 |
59576 | Special characters are not displayed in the table NEIGHBOR when you use the &MATableForMacro macro in SAS® Customer Intelligence |
R60014 |
59578 | Custom details (of type Hyperlink) that are used in SAS® Customer Intelligence Studio do not work for shared folders |
R60014 |
59618 | PDF documents that are created in SAS® Customer Intelligence Studio do not render correctly when you use the Google Chrome browser |
R60014 |
60037 | The Date and Time control for a date custom field displays the incorrect time when you click OK |
R60014 |
60101 | Certain Cyrillic characters are rendered with trailing spaces when you produce campaign document PDF files |
R60014 |
60137 | An error occurs when you validate a decision campaign that contains a data process of type 'Insert Data' |
R60014 |
60198 | A null-pointer exception occurs in SAS® Marketing Automation when the locale is not set during campaign execution |
R60014 |
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 |
R60014 |
58643 | Only one list box is displayed at a time in SAS® Customer Intelligence Studio |
R60014 |
58652 | Grouping two similar nodes in SAS® Customer Intelligence Studio might show incorrect results when the nodes are expanded |
R60014 |
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 |
R60014 |
59674 | Export files that are created by Communication nodes in SAS® Marketing Automation contain incorrect Control Group codes |
R60014 |
56786 | Incorrect counts are generated when you use the parameter DAY<=10 combined with MONTH<=10 in a Select node in SAS® Customer Intelligence Studio |
R60015 |
57409 | SAS® Marketing Automation campaign custom details are not populated when you use the Initiate Campaign web service |
R60015 |
58233 | Calculated data items are not all visible in SAS® Customer Intelligence Studio |
R60015 |
58991 | The renaming of a treatment in SAS® Customer Intelligence Studio is not reflected in the CI_TREATMENT table |
R60015 |
59316 | The remainder cell does not contain all records when the cell is used with a "Split" node in SAS® Marketing Automation |
R60015 |
59340 | Generating SAS® Marketing Optimization input data fails when you refine data on different subject levels |
R60015 |
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" |
R60015 |
60227 | An incorrect command is generated when you add a campaign to a SAS® Customer Intelligence campaign group |
R60015 |
60228 | The sasmaimport command fails when you use SAS® Customer Intelligence Integration Utilities and the first node in a diagram is a Process node |
R60015 |
60230 | The sasmaimport command adds a duplicate output cell when you import a diagram with SAS® Customer Intelligence Integration Utilities |
R60015 |
60544 | The sasmaimport command in SAS® Customer Intelligence Integration Utilities does not import static list values used in a Process node |
R60015 |
60713 | The DELETED_FLG column in the CI_CELL_PACKAGE table is not updated correctly for holdout groups |
R60015 |
54521 | Performance is slow when you are editing a complex diagram in SAS® Customer Intelligence Studio |
R60015 |
56287 | Large SAS® Real-Time Decision Manager campaigns might respond slowly in SAS® Customer Intelligence Studio |
R60015 |
56323 | Slow performance occurs when you open a large campaign after a process definition is updated |
R60015 |
58970 | You cannot disable the "Required" flag in the Custom Details Groups in SAS® Customer Intelligence Studio |
R60015 |
59058 | The Cell Code value is missing in the Communication node after you copy and paste a diagram in SAS® Customer Intelligence Studio |
R60015 |
59128 | An export definition is imported into the wrong business context in SAS® Marketing Automation |
R60015 |
60373 | Campaign PDF documents do not render Cyrillic characters correctly in SAS® Customer Intelligence Studio |
R60015 |
60718 | The time or datetime values in a user-defined format incorrectly changes when they are used in a SAS® Customer Intelligence Studio campaign |
R60015 |
61010 | Incorrect values are stored for the common data model when it is used in a SAS® Customer Intelligence Studio campaign |
R60016 |
60432 | SAS® Customer Intelligence Studio displays the incorrect time when you change the Time value manually in the custom details |
R60016 |
59490 | You cannot re-enter the name of a Cell node that is created with a Split node in SAS® Customer Intelligence Studio |
R60017 |
61679 | The sasmaimport command in SAS® Customer Intelligence Integration Utilities does not import custom details for treatments properly |
R60017 |
56961 | The contents of user-defined fields in a communication revert to their original values after counts are updated |
R60017 |
57141 | SAS® Customer Intelligence Studio shows a green process indicator when you use a Process node downstream of a Communication node updating count |
R60017 |
57909 | Counts are incorrect when you import SAS® Customer Intelligence Response definitions using SPK files |
R60017 |
58535 | Cell codes are missing after changing A/B Test node type |
R60017 |
60376 | Treatment custom-detail values are not maintained after you update a treatment in SAS® Customer Intelligence Studio |
R60017 |
60682 | Previously published campaign information might be deleted when the latest version is executed |
R60017 |
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 |
R60017 |
61507 | Incorrect results occur when you select the "Select missing values" option in a Split node |
R60017 |
60247 | Groups that are added to the Campaign Permissions list on a campaign's Definitions tab are missing after promotion |
R60017 |
60717 | Searching for campaigns that contain non-standard Latin characters is very slow in SAS® Customer Intelligence Studio |
R60017 |
61726 | SAS® Customer Intelligence Studio contains a security vulnerability |
R60017 |
58816 | An error occurs in SAS® Customer Intelligence when you execute a campaign |
R60017 |
58819 | The Teradata database stops responding when you concurrently publish multiple SAS® Customer Intelligence campaigns to the Common Data Model |
R60017 |
60680 | A Teradata deadlock occurs and generates an error when you publish multiple campaigns to the SAS® Customer Intelligence Common Data Model |
R60017 |
NOTE: If you install this hot fix and have SAS Marketing Optimization installed, you must also install hot fix:
R88014 for SAS Marketing Optimization.
NOTE: If you install this hot fix and have SAS Digital Marketing installed, you must also install hot fix:
R47014 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. |