Release Notes

• Enhancements• Resolved Issues• Current Issues• Release Information

LAW PreDiscovery®, Version 6.12.106

No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical,including photocopying, recording, or by any information storage or retrieval system, without permission.

While the information contained herein is believed to be accurate, this work is provided "as is," without warranty ofany kind. The information contained in this work does not constitute, and is not intended as, legal advice.

LexisNexis and the Knowledge Burst logo are registered trademarks of Reed Elsevier Properties Inc., used underlicense. PreDiscovery is a registered trademark of LexisNexis, a division of Reed Elsevier Inc. Other products orservices may be trademarks or registered trademarks of their respective companies.

© 2016 LexisNexis. All rights reserved.

CaseMap®Concordance®LAW PreDiscovery®LexisNexis® Early Data AnalyzerLexis® DiscoveryIQ

LAW PreDiscovery®Version: 6.12.106Release Date: October 7, 2016

LAW PreDiscovery Release Notes

3Contents

3

© 2016 LexisNexis. All rights reserved.

Table of Contents

Chapter 1 LAW PreDiscovery 6.12 Release Notes 4

Chapter 2 Enhancements 5

Chapter 3 Known Issues 5

Chapter 4 Release History 10

Chapter 5 Copyright Information 11

Index 0

Release Notes4

© 2016 LexisNexis. All rights reserved.

LAW PreDiscovery 6.12 Release Notes

October 7, 2016

Version 6.12.106

The LAW PreDiscovery Release Notes provide a list of new features, resolved issues, andknown issues in LAW PreDiscovery® version 6.12.106. The current issues may be addressed inan update or other future release of LAW PreDiscovery.

What’s New

Known Issues

Release Information

You can subscribe to an RSS feed that announces releases and updates for LAWPreDiscovery and Early Data Analyzer.

The URL for the RSS feed is:

http://help.lexisnexis.com/litigation/ac/ac_portal/LAW_EDA_RSS_Feed.xml

The following procedures for Outlook 2010 are provided for your convenience. For otherRSS subscription applications, consult respective documentation for the application.

To create a feed subscription via Microsoft Outlook 2010Perform either of the following:

1.Right-click RSS Feeds in navigation pane.

2.Choose Add a New RSS Feed.

3.Paste the above link into the New RSS Feed dialog that appears.

4.Click Add.

Or

1.Click File > Account Settings > Account Settings.

2.Click on the RSS Feeds tab.

3.Click New.

4.Paste the above link into the New RSS Feed dialog that appears.

5.Click Add.

6.Click Close.

In Outlook, any notifications will appear in the RSS Feeds area of the navigation pane.

LAW PreDiscovery 6.12 Release Notes 5

© 2016 LexisNexis. All rights reserved.

Enhancements

Enhancements - LAW PreDiscovery 6.12.106

Annotations and redactions

Upon TIFFing and direct export to LAW PreDiscovery, both the HasAnnotation andHasRedaction fields in LAW PreDiscovery are updated to Y if any redactions were applied tothe file in DiscoveryIQ. If only annotations were applied to the file in DiscoveryIQ, only theHasAnnotation field is updated to Y.

Export to Concordance Desktop

LAW PreDiscovery can now export to Concordance Desktop.

Import

Null characters are now removed from email metadata during ingestion. This enhancement,which applies to all methods of export from Early Data Analyzer to LAW PreDiscovery, helpsto prevent issues when importing email into LAW PreDiscovery.

NIST

LAW PreDiscovery now uses version 2.53 of the NIST list.

Validate endorsements

LAW PreDiscovery now offers a process that allows you to validate endorsements added toheaders and footers. After endorsing, go to the File menu, select Administration, and thenselect Scan for Errors. Select the Validate Endorsed Images check box and click Begin.See the Scanning for Errors and Endorsing Headers and Footers sections of the AnswerCenter for more details.

Known Issues

Release Notes6

© 2016 LexisNexis. All rights reserved.

Current Issues - LAW PreDiscovery 6.12.106

Notes for Reviewers: Yellow highlighting indicates material that must be updated before

publication. Green highlighting shows items that were added for the upcoming release.

Technical Writer: Be sure to remove all highlighting before publication.

