| Issue Number | Problem Description | Solution Notes |
|---|---|---|
| 418 | Campaigns exported using the Campaign tool have incorrect date values for campaign expiration date, campaign creation date, etc. | |
| 921 | The follow-up interaction does not have any information regarding the content that should follow when exporting the campaign. | |
| 1020 | When cloning a campaign that is a 'subscribe' campaign with one main message and three follow-up messages, the follow-up messages are orphaned, disassociated from the main message, without any way to delete them. | When cloning the campaign, the follow-up messages are no longer orphaned and are associated to the main message |
| 1126 | When clicking on the "Message Debug" link to adjust content for a campaign, the edit panels are not resizable as expected. | |
| 1540 | It was discovered that tooltip help balloons remained on the screen where they were initiated. | |
| 1556 | When creating content for event-triggered campaigns, Connect does not allow the upload of XSL files. | The solution adds file validation based on the jmimemagic API. It checks if the mime type of an uploaded document is plain text. If so, the file is allowed for processing. Else, the file is rejected. |
| 1568 | When uploading an invalid XSL content file, the system saves it to the content repository and refuses to save the content record, without the ability to edit it. | The solution applied now has Connect skipping the content validation on editing and saving Campaign content. The content validation now occurs on saving uploaded content on the content repository and launching the campaign message |
| 1569 | When empty content is created for an HTML content link, the created file contains invalid HTML. | |
| 1570 | Invalid XSL is being generated when empty content is created for a Text Content link. | |
| 1582 | The "Use Default Deployment Settings for Cluster" checkbox is not working when attempting to create a new deployment and add machines. The fields below the checkbox remain greyed out and the system will not allow the user to save changes since Connect believes the fields to be blank. | Following the upgrade of the jquery library, this issue was discovered. As a result, the event handler on the checkbox's change event did now function with existing code. The event handler register mechanism was changed to solve the issue. |
| 1583 | An error occurs when running the 'updatedb' on MSSQL server. | |
| 1589 | An error message validating incorrect XSL content was ambiguous to the user. It stated that the "Content URL is not validated." and did not indicate the presence of incorrect XSL content. | |
| 1590 | An error message occurred when content was created with valid XSL but no parameters defined. Connect created a validation error stating that there was no parameter associated with the XSL content, which is erroneous since parameters are not mandatory for XSL content. | |
| 1591 | The 'Rollout Message' and 'Stage Message' actions remained available for a message that had XSL content that was initially valid and then was altered to be invalid XSL. | |
| 1599 | When content with invalid XSL is saved, currently no message is displayed to the user. The user discovers this fact when the content is assigned to a message. | |
| 1604 | It appears that if content of 'XSL Template' type has an invalid XSL file, uploading new content with 'good' XSL is not uploaded. | The solution now validates only the content type the user is creating or uploading, instead of validating all of the content types available and set to the campaign content. |
| 1607 | A null object error occurs when content is attempted to be edited by using the message content link on the Messages page. | |
| 1630 | There is a desire to revert some of the aspects of the 10r53 UI layout. In particular, the vertical left navigation column should be changed back to a second level of horizontal tabs. As well, the multi-page forms that use large horizontal title bars force the user to scroll. These should be reverted to horizontal tabs. These changes impact the Campaign Content, Customer Editor and Deployment Editor pages. | |
| 1652 | There appears to be an issue with reports in 10r533 on AIX 6.1/WAS 7 and could not be displayed. | |
| 1653 | When a user logs out of Connect, they are directed to the login page. This is not appropriate in an SSO environment. A parameter has been introduced providing a URL for the user to be directed to once logging out. | A new string system parameter is now in the product which takes a URL value as input. The URL can be absolute or relative. For relative URLs (e.g. specifying /CompanyAdmin/Index for a company admin page) the system will display the login page on logout operation as the user session is terminated after the logout operation and redirect to the company admin page. For absolute URLs, the system redirects the user to the specified URL. |
| 1694 | It was discovered that the launch schedule shifts by six hours once saved. | |
| 1696 | When drilling down into the Campaign Counts report, the report only displays the unique opens and not the total opens. As well, the first click field in the Opens report should display "first open" and look at first read and not first click. | |
| 1704 | Connect has displayed inconsistencies in the UI between Chrome and IE11. | |
| 1708 | The 'Calculate All' button is not working in IE11. | |
| 1737 | The Drill Down Report has display issues including 1) the Alt Customer ID not displaying in full as it is truncated, 2) the date and time of the report id showing as the server time stamp, and 3) when first opening the report, the time stamp is different from subsequent opens. | |
| 1738 | Connect has displayed the incorrect date and time value in the results of the Campaign Drilldown report. | |
| 1764 | In the 'Report Options' section of the Reports page, the dropdown for campaigns is not scalable if the user has several campaigns. | This has been replaced by a suggestion box, which by default displays the first 10 entries. Once the user enters search terms they are displayed in the box. |
| 1863 | Connect has been modified to allow TIBCO-based JMS connections to allow SSL and non-SSL based connections. |
| Issue Number | Problem Description | Solution Notes |
|---|---|---|
| 927 | Customers from different segments in the same imported conversation are receiving follow-up messages intended for only one segment. | |
| 1060 | On a new installation of 10r5.3, the newly created admin account has a profile_id of 'null' in the user_master record. | The newly created admin profile has the appropriate value in the user_master record. |
| 1079 | The UI is behaving poorly when attempting to import a campaign with the 'Import Campaign' buttons and functions displaying at the bottom of the page with a large blank space in the page. | Correct UI layout in browser. |
| 1224 | An APNS unsubscribe error occurs in the MailProcessor log (Error code = 8 Invalid token). | |
| 1351 | On the Campaign Results dashboard, there is no data being reported for unsubscribes and spam FBL. | |
| 1356, 1357 | An NPE is thrown in Conversation Manager. | |
| 1370 | Unable to delete multi-address preference values in the Customer Editor. | |
| 1375 | Users with "View Reports" privileges are unable to view the Campaign Results tab. | Users that only have report viewing privileges can now view campaign results. |
| 1377 | When the number of retries for an email has been exhausted, the application should update the status_code to '107' and record the last SMTP error code received in the customer_queue. | If a 4XX status code is returned, the domain is disabled and the records are marked with a status_code of '109' and record the error from the receiving server. 5XX codes are not handled in this manner. |
| 1378 | The default mailfarm is not available in multi-tenant mode. The system should use the default mailfarm if the 'Use DMS' system parameter is set to 'False'. | |
| 1407 | Session cookies do not have HttpOnly flag. | On WebSphere, the HttpOnly flag must be set in the WebSphere Console and cannot be set in the web.xml file. On the other hand, in JBoss the HttpOnly setting must appear in the web.xml file. See https://www.owasp.org/index.php/HttpOnly for more information. |
| 1408 | The cache-control and pragma HTTP Headers have not been set correctly. | See https://www.owasp.org/index.php/Session_Management_Cheat_Sheet#Web_Content_Caching. |
| 1409 | The Anti-MIME-Sniffing header X-Content-Type-Options is not set to 'nosniff', allowing older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body. | The X-Content-Type-Options header is now included and 'nosniff' is set for all pages. See https://www.owasp.org/index.php/List_of_useful_HTTP_headers. |
| 1410 | The X-Frame Options header is not included in the HTTP response to protect against 'ClickJacking' attacks. | See http://blogs.msdn.com/b/ieinternals/archive/2010/03/30/combating-clickjacking-with-x-frame-options.aspx?Redirected=true |
| 1417 | Application server needs to be restarted after changing MS.SimpleEmailServer system parameter | |
| 1428 | System parameter changes are not propagating to the deployment machines properly. | |
| 1443 | An error appears in the logs when more than one Tracker domain exists. When the components are restarted on deployed nodes, a critical KC error is thrown. | |
| 1448 | A critical error occurs in the Profiler, preventing the system from updating the database with data from the storage files. | Caused by a malicious user-agent string that was larger than the database field length. |
| 1461 | Add tokens to all forms to prevent Cross Site Request Forgery (CSRF) attacks. | See https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF). |
| 1462 | Update jQuery library to latest. | Earlier versions of jQuery have security vulnerabilities. See http://www.cvedetails.com/vendor/6538/Jquery.html. |
| 1465 | Eliminate stack traces in UI error pages. | |
| 1467 | Scan uploaded files to screen out malware. Delete all uploaded files after errors or after conclusion of processing. | Uploaded files (CSV data files, Message content files, and XML campaign and survey import files) are scanned to ensure that executable files are rejected and that that only text files are accepted for upload. In addition, the application ensures that all uploaded files are deleted after processing has completed, after an error is encountered with the file, or after the user session expires. |
| 1468 | UI code updated to enforce use of HTTP POST on controller modules. | Previous versions allowed use of HTTP GET and POST. |
| 1472 | Unsubscribe form processing modified so that customer lookup is based on the email address and the customer_id. | Prior versions only used email address which can return multiple records. |
| 1477 | Profiler error on MySQL | Caused by incorrect data type in MySQL schema |
| 1478 | Fix case-sensitivity issue in domain cache | |
| 1479 | Fix issue with incorrect connection counts in domain connection pools | |
| 1482 | An exception occurs when accessing the "Mail Sent per Domain" report with no data. | Added "no data" handling to report definition |
| 1491 | Tune connection pools so that encrypted connections will be used for non-secure traffic. | Prior implementations only used non-encrypted connections for traffic that did not require encryption, which limited throughput on mixed workloads. |
| 1492 | The 'maximum message per connection' parameter was not being overridden by the domain configuration table. | |
| 1495 | Fix assert failure in ConversationManager when sending a normal campaign with a mix of single and multiple addresses. | |
| 1500, 1503 | The maximum messages per hour function is being ignored and the maximum messages per hour is being exceeded. | |
| 1515 | Unsuccessful logins are not being stored in the USER_LOGON_INFO table. | |
| 1525 | Errors occur in the purge scheduler, appearing to be a multi-address related issue with customer_queue purging. | The Message_history index, restricts the cq.customer_id, cq.instance_id, cq.event_queue_id to be unique. However with the customer_queue table, the purge stored procedure querying from is not unique because of the new multi-address delivery channel feature. The purge code and message_history table were not handling this operation properly when using APNS and GCM push with multiple device tokens/device registrations per customer (i.e. multi-address preferences). |
| 1532 | XXE Vulnerability in Event Listener | External entity resolution disabled in XML parser. See https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing. |
| 1533 | XSS vulnerability due to missing HTML encoding in certain UI fields. | |
| 1540 | Tooltips do not disappear. | Corrected javascript code so that tooltips disappear when mouse leaves tooltip region. |
| 1548 | Dates for log files cannot be selected in log viewer section of deployment editor. | |
| 1550 | The Mail Sender is not able to start in a Windows network without DNS/RDNS mappings. The code now uses the default hostname if no mappings are present. | Commonly occurs in Windows networks behind a firewall. |
| 1556 | "Create XSL Content" for Event-Triggered Campaigns does not allow upload of XSL files | |
| 1557 | Creating a new "blank" XSL content object for an event-triggered campaign does not create valid XSL content. | The code created HTML or text content, which is not valid XSL. |
| 1561 | UI crash in Campaign -> Content -> URL -> "Create Content" when no content repository is selected. | Add a validation which checks the mandatory Repository ID field. If there is no Repository ID selected for the content, it will display a validation violation message and prompt the user to select a repository. |
| 1565 | When campaign messages are scheduled for rollout, the scheduled date is set incorrectly when multiple messages are scheduled at the same time. | |
| 1566 | An NPE is thrown when failing to load an FTPS certificate. | Null checks and better diagnostic messages added. |
| Issue Number | Problem Description | Solution Notes |
|---|---|---|
| 920 | Campaign Importer: Segment not set properly on imported Messages | |
| 1201 | ETL2: Email-Based Data Loader was not handling mixed-case email addresses properly | The CUSTOMER_MASTER table has two fields: ACTIVE_EMAIL_ADDRESS, with mixed case, and EMAIL_LOWER, with lower-case. The email-based data loader was matching incoming records against ACTIVE_EMAIL_ADDRESS instead of EMAIL_LOWER. If the email-based data loader has been used (versus the ALT_CUSTOMER_ID data loader) then scan the customer table for duplicate records as described in Managing Duplicate Customer Records. |
| 1327 | Max Connections to Domain setting was being exceeded in outbound SMTP | |
| 1341 | Add Segment name to Campaign Drilldown reports |
| Issue Number | Problem Description | Solution Notes |
|---|---|---|
| 76 | The Campaign Counts report does not show staging messages | |
| 353 | Event Loader / KCXML does not handle inactivated customers property | When receiving a new event, Connect ensures that both the Customer is active and the relevant subscription is active. The ETL2 package (based on the Informatica ETL package) did this. The KCXML code in the Event Loader did not. Adverse impact is that events to inactive customers could be delayed and not sent until a long time after first submitted. |
| 587 | The database update action requires database user to have permission on USERS tablespace on Oracle. | Survey tables were defined in the USERS tablespace on Oracle. |
| 606 | Connect hung on processing storage files | CONNECT now can be configured to give up on bad storage files after a certain number of retries. New system parameter: "Number of Times to Retry Storage File". Default to 0; 0 means retry forever. (This is current behavior.) Sysparam > 1 means retry this many times. When giving up on a storage file, move the file to a subdirectory of the storage dir, log it, and send an email alert. |
| 644 | Help link in UI does not behave as expected | Currently the UI retrieves the help URL and forwards the information to the end user but unfortunately for some customers the GUI node doesn't have access to the internet. The help should open a new window and point the user to the help URL since they'll have access to the internet. |
| 656 | Campaign Results page should default to previous 24 hours | |
| 661 | Ambiguous error message in survey fields page | Error message now specifies which survey field caused the error. |
| 685 | JBoss UI goes down after Connect shuts down all nodes in UI | CRM Monitor on Windows was killing the JBoss Java process in addition to the CONNECT processes. |
| 686 | An NPE is thrown in RealtimeViewer | |
| 688 | Use ignorecase for windows SFTP deployments | |
| 690 | Acknowledge individual JMS message by using dedicated session | Event Loader crashes could result in lost messages due to properties of the JMS API. |
| 693 | The user can delete attribute used in survey | |
| 694 | Unable to delete customer preference | |
| 695 | The calculate button in message rollout does not show the results until refreshed | |
| 696 | Error when exporting HTML Survey after import | |
| 711 | Info and targeting pages do not lock after launch | |
| 712 | Campaign results are not available after message expires | |
| 722 | Event Listener should only lookup Active Event based campaigns | Prior to 10R5, duplicate campaign names were not permitted. This restriction was relaxed in 10r5 so that campaign names can be reused when campaigns expire or are deleted. The code that processes incoming KCXML messages was not handling the case where two campaigns with the same name exist, and one campaign is expired and one is not. |
| 737 | Per-deployment monitoring needs improvement | COUNTER_HISTORY data records are now linked to deployment records |
| 776 | Error during JMS configuration with OpenMQ | |
| 789 | OutOfMemoryError error in DB Manager when purging large data sets | |
| 793 | A NPE is thrown when trying to stage a message after staging a message to a deleted group | |
| 794 | Handle non-text JMS messages | Handle all JMS message classes. |
| 810 | MySQL 5.6 index create failure: Specified key was too long; max key length is 767 bytes | MySQL behavior changed in version 5.6. Index definitions that worked in 5.5 broke in 5.6. |
| 814 | Email & SMS Double Permission handling broken | |
| 830 | Unable to include unsubscribeme merge tag in follow-up campaign | |
| 836 | Wrong count when using random segments with conversation larger than 4M | |
| 839 | Missing CONNECT_SCHEMA_NAME from etl2_config table | Connect installation does not create the column CONNECT_SCHEMA_NAME (Varchar2 100byte) in the etl2_config table |
| 849 | Error 500 when saving recency filter in segmentation model editor | |
| 858 | Do not stage messages with content validation errors | . |
| 866 | Japanese characters do not export to CSV file from reports | |
| 881 | Customer search by Birth Date only returns first record | |
| 883 | Runtime Exception when the content has URLs with merge tags and escaped HTML characters | |
| 884 | alt_cust_id column is getting truncated in Click Report | |
| 893 | Segmentation counts and exported customers do not match | |
| 896 | Malformed HMTL content received by customer | Error occurs when same content URL is used for HTML and Text content. |
| 898 | customer_queue rows not purged for expired and deleted campaigns also | Purge deleted campaigns |
| 899 | Error when trying to send email reports | |
| 911 | Edit campaign without Create/Edit option | Users with "View Campaign" and without "Create/Edit Campaign" security profiles were allowed to edit campaigns. |
| 913 | Province field not visible from UI | CUSTOMER_MASTER table has a PROVINCE field that is not accessible from the UI. Workaround was to use the STATE field instead. |
| 914 | Email backlog prevents staged emails from going out. | When Connect looks to target customers the query used did not take priority_code into consideration. |
| 916 | Segment custom value not working for campaign import/export | |
| 917 | Attribute import maintains import value for ext_table_attr_value | |
| 921 | Follow-up interaction does not have any information regarding what content to follow when exporting campaign | Campaign import/export was not handling follow-up messages properly. |
| 923 | Follow-up parent message missing after cloning campaign | |
| 931 | SocketException error when using encrypted connections between deployed nodes. | |
| 954 | Cannot create main message after first was deleted | |
| 960 | Bounce campaign message not sent | Error in test case T2454-Use Case: Resend Bounced Message on Different Cluster |
| 964 | Disable cert check on TLS | Added a system parameter (MS.CheckMailServerCertificate) that controls whether TLS certificate checking is disabled when sending campaign messages that have Force-TLS selected. |
| 969 | Multitenant: Redundant Administrator Profile is created every time when you create a new company | |
| 973 | No row inserted in UNSUBSCRIPTION_HISTORY when instance not found | Code modified to save a record even if the instance id part is invalid. |
| 989 | Unable to save default effective date from rollout page | Rollout dates are assumed to be saved in server local time. Code was not handling the case where client time zone did not match server time zone. |
| 993 | FtpFailureException on update deployment or reinstall | Occurs with COPSSH on Windows |
| 994 | Unable to create segment using birthdate attribute | Corrected date/time parsing code |
| 995 | Error messages that contain ' character are not correctly displayed | |
| 996 | Failure when duplicating segment model or audience model | |
| 997 | Debug XSL Content: NPE is thrown when generating xml without filling in parameter | |
| 1002 | Drilldown reports don't show results for the proper time interval | |
| 1004 | Surveys requires privileges on tablespace 'USERS' | |
| 1005 | Campaign results filter remains active after refresh | |
| 1006 | Searching customers by gender field doesn't work | |
| 1010 | NullPointerException on remove delivery channel from deployments | |
| 1015 | Workaround for Tibco EMS JMS "prefetch not disabled" | |
| 1016 | Birth date assigned by default when creating a new customer | When creating new customer Birth Date is set by default at actual time. |
| 1020 | Cloning campaign with follow-up messages creates orphans | |
| 1023 | An NPE is thrown in tracker log when handling invalid URLs | |
| 1064 | Failed login with bad password causes an NPE | |
| 1091 | An NPE is thrown when creating APNS send handler without certificate | APNS configuration UI now requires certificate. |
| 1092 | APNS JSON parser is too restrictive | JSON validator in APNS delivery channel was rejecting valid APNS messages. |
| 1100 | Parameter to disable XSS breaks staging ET campaigns | The code to prevent cross-site scripting attacks escapes incoming XML markup. This breaks staging messages for event-triggered campaigns that use ExternalXML. The UI now does not escape ExternalXML data when it is input, and ensures that it is not displayed in the UI. |
| 1130 | Message text too long for push event | Code was assuming that short text content in push events needed to conform to the limitations of the SMS channel. |
| 1143 | SMPP bounce reply handler not handling SMS bounces | Some SMPP gateway providers are inconsistent in how they format SMPP Message IDs in reply messages. |