Q2 2016: LexisNexis IQ® 2.1 Update 7 - 2.1.7.51 (May 4, 2016)

This update includes the new functionality of Signature Capture for InterAction IQ 2.1. This feature is only available in InterAction 6.2. If you are running InterAction 6.1, you can install this latest update to get fixes, but Signature Capture will not be activated.
 

This update addresses the following issues:

• Newly discovered knows relationships and scores were not being passed from IQ and created in InterAction. (55334)
• The system was only retrieving the first 200 contacts from the Exclusion Folder and when more than 200 contacts were linked into the folder it resulted in some contacts in the Exclusion Folder being mined.(56406)
• IQ Metrics report causing database exception SqlDateTime overflow' error. (54526)
• Signature Capture did not capture updates for a contact in the firm's list when the contact was private or unresolved in another user's contact list. (54035)
• Resolved an issue that occurred when an email address was changed on a contact that previously had an IQ score. (54053)
• Resolved the following exception that could occur: [2008] Unable to load items jdoe@abc.com (Contacts)...skipping - You must load or assign this property before you can read its value. (54036)
• Disabling Signature Capture causes error: [1009] Signature Capture feature must be enabled to activate the exclusion folder 'IQ No Contact Updates.' (54054)
• IQ is now supported with on-premise Exchange Server 2016.
• Enhancement: Performance improvements have been made to the export relationships phase of the IQ process. (55201)
• Enhancement: The 'Peak Communication' column has been removed from the IQ Score Report and a Back button added to the page. (54034)
• Enhancement: The default for the "Relationship Creation Setting" in the IQ Admin application was changed from 5 to 80. (54055)
• Enhancement: Improved capture of signatures with UK address formats and phone numbers. (53757)
• Enhancement: Improved capture of signatures with Canadian address formats and phone numbers. (53742)
• *Enhancement: Added a Job Title column with filtering to the User Management screen. (53959)
• *Enhancement: Suppressed generation of phone reformatting tickets in the DCM inbox when only format changes are captured for a contact’s phone number. (55229)
• **Enhancement: Added ability to search on the IQ Signature Capture user in the InterAction Windows Client DCM Inbox. (52964)

* This feature requires Application Server Update 6.20.55 or higher
** This feature requires Desktop Applications Update 6.21.12 or higher

What can LexisNexis IQ^® do for my organization?

• Click here for LexisNexis IQ^® details

LexisNexis IQ^® Resources

Download Documentation

• IQ User Guide
• IQ Installation and Configuration Guide

Version 2.1.7 Compatibility

While other configurations are supported, the IQ 2.1.7 product has been certified with these component versions:

IQ	InterAction AppServer	Microsoft Exchange	Other Components
2.1.7	6.20.53, 6.20.55	Exchange 2013	InterAction Desktop Applications Update 6.21.12 InterAction Database Update 55

Other supported configurations:

- AppServer 6.20.54

- Exchange 2010 or Exchange 2016

Configurations no longer Supported

The following configurations are no longer certified or supported:

Software Download (for InterAction 6.2 & 6.1 only)

• Please contact your sales representative for more information
• See IQ Installation and Configuration Guide for installation or upgrade instructions.
• Click here to download the update.

Links to other updates for 6.2 Customers:

• 6.2 App Server Update 57
• 6.2 Database Update 56.001
• 6.2 Desktop Applications 14

Update Requirements for 6.1 Customers:

• 6.1 App Server Update 52
• 6.1 Database Update 50.001

Update History

Update 5 / 2.1.5.97 (Oct 28 2015)