Category Issue Found InBuild #

ResolvedIn

Build #

Antivirus AVG Antivirus software may misidentify LawReportLib.dllas malware. 216388 - found in 6.10.194

6.10 194

Batchprocessin

g

We have corrected an issue related to splitting PDF filesby bookmarks. LAW PreDiscovery was displaying TIFF filesin the image extension column but not retaining the TIFFimage. Image extensions are now cleared after splittingPDFs based on bookmarks and the TIFF images areretained. 211835

6.6 14

6.10 192

6.11.108

Batchprocessin

g

ICS body content is now captured during the batch TIFFprocess. 212128

6.9 125 6.11 108

Batchprocessin

g

LAW PreDiscovery no longer places "UNKNOWN" in theheader during the batch TIFF process for MSG files.215214

6.10 194 6.11 108

Batchprocessin

g

The batch TIFF process can now produce TIFF images ofVCF files that contain Chinese characters.

6.9 125 6.11 108

Deletion When emails were deleted from LAW PreDiscovery, thebody of the email was not being removed. This issue hasbeen corrected. 193266

6.7 143 6.11 108

EasyPDFand

InternetExplorer

11

Text can become illegible on images of MHTML messagestiffed using EasyPDF and Internet Explorer 11. 212275 -found in 6.10.194

6.10 194

ED Loader Custom page level field values are not carried over asexpected when importing a LAW PreDiscovery case intoanother LAW PreDiscovery case. 215539 - found in6.10.19 and 6.11.68

6.10 195

6.11 68

ED Loader We have corrected an issue that was preventing EDLoader from properly processing EML files. 214905

6.10 194 6.11 108

Endorsement

The image viewer does not display endorsements forsome documents that have been endorsed outside ofLAW PreDiscovery. 212532

6.9 125

Export When exporting data from LAW PreDiscovery to aSummation DII, tokens are not exported to the DII loadfile. This issue only affects data obtained from an EarlyData Analysis LAW Direct export. 220349 - found in

6.11 110 6.12 106

Known Issues 7

© 2016 LexisNexis. All rights reserved.

Category Issue Found InBuild #

ResolvedIn

Build #

6.11.110 MAY BE FIXED in 6.12

Export When exporting a PDF with at least one attachment usingthe PDF Conversion and Combine Parents/Attachmentsoptions, the attachments are now correctly merged.220464

6.10 194 6.12 106

Export (Native-only export) An error condition can occur whenexporting using the option to include natives only fortagged documents. This happens for all documents thatdo not have a value in the custom field used as the filenaming scheme for natives. 212968 - found in 6.10.194

6.10 194

Export We have addressed an issue that caused an error whenexporting raw images with LZW compression. 195127

6.8 133 6.11 108

Export Text encoding settings have been improved to preventUnicode settings from corrupting files in LAWPreDiscovery. 216292

6.10 195 6.11 108

Export When the exported text exceeds the ConcordanceDesktop allowable limit of 12 MB for a field, the excesstext will be entered into the next incremental field up to amaximum of six fields. For example, if the first text field isLAW_OCR_01, the first 12 MB of text goes into that field.The next 12 MB of text goes into LAW_OCR_02 and soforth until LAW_OCR_06. If there is still text to be stored,an error message is logged indicating that the text sizeexceeded maximum space available and data wastruncated.220304

6.12 106

Export The @FULLTEXT DOC token is placed below the first line inSummation DII, which may cause issues upon import inSummation. 208157

6.9 125

Export We have corrected an issue that occurred if one of thefields imported from Early Data Analyzer via LAW DirectExport into LAW PreDiscovery included a null stringterminator. Data in SQL Server fields is no longertruncated due to the way SQL Server handles null stringterminators. 220193 - defect workaround fix

6.11 110 6.12 106

Export When exporting a PDF with at least one attachment usingthe PDF Conversion and Combine Parents/Attachmentsoptions, the attachments are now correctly merged.220464

6.10 194 6.12 106

Extraction ZIPX files currently do not extract properly. Contents arenot extracted and there is no error message to indicatethat the contents are missing. 218803 and 221273

6.10 194 6.12 106

