LexisNexis IQ® 2.1 Update History

The following issues have all been corrected in previous IQ 2.1 Updates.


 

Update 32 / 2.1.32 (May 20, 2021)

• Relationships and scores were not being sent to InterAction, if users had a secondary email address (i.e. Home) that contained a domain (i.e. gmail.com) that was part of a contact linked into the IQ No Relationships and Scores IQ folder. (191494)
• IQ has been modified to allow mailbox access using Impersonation with on-premise Exchange Server and basic authentication*. (178614) (4581)
• Private Outlook contacts in Contact sub-folders were not being excluded from Signature Capture and Relationship scoring. (202506)

*Requires a change to an IQ configuration file. Impersonation is disabled by default.


Update 31 / 2.1.31 (Apr 22, 2021)

• Non-mined users could still have relationship scores with contacts despite being disabled for IQ because they were included on emails, meetings, etc with the contact. The default behavior has been changed with this version of IQ. Relationships and scores will no longer be created in InterAction for users that are not enabled for IQ (Note: IQ can be modified to create relationships and scores for disabled users). (195821)
• Enhancement: IQ now has the ability to process single users and users in groups. (183618)
• IQ has been updated to use Microsoft .NET Framework 4.8*. (192286)
   

*Microsoft .NET Framework 4.8, or higher, needs to be installed on the IQ server.


Update 30 / 2.1.30 (Jan 28, 2021)

• Enhancement: IQ now has the ability to send daily IQ Processing Summary emails containing information regarding process results, configuration settings, and error & alert details. (191757)
• Modified the GetAddressExclusion call to eliminate the default 30 second SQL timeout. (191269 & 192123) (4699)

Update 29 / 2.1.29 (Nov 19, 2020)

• The following error can occur if IQ is on SQL 2014 (or lower): Unable to compute relationships - Operation failed. The index entry of length 1070 bytes for the index 'IDX_FilteredRawEvent_itemId' exceeds the maximum length of 900 bytes. (189466) (20599)
• High CPU utilization on the IQ Server occurred while processing the Company name during Signature Capture contributing to the following error in the IQ logs, "could not capture signature due to regex match timeout". (189931) (20605)
• Personnel to Personnel relationship scores were continuing to be displayed in InterAction after enabling IQ setting "Do not export personnel to personnel relationships". (189555)
• A stack overflow error occurred while processing html data during signature capture processing (189931) (20605)

Update 28 / 2.1.28 (Oct 15, 2020)

• Enhancements to the IQ Score Details report (171188):
• Filtering option now uses 'contains with' instead of 'begins with' on the following fields: Email Address, Name, Company Name, Job Title
• Ability to sort by the following fields: Score, Raw Score, Emails, Meetings, InterAction Activities, Last Communication
• The following fields have been added to the report: Company Name, Job Title and Raw Score
• Ability to filter users by the following status: Active, Inactive, Ineligible, Alumni
• Ability to export the information in .csv format.

Update 27 / 2.1.27 (Sep 17, 2020)

• Corrects an issue where the primary email address of a contact in a relationship is updated in InterAction causing IQ to become disconnected from the relationship and unable to update the IQ score. We introduced a procedure that runs as part of the Database Maintenance process that identifies and clears the IQ score from InterAction relationships that are no longer linked to a relationship tracked in IQ in this situation. Please ensure that the Database Maintenance Process is scheduled to run regularly. (177919)
• Corrects an issue where a contact in a relationship is linked into the 'IQ No Relationships & Scores' exclusion list and becomes disconnected from the relationship and unable to update the IQ score. We introduced a procedure that runs as part of the Database Maintenance process that identifies and clears the IQ score from InterAction relationships that are no longer linked to a relationship tracked in IQ in this situation. Please ensure that the Database Maintenance Process is scheduled to run regularly.(177919)

Update 26 / 2.1.26 (Aug 20, 2020)

• The User Inbox and IA Contact ID additional fields on the IQ Update Contact folder did not contain values for changes made to internal contact records (i.e. Our Personnel contacts). This was a side effect of having IQ option, 'Do not export personnel to personnel relationships’ enabled, and has been resolved. (14632) (19758)

Update 25 / 2.1.25 (Jul 16, 2020)

• In the IQ Admin portal, the threshold values for both Engagement Scoring and Signature Capture were being removed when the following error occurred: [4000] Database Exception SQL Exception. (181202) (20508)
• In some cases, IQ was not creating Knows relationships for contacts that were linked into the "IQ Contact Details" folder. (181247) (20509)

Update 24 / 2.1.24 (Jun 18, 2020)