• Some emails were causing out-of-memory issues when attempting to process the email signature. (50881)
• Signature Capture was detecting signatures from the wrong contact on some emails with conversation threads between multiple recipients. (50981)
• Signature Capture was not using a contact's full display name from Exchange when attempting to capture the contact's email signature. (51850)
• A performance improvement has been made in the Scoring phase of the IQ process. (51910)
• The Export Failure Reasons column of the Failed Contacts.csv file was not listing the reasons why contacts were not exported to InterAction. (52013)
• The IQ Server was not checking for the correct version of the IQ Database. A version check is now done before the IQ Server starts. (52070)
• The Junk email folder in Exchange was being mined due to a naming convention issue.
• The InterAction IQ folder-specific Additional Field values for User Inbox and IA Contact ID were not updating for some contacts whose email signatures had changed.
• Data Change Management (DCM) Edit tickets were being generated to change the email address on existing InterAction contacts. (52310)

Update 4 / 2.1.4.29 (Sep 22 2015)

• UK email signatures were not being captured correctly. (51450)
• Some email addresses in a signature were not being parsed correctly during IQ signature capture due to an incorrect mailto: link within the HTML.
• Some email signatures from contacts linked into the IQ No Contact Updates folder were being incorrectly captured by IQ. (51847)
• DCM tickets were not being generated from contact updates originating from IQ signature capture. (52002)
• Contacts linked into the IQ exclusion folders in InterAction were not being excluded from Relationship Scoring and Signature Capture due to case sensitive matching of their email addresses. (52048)
• Contacts linked into the "IQ No Relationships & Scores" folder were being excluded from IQ Signature Capture. (52056)
• Contacts linked into the "IQ No Contact Updates" folder were being excluded from Relationship Scoring. (52059)

Update 3 / 2.1.3.31 (Sep 3 2015)

• Improved IQ's recognition of deleted or merged InterAction contacts to correct AppServer exception errors, which caused IQ error code [5020] - Unable to export score. (50231)
• Improved the company detection logic in IQ Signature Capture in order to prevent contacts from being disassociated from companies in InterAction. (51016)
• Improved performance in the Scoring phase of the IQ process. (51317)
• Duplicate DCM tickets are no longer created when email signatures are repeatedly enabled/disabled. (51638)

Update 2 / 2.1.2.77 (Aug 13 2015)

• New functionality - an IQ Metrics report is now available under the Dashboards & Reports area. This report will track the number of Captured Signatures, New Contacts, Updated Contacts, and New Relationship Scores. (50342)
• IQ Signature Capture now sends newly discovered contacts that have the highest score with a mined user to InterAction. (50393)
• The detection of email signatures from UK and Canadian addresses has been improved. (50647)
• Corrected an issue where anonymous relationships were not being properly tracked in IQ when using a version of the Application Server prior to 6.20.52. (51260)
• Corrected a timing issue between Microsoft Exchange and the IQ database, resulting in error code [4008] (Unable to save data for mined items). (51262)
• Fixed an issue regarding database permissions when upgrading the IQ database during the installation process. (51314)
• Resolved a data type error during the IQ database upgrade process when upgrading from a previous IQ 2.x version. (51316)

Update 1 / 2.1.1.49 (July 23 2015)