Extraction By default, LAW PreDiscovery does not retain the PDFportfolio container. However, you can extract a PDFportfolio container file by going to theEDLoader.case.config.ini file and changing theOLE_IncludePDFPortfolioContainer property value to 1.Then run ED Loader with either the Enable compound

6.10 194 6.12 106

Release Notes8

© 2016 LexisNexis. All rights reserved.

Category Issue Found InBuild #

ResolvedIn

Build #

document extraction on all supported file types or theRestrict compound document extraction to PDFportfolios option selected. 218251 - found in 6.10.194

Extraction PowerPoint files created with older versions ofPowerPoint for Mac and have Excel and/or PowerPoint forMac files embedded in them now extract as expected.222963

6.11 110 6.12 106

Extraction Documents embedded in RTF files are now extracted uponingestion. 212133

6.9 125 6.11 108

Extraction We have corrected an issue that caused random text filesto be generated in the $EDD folder. 215496

6.10 196 6.11 108

Extraction If there are issues when extracting RAR files that haveembedded ZIP files, an error message will bedisplayed.215267

6.10 194 6.11 108

Hashing The contents of the Attach field have been corrected. Itnow points to the correct filename and path. Thiscorrection resolves an issue that was affecting the MD5hash for NSF files with inline attachments.

6.10 194 6.11 108

Hashing Version 6.11.108 of LAW PreDiscovery included an updateto dtSearch from 7.79 to 7.83. The update to dtSearchcan cause hash values for a specific type of emailingested into older versions of LAW PreDiscovery (version6.10 and earlier) to not match the hash values from LAWPreDiscovery 6.11 and higher. This issue occurs only foremails with no content in the body and only if the file isre-ingested into a case after upgrading from version 6.10or earlier to 6.11 or higher.

If you experience this issue, contact Support for a runcommand that identifies the affected files. 222422

6.11 108

IMPAIsession

An error condition with the IMAPI session may bereported when processing more than 50,000 emails toHTML/MHT. The error message reports that items havebeen processed as edocs. 216388 - found in 6.10.194

6.10 194

Import Scanning may stop unexpectedly when importingmailstores larger than 64 GB consisting of large nestedPSTs (>7 GB). 216456 - found in 6.10.194

6.10 194

Import We have corrected an issue that was preventing importwhen the regional locale was set to Japan. 216385

6.9 125 6.11 108

Import Importing emails with HTML into LAW PreDiscovery nolonger converts the email to a webpage. The nativeformat of the email is now maintained. 214905

6.10 194 6.11 108

Import When imported with the Identify Hidden Text functionalityenabled, some edocs were incorrectly encoded to ANSIinstead of UTF-8. This intermittent issue has beencorrected. 220918

6.11.108 6.12 106

Known Issues 9

© 2016 LexisNexis. All rights reserved.

Category Issue Found InBuild #

ResolvedIn

Build #

Installation

Install the correct version of Microsoft Visual C++ beforeinstalling LAW PreDiscovery. See the Microsoft KnowledgeBase article "Update for Universal C Runtime in Windows"for the download and instructions. Be aware that the LAWPreDiscovery installer attempts to install all MicrosoftVisual C++ prerequisites, including:

Microsoft Visual C++ 2008 SP1 (x86)

Microsoft Visual C++ 2010 SP1 (x86)

Microsoft Visual C++ 2010 SP1 (x64) - on 64-bitmachines only

Microsoft Visual C++ 2012 Update 4 (x86)

Microsoft Visual C++ 2012 Update 4 (x64) - on 64-bitmachines only

Microsoft Visual C++ 2015 Update 2 (x86)

Microsoft Visual C++ 2015 Update 2 (x64) - on 64-bitmachines only

The LAW PreDiscovery installer may hang when itattempts to install "Microsoft Visual C++ 2015 Update 2Redistributable Package (x86)" or Microsoft Visual C++2015 Update 2 Redistributable Package (x64)" even if youhave installed it prior to the LAW PreDiscoveryinstallation.

If this occurs, abort the installation, reinstall the updatefrom the Microsoft Knowledge Base article "Update forUniversal C Runtime in Windows", and rerun the LAWPreDiscovery installer. 217325 - found in 6.10.201- Also inEDA 2.0.1.94 for bug 222925

