Concordance Native Viewer - Known Issues

•Images are not available for viewing in FYI Reviewer using Concordance Native Viewer if the image file path contains an Ampersand (&) character.

•Production numbers may be written to Read-Only fields when executing a production run.

•OCR on the Fly cannot process Hebrew or Arabic characters.

•Microsoft .NET Framework 3.5 Sp1 needs to be installed to be compatible with CNV and .NET Framework 4 must be installed to use the OCR on the Fly command.  The components are installed automatically for Windows XP and Windows 7 when CNV is installed.  However, when installing on server machines (Windows Server 2003/2008) .NET Framework 3.5 Sp1 and/or .NET Framework 4.0 must be installed manually.

•Information contained within a sticky note applied to a PDF document before loading and viewing the PDF document in Concordance Native Viewer is not captured during the OCR process.

•Redactions applied to text formatted files using Concordance Native Viewer, versions 1.0-1.01 may not appear in the proper location when using with CaseMap version 10.0.

•The volume name is not included in the produced OPT file during a Production.

•Due to changes in the latest release of BravaDesktop, the Redaction Reason dialog box is removed.  Reasons are now entered in the Markup Properties toolbar.  See, Applying Redactions in the Concordance Answer Center.

•Applying the Note markup to a rotated document/image results in the document/image maintaining its rotated state when navigating between files.  The rotation does not affect the placement for any other markups.  However, if needed, remove the note and the document/image will return to its original orientation.

•When printing OPT load error log files, if the OPT file path is longer than 70 characters, the printed filepath overlaps with the date, rendering the filepath and date text unreadable.longer than 70 characters

•When executing a production, volume aliases (names) are not written to a generated OPT file.  The volume alias is not needed for Concordance Native Viewer to properly load files.

•File > Close command does not close Concordance Native Viewer accessed through FYI Reviewer.

•An error message may appear when using a .fyi file to view native documents in Concordance Native Viewer.

•Converted or directly created Concordance Image Base database (.cib) files are not compatible with Concordance version 10.09 or earlier or Concordance Image version 5.07 or earlier.

•Printing back-to-back batches of documents may cause the CNV Printing to stall.  If this should happen, close Concordance and rerun the print job.

•CNV Markup and Navigation toolbars may disappear when the Review button is activated in Concordance.

•Highlight markups applied in CNV print opaque, which hides the text underneath.

•When printing and/or production documents or images and selecting one of the markups (crossout, strikeout, highlight, or underline) will print or produce all three markups.

•Navigation toolbar buttons become disabled in Concordance and Concordance Native Viewer after creating an OPT file and CIB conversion.  To view records, run a Zero query.

•Printed document quality is low when compared to the printed quality of a document printed after a production run.

•Markup history is not updated when the markup created by one user is edited by different user for .fyi file on a different machine.