• Improved IQ's recognition of deleted or merged InterAction contacts to correct AppServer exception errors, which caused IQ error code [5020] - Unable to export score. (50231)
• Improved the company detection logic in IQ Signature Capture in order to prevent contacts from being disassociated from companies in InterAction. (51016)
• Improved performance in the Scoring phase of the IQ process. (51317)
• Duplicate DCM tickets are no longer created when email signatures are repeatedly enabled/disabled. (51638)
• New functionality - an IQ Metrics report is now available under the Dashboards & Reports area. This report will track the number of Captured Signatures, New Contacts, Updated Contacts, and New Relationship Scores. (50342)
• IQ Signature Capture now sends newly discovered contacts that have the highest score with a mined user to InterAction. (50393)
• The detection of email signatures from UK and Canadian addresses has been improved. (50647)
• Corrected an issue where anonymous relationships were not being properly tracked in IQ when using a version of the Application Server prior to 6.20.52. (51260)
• Corrected a timing issue between Microsoft Exchange and the IQ database, resulting in error code [4008] (Unable to save data for mined items). (51262)
• Fixed an issue regarding database permissions when upgrading the IQ database during the installation process. (51314)
• Resolved a data type error during the IQ database upgrade process when upgrading from a previous IQ 2.x version. (51316)
• Previously, IQ was reporting warning [5012] 'Unable to get Relationship Scores Object reference not set to an instance of an object' during the Exporting phase of the IQ process. This has been corrected. (50872)
• System improvements have been made in the manner in which IQ generates its output spreadsheets related to system resource management. (50882 & 50849
• Associating contact phone numbers labeled as 'Direct' through signature capture functionality has been improved. (50717)

New IQ 2.1 Release / 2.1.0.1462 (June 30 2015)

• New functionality - Signature capture feature included for the first time in this release.
• The unresolved relationship references spreadsheet file (UnresolveRelationshipReferences-YYYY-MM-DD-hh-mm-ss.csv) generated by IQ was not listing email address for some contacts. (48496)
• During an IQ in-place upgrade/installation, values for the Account Name and Account Password fields were being overwritten with default values. (49795)
• The IQ Process Dashboard was reporting alerts (code 5020) from the InterAction Application Server when attempting to create a relationship between contacts when that relationship already existed. (50223)
• While running the IQ process, there were instances of timeout errors (error code 4008) during the email mining process from Microsoft Exchange. (50224)
• When the Exchange Server was busy, error code 2008 (Unable to load items) was being generated during Exchange mining. To eliminate the error, IQ now retries the Exchange mining request. (50225)
• A SQL Server exception was being generated during the scoring phase of the IQ process. This has been corrected through an IQ database update. (50632)

Update 6 / 2.0.6.93 (Apr 15 2015)

• IQ was encountering error "[5000] IQMananger Exception Execute method Value cannot be null." during the mining process for InterAction activities. (48054)
• IQ was attempting to match email addresses from InterAction in a case-sensitive manner. This could result in an empty Score Report for a user. (48530/49061)
• "Known By" relationships were not being processed correctly. (48531/48115)
• During the IQ export process, when writing relationship data to InterAction, an error was being sent from the Application Server back to IQ. (48295)
• During the IQ database upgrade process, an error displayed while attempting to update certain database tables. (48495)
• The unresolved relationship references spreadsheet file (UnresolveRelationshipReferences-YYYY-MM-DD-hh-mm-ss.csv) generated by IQ was not listing email address for some contacts. (48496)
• IQ was previously counting the same email both in a sender's Sent folder as well as in the recipient's Inbox during the scoring process. (49113)

Update 5 / 2.0.5.5 (Feb 27 2015)

• IQ now supports MS SQL 2014. (47298)

Update 4 / 2.0.4.3 (Jan 15 2015)

• Processing of certain anonymous relationships was causing issues with calculating IQ scores. This issue has been corrected.(48086)
• Organizations now have the option to NOT create the SQL Server logins and users associated with IQ. This option is available when running the creation/upgrade script. (48118)

Update 3 / 2.0.3.25 (Dec 19 2014)

• In some cases, IQ scoring was not including InterAction activities between two contacts. (47936)
• Threading issue with checkSession. (47996)

Update 2 / 2.0.2.9 (Dec 5 2014)

• In some cases, IQ scoring was not correctly reflecting duplicate contacts that had been merged. (47578)
• Entries for the name of the Exchange Server in the HostRouting.xml file were case-sensitive. (47650)

Update 1 / 2.0.1.78 (Nov 10 2014)

• November 10th, 2014 - LexisNexis IQ^® 2.0.1 released

New IQ 2.0 Release / 2.0.0.326 (Oct 24 2014)

• October 24th, 2014 - LexisNexis IQ^® 2.0 released

Copyright 2016 LexisNexis. All rights reserved.