• DCM tickets can be generated to change a contact's name with Suffix information from their email signature. IQ was failing to identify them as valid Suffixes. IQ has been updated to support all Suffixes defined within the InterAction database. (176786) (20437)
• Changes to address rules for eliminating the capture of partial addresses. (178788) (19846)

Update 23 / 2.1.23 (Apr 16, 2020)

• Modified IQ to support using Exchange Web Services (EWS) with Modern Authentication (OAuth 2.0) while accessing user mailboxes on Office 365 or Exchange Online. (174417) (20367)
• Corrected an issue where the Exchange Server alias was not being saved properly within the HostRouting.xml file. (176041) (20430)
• Corrected an issue where the Engagement Scoring value was being cleared under Feature Settings. (176358) (20287)
• Improvements to better identify company name information in e-mail signatures. (16131)

Update 22 / 2.1.22 (Mar 19, 2020)

• Signature Capture now supports phone formats where the qualifier is noted in parenthesis (i.e. (direct) xxx.xxx.xxxx), or is separated with a hyphen (i.e. direct-xxx.xxx.xxxx). (8485) (18286)
• IQ Score report may show "No user relationships available" for some users. (165380) (20247)

Update 21 / 2.1.21 (Feb 20, 2020)

• Revisions to a calculation performed by IQ that, in certain situations, prevented some information gathered by IQ from flowing back into the Data Change Management process due to the following error: [5010] Unable to Compute Relationships Divide by zero error encountered. (169228) (20321)
• Improvements to how engagement scores are decayed over time when there has been a lack of interaction, enabling the score to adjust more precisely in reflection of relationship strength. (170158) (20341)
• Windows Authentication is used when running the Publish_IQDB.cmd file even though SQL Authentication is selected. (167630) (20290)

Update 20 / 2.1.20 (Nov 21, 2019)

• Initializing a new IQ database on SQL Server 2016 generates error message "Error SQL72018: SqlDatabaseCredential could not be imported but one or more of these objects exist in your source." (169149) (20343)
• Corrected another instance that caused blank names to display in the Score report. (170335)(19900)

Update 19 / 2.1.19 (Oct 17, 2019)

• Score report may show blank email addresses and/or names. (16618)(19900)

Update 18 / 2.1.18 (Jul 18, 2019)
 

• The IQ Score report now includes an information icon that provides an explanation of the 'Last Communication Date' field. (16604) (19896)
• IQ may cause high CPU usage on the IQ server and require frequent server reboots. (162833) (20171)
• The 'Mine Unresolved' option is not retained for users after IQ runs. (164082) (20207)
• IQ Score report shows duplicate rows for the same email address. (8477) (19376)
• Corrected IQ so scores will properly decay over time. (65031) (20050)

Update 17 / 2.1.17 (Jun 20, 2019)

• The Metrics Report cannot be loaded and displays error message "Bad response from the server". (10226)

Update 16 / 2.1.16 (May 16, 2019)

• IQ now supports SQL 2017 (162930)
• Incorrect SQL call used in IQ causes issues creating IQ Score Report (85666)

Update 15 / 2.1.15 (Apr 18, 2019)

• The GetContactsByEmail procedure call of the IQ sync has been re-engineered for improved performance. (15373)

Update 14 / 2.1.14 (Dec 20, 2018)

• Users are being set to inactive in IQ. (16325)
• Fix for the following error message: "Error 14 IQManager.ContactsExportHandle [4008] Unable to save data Database_Exception Description: Value cannot be null." (17952)

Update 13 / 2.1.13 (Jul 9, 2018)

• The following error was fixed: "Cannot insert the value NULL into column optInNCR". (14147)
• The following error was fixed: Exchange.FoldersMonitor [2000] Exchange Exception MiningWorker method InnerException: An item with the same key has already been added. (14500)
• Fixed the following error that could happen while trying to view score reports: [4000] Database Exception Execution Timeout Expired. The timeout period elapsed prior to completion of operation or the server is not responding. (15656)
• The following alert was fixed: Exchange.ExchangeHandler [4000] Database Exception Procedure or function 'SaveExcludedExchFolder' expects parameter '@folderName', which was not supplied. (14888)
• Enhancement: Contacts that have been suppressed (deleted) in the InterAction database are also now deleted from the IQ database.

Update 12 / 2.1.12 (Mar 30, 2018)

• Enhancement: The IQ server configuration file was modified to purge the Incomplete Contact Excel File (Incomplete_Contacts.xls) after 7 days.
• *Enhancement: The firm can optionally require an email and/or phone number in addition to last name when adding/creating new contacts.

*This feature requires multiple components to be updated.  See the Data Minder Update for details.