6.10 201

Installation

When Microsoft Office 2016 is installed on a Windows 7machine, an error may be displayed when installing LAWPreDiscovery. This error appears after upgrading an olderversion of Microsoft Office. 206281

6.10 194

Installer The MSXML.DLL has been removed from the installer andProfile Manager. 212635 and 212633

6.8 6.11 108

LAWManagem

entConsole

The font selected for endorsments on the LAWManagement Console host computer may revert to thedefault font on worker computers. 216668 - found in6.10.196

6.10 196

Licensing We have corrected an issue that caused an error whenyou changed the license server in the LAW ProfileManager. 189314

6.8 109 6.11 108

Licensing The option to refresh the license from the internet is nolonger enabled under the server key menu when you areconnecting through a software license. 189316

6.8 109 6.11 108

Release Notes10

© 2016 LexisNexis. All rights reserved.

Category Issue Found InBuild #

ResolvedIn

Build #

NearNativeViewer

Strikethrough annotations applied in DiscoveryIQ are notvisible in LAW PreDiscovery when exported using LAWDirect Export in Early Data Analyzer. 220494

6.12 106

OCR A new line and text are added in OCR output files whileperforming OCR with ABBY 11 engine for CSV files. 173892

6.7 139

Persistenttag hits

The Persist Tag Hits setting can cause words to beseparated by a semicolon. 217788 - found in 6.10.194

6.10 194

TFF/PDFConversio

n

Embedded images in emails are truncated whenperforming TIFF/PDF conversion when the email is savedas an RTF file and the source app is set as MicrosoftWord. 172391

6.7 23

TFF/PDFconversio

n

When converting a document with text hidden in color toTIFF format with Reveal hidden text and Normal modeenabled, the hidden text is not shown.

6.11 108 6.12 106

Virusdetection

We have removed a signature in a file that was beingflagged by McAfee Antivirus as a potential issue. Thesignature was verified as harmless and removed from thefile to prevent further warnings from McAfee.

6.10 194 6.11 108

Release History

LAW PreDiscovery® Release Notes are specific to each version. Read the release notes for acomplete list of enhancements and issues that have been resolved or are still outstanding.

The table below contains a list of build numbers and release dates:

Version Number Release Date

6.12.106 October 7, 2016

6.11.110 July 19, 2016

6.11.108 July 6, 2016

6.10.194 April 4, 2016

6.9.113 October 15, 2015

6.9.112 September 30, 2015

6.8.133 July 27, 2015

6.8.130 July 13, 2015

Release History 11

© 2016 LexisNexis. All rights reserved.

6.8.117 May 27, 2015

6.7.144 May 4, 2015

6.7.143 April 6, 2015

6.7.139 January 20, 2015

1.6.15 December 2, 2014

6.7.137 November 21, 2014

6.6.14 September 10, 2014

6.6.09 June 24, 2014

6.6.07 May 30, 2014

6.5.25 November 19, 2013

6.4.27 July 23, 2013

6.3.45 June 17, 2013

6.3.41 May 13, 2013

6.3.37 March 29, 2013

6.2.48 November 7, 2012

6.2.46 September 5, 2012

6.1.54 February 29, 2012

6.0.06 October 20, 2011

6.0.05 August 30, 2011

Copyright Information

No part of this work may be reproduced or transmitted in any form or by any means, electronicor mechanical, including photocopying, recording, or by any information storage or retrievalsystem, without permission.

While the information contained herein is believed to be accurate, this work is provided "as is,"without warranty of any kind. The information contained in this work does not constitute, and isnot intended as, legal advice.

LexisNexis and the Knowledge Burst logo are registered trademarks of Reed Elsevier PropertiesInc., used under license. PreDiscovery is a registered trademark of LexisNexis, a division ofReed Elsevier Inc. Other products or services may be trademarks or registered trademarks oftheir respective companies.

Copyright © 2016 LexisNexis. All rights reserved.

LAW PreDiscovery®

Release Notes12

© 2016 LexisNexis. All rights reserved.

LexisNexis® Early Data Analyzer

Lexis® DiscoveryIQ

Concordance®

CaseMap®