LAW 6.8.117 - May 27, 2015

Enhancements

Licensing

•Software can now be licensed via software key in addition to the USB key.

Near-Duplicate & Email Thread Analysis

•Email threading and near duplicate processing can now run independently of one another.

•The ET_Indent field is created by the Email Thread Analysis process to reflect the nested reply level of emails analyzed.

Placeholders

•Custom Placeholders can be created, edited, and deleted on a case level from the Separator Page Options dialog box.

•Custom Placeholders can be assigned in the grid view and will be processed during batch TIFF/PDF conversion and e-print.

User Documentation

•Answer Center topics can now be launched directly from the LAW PreDiscovery Help.

ED Loader

•The ED Loader compound document processing has been replaced with the EDA compound document processing.

•The ED Loader archive processing has been replaced with the EDA archive processing.

Endorse

•The use of ImagXpress SDK has been eliminated.

•Modified the current method of endorsing single page PDF files to avoid unnecessary file conversions.

•Header and footer height is now set to be incremental at .25 inches.

Search

•The LAW PreDiscovery search engine is now upgraded to dtSearch version 7.79.

User Documentation

•Removed the Law50.chm file from the LAW PreDiscovery installer.

•The LAW50.chm file is no longer added to the LAW50 directory during installation.

Known Issues

ED Loader

•7zip processing is much slower than the current archive processing due to limitations of the toolkit used for extraction.

Workaround/Comments:

This issue will be addressed in a future release of LAW PreDiscovery.

•Decompression of JPEG images in ZIPX archives is not supported. Decompression of JPEG images in ZIPX archives is not supported.

Workaround/Comments:

Warnings are logged for the affected files during the import process. Users can then perform the extraction manually (or with another tool) outside of LAW PreDiscovery. Support for this format will be attempted in a future release.

•The issue of MIME headers (e.g. “Date: Wed, 06 Aug 2014 08:47:49 -0700”) being visible (in certain viewers) when saving emails to MHTML during ED Loader imports was resolved in LAW PreDiscovery version 6.7; however, this issue still occurs with “Note” Microsoft Outlook items.

Workaround/Comments:

This issue is caused by a third-party component used by LAW PreDiscovery. We will attempt to address this in a future release.

•"Object variable width block not set" error occurs when attempting to load OST files created with Microsoft Outlook 2013.

Due to the lack of a specification, the 3rd party component used to process OST does not support OST files created with Microsoft Outlook 2013. This issue will be resolved in a future release.

This issue only applies to LAW PreDiscovery versions 6.5.x, 6.6.x, 6.7.x, and 6.8.x.

Workaround/Comments:

Convert the OST file to PST using third-party component and then process as PST.

Endorsing

•When endorsing PDF files with comments, the comments may be lost.

Workaround/Comments:

This issue will be addressed in a future release of LAW PreDiscovery.

Export

•When exporting documents with duplicate filenames while using filename as the naming scheme and Perform Duplicate Checks 'On file naming scheme' checked, the files with duplicate filenames will not be written to disk using the "(Copy x)" suffix. This will result in only one file being created for all files with the same file name.

This issue only applies to LAW PreDiscovery versions 6.7.x and 6.8.x.

Workaround/Comments:

Duplicate the filename field and manually update duplicate filenames with "(Copy x)" suffix. Use this field for the naming scheme.

Import

•Images over 2GB in size may fail to import.

Workaround/Comments:

This issue is due to a limitation of a 3rd party component. To correct the issue, reduce the file size utilizing a 3rd party application that supports images over 2GB prior to importing.

•Unable to import OST files created with Microsoft Outlook 2013.

Due to the lack of a specification, the 3rd party component used to process OST does not support OST files created with Microsoft Outlook 2013. This issue will be resolved in a future release.

This issue only applies to LAW PreDiscovery versions 6.5.x, 6.6.x, 6.7.x, and 6.8.x.

Workaround/Comments:

Convert the OST file to PST using third-party component and then process as PST.

PDF Support

•The PDF conversion process may fail on certain Microsoft Office documents on supported 64-bit operating systems (Windows 7 and Windows Server 2008 R2) with 32-bit Office 2010.

Workaround/Comments:

Currently, the workaround is to run the conversion using an alternate system configuration (32- or 64-bit operating system with Office 2007 or 32-bit operating system with Office 2010).

•Markup (e.g., comments, arrows, lines) existing in (raw image) imported PDFs will not be viewable in the LAW PreDiscovery image viewer and will not appear in the output when printed.

Workaround/Comments:

As an alternative, the PDFs can be imported using ED Loader and, if needed, converted to TIFF or PDF.

Scanning

•The File Type scanner output value may become “stuck” (cannot be changed from drop-down list) in certain scenarios when using the scan toolbar.

Workaround/Comments:

Close and re-open the scan toolbar to resolve the issue.

•LAW will close unexpectedly when the Edit > Insert > Scanned Document function is selected if a scanner is not configured in LAW PreDiscovery.

Workaround/Comments:

Ensure a scanner is properly configured in LAW prior to accessing this scan function.

Software Licensing

•The LAW Management Console (LMC) may improperly report negative license counts when the license server is set to localhost.

This issue only applies to LAW PreDiscovery version 6.8.x.

Workaround/Comments:

Install product keys on one single server and point all machines to that server.

TIFF/PDF Conversion and E-printing

•LexisNexis Image Drivers are renamed when upgrading to LAW PreDiscovery version 6.7 to resolve an issue with a “This printer is currently set to black and white mode” pop-up error message that halted the conversion process. If the drivers are not renamed during the upgrade (e.g. permissions issue arises), please use the workaround if this error was a problem for you in previous versions or to avoid the issue should it arise in the future.

Workaround/Comments:

The two image drivers can be renamed manually, provided the user permissions are sufficient. The new names are “LexisNexis Image Driver” (no quotes – formerly “LexisNexis Image Driver 5.0) and “LexisNexis Image Driver 300 DPI” (no quotes – formerly “LexisNexis Image Driver 5.0 (300 DPI)”). If a second set of image drivers are added during the upgrade, simply remove the original set which include the “5.0” in the driver names.