Update 11 / 2.1.11 (Oct 27, 2017)

• Optimized the mining of Outlook subfolders. (70851)
• Phone reformat tickets will no longer generate because the format of the phone on the signature is different than the auto-format set within InterAction. (70869)
• Enhancement: Reduced the generation of some unnecessary Address Reformat and Address Change tickets. (71448)
• Enhancement*: Includes the New Contact Review feauture that can allow users to review new contacts created by IQ Signature Capture. 

* This feature also requires Database Update 62_001, Application Server Update 6.20.64, Admin Update 6.21.24, and Desktop Update 6.21.24.

Update 10 / 2.1.10 (Mar 31, 2017)

• Enhancement*: There is now an option in IQ to exclude scores for Personnel to Personnel relationships. (53749) 
• Enhancement: The version number of IQ now shows at the top of the IQ Admin portal webpage. (70262)
• InterAction is now supported on Windows Server 2016. (67515)
• InterAction is supported with SQL 2016 AOAG (Always On Availability Groups). (67758)

Additionally, the Create a knows relationship when calculated strength is at least setting was moved to the Features Settings page under the Engagement Scoring feature from the Mining Configurations page. This setting is used to specify the minimum engagement score for which IQ will create a knows relationship in InterAction.

Update 9 / 2.1.9 (Dec 15, 2016)

• New setting on the User Management page of the IQ Admin application to override the exclusion of unresolved contacts.  When this setting is selected for a user, or multiple users, IQ will send new contacts to InterAction that have not yet been shared with the firm, because they are unresolved in an InterAction user's contact collection.

• Ability to specify normalization rules for job title and state/province fields.  Once the rules are defined, when contact data is captured from email signatures it will be normalized before tickets are created in InterAction DCM (requires the InterAction 6.20.61 AppServer, 6.20.59 Database and 6.21.18 Desktops Applications updates).

• New control in the IQ Admin application to specify a minimum engagement score for sending a new contact to InterAction. When a mined user's score with a new contact equals or exceeds the minimum score set, IQ will send the new contact.

• Ability to identify companies IQ should always send new contacts to InterAction for by linking them into an InterAction folder. This folder over-rides the minimum engagement score setting.

• Multi-value IA User Engagement additional field on new contact from IQ which lists first and last name for each InterAction user communicating with a new contact [up to 10 users] and their engagement scores.

• Suspect address tickets will no longer be created in InterAction DCM when a captured signature does not contain a country.

Additionally, the Create a knows relationship when calculated strength is at least setting was moved to the Features Settings page under the Engagement Scoring feature from the Mining Configurations page. This setting is used to specify the minimum engagement score for which IQ will create a knows relationship in InterAction.

Update 8 / 2.1.8.52 (Sep 15, 2016)

• IQ now matches the mined user's email address to the firm contact's primary Email address to correct issue where a mined user’s score report would be empty because the mined user had more than one email address in InterAction. (57569, 54584)
• Removed maximum number restriction on contacts returned to IQ from InterAction to correct inconsistent results between mined users score report (no scores) and InterAction relationships with scores. (57340)
• IQ now supports fully qualified domain name and implicitly defines the container based on the domain name (example: domain.sub1.sub2 equates to container names CN=domain, CN=sub1, CN=sub2). (58060)
• Corrected issue where ExcludedElectronicAddresses.csv did not get created when there were only unshared contacts in User lists. (59256)
• *Enhancement:  A new option has been added in the IQ Administrator application to set a minimum engagement score threshold for sending new contacts.  IQ will only send the new contact to InterAction once a mined user’s score with the new contact equals or exceeds the minimum score defined. (58887)
• **Enhancement:  A new “inclusion” folder has been added in the Windows Client.  Company contacts can be linked into the IQ Always Send New Contacts folder to allow firms to always receive new contacts discovered by IQ for certain target companies. (58921)
• Enhancement:  The Create a knows relationship when calculated strength is at least option was relocated from the Mining Configurations page to the Feature Settings page under the Engagement Scoring feature. (59462)
• Enhancement: IQ Server installer now automatically detects OS architecture to run seamlessly in x86 or x64 using a single executable. (58955)
• ***Enhancement: A multi-value additional field has been added on new contacts from IQ. The IA User Engagement field lists the first and last name and IQ score for up to ten InterAction users communicating with a new contact (58453)
• Enhancement: When no country is captured in an email signature with a US, UK or Canadian address format, suspect address tickets will not be generated in the InterAction DCM inbox. (58440, 51800)

Update 7 / 2.1.7.51 (May 4, 2016)

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

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

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 2017 LexisNexis. All rights reserved.