<< Click to Display Table of Contents >>

Concordance

Concordance Native Viewer

Concordance Image

Concordance FYI Server

Concordance FYI Reviewer

 

Enhancements | Resolved Issues | Known Issues | History

 

Issues

Fixed in Version

Resolved an issue where some email content (more commonly emails with embedded images), fails to display in Concordance Native Viewer.

Updated error handling to properly display messages for internal errors occurring during productions to PDF.

Resolved an issue where produced scrub text files were not output to the correct folder structure.

1.14

Documents are not displayed in Concordance Native Viewer when the media key characters in the OPT file and the image key characters in the Concordance database record are not written in the same format (uppercase/lowercase).  For example, the OPT file contains the media key abc001 and the corresponding database record contains ABC001.  Media keys are case-sensitive.

Creating an Email and Attachments database and then selecting to view e-mails in Concordance Native Viewer, the original time format of .msg file changes to GMT time.

The imagebase cannot be renamed if the alias contains a hyphen character (-).

Productions that include all .jpeg formatted files may duplicate the first image multiple times.

Single page images with more than one image file associated with a document does not display the image name.

Thumbnails pane closes when navigating between documents or pages.

Setting the font size in the Font dialog box of the Edit Headers and Footers dialog is not reflected in the UI after closing and reopening the dialog box.  

When using the CNV Printing option to print PDF documents to a PDF Distiller or a PostScript printer in Concordance, the printouts print inverted (black background and white foreground).

When viewing a PowerPoint with multiple slides, some slides are not displayed in CNV.

A folder is created in the root of the C drive when using Concordance Native Viewer as an external viewer with .FYI files and FYI Reviewer.

Selecting the Grayscale option when producing TIFF formatted type files from multi-page native files containing imbedded images, does not render the imbedded images properly.  Use the Color option to produce these types of files.

Additional blank page(s) are shown for Microsoft Excel (.xls, .xlsx) and Word (.docx) documents.

Microsoft Excel files imported using the E-Documents import display as expected in Concordance Native Viewer.

Files with embedded htm code do not display properly in Concordance Native Viewer.

1.10

Executing a query and then adding markups to a document displays the incorrect markup history information for the document.

Increase zoom button (+) not working properly for some .msg and .xls file types.

Images not resizing to fill viewer image area.

1.08

Go To Image page feature button returns to first image when navigating to the first image page.

1.07

Concordance Native Viewer supports single-page OPT conversions for JPG and BMP formatted file types.

Microsoft Windows XP users that have a Limited User Account cannot access the Image Base Management feature.

1.06

Improved performance for document to document navigation when multiple users are reviewing documents in the same database.

Document breaks are rendering properly when exporting an OPT file from the Concordance Native Viewer imagebase.

1.05

OPT files convert properly to a .CIB file if an apostrophe exists in the filepath of the opt file.

During a production, Stamp markups would not appear if both Text and Rectangle markups are set to No. To include Stamp markups in a production, make sure that both Text and Rectangle markups setting are set to Yes along with the Stamp markup.

After upgrading from CNV v1.01, with a Document Management application open and then launching the viewer no longer causes CNV to not render the file and display an Unspecified Error message.

1.04

Improved performance when importing an opt file for a native documents database.

Long database paths overlap the date in the Concordance Native Viewer printed conversion report.

1.03

The conversion of a .DIR file to a .CIB file no longer prompts the user to install Microsoft Office if the application is currently installed.

Comma-separated formatted (.csv) files can be viewed in Concordance Native Viewer

1.02

Support for PackBits compression of TIF files for use with Concordance Image.

A single load file imported into a Concordance Native Viewer Image Base (CIB) file is now supported.

Resolved an issue that resulted in an extra “\” being added to the end of the file extension path when exporting a Concordance Native Viewer imagebase to an OPT formatted file.  

Resolved an issue where an error message is generated if the "alias" in an OPT file did not exactly match the media key in Concordance due to case sensitivity.  For example, the OPT file contains abc001 and the corresponding record in Concordance contains ABC001.

Concordance Native Viewer is now compatible with both upper and lowercase file extensions when loading multiple single page image files.

1.01

When printing and using the bates stamp option, Concordance does not auto-increment the bates on a multi page document. A bates numbered range is printed on all pages.

Pressing any key on the keyboard when opening Concordance Native Viewer produces an Unhandled Exception Error message to display.

When viewing documents and then adding a document to the database in Concordance, clicking the Last Document button does not display the added document until the Last Document button is clicked a second time.

If a record contains an unsupported embedded file type and page navigation is attempted using the Thumbnail pane, Concordance Native Viewer displays multiple error messages.

A folder is created in the root of C drive when viewing images when using Concordance Native Viewer as external viewer with .FYI files and FYI Reviewer.

Executing the OCR on the Fly process after editing a record in Concordance, displays a message indicating the database is locked.  Make sure to navigate to next record and back after editing a record and then execute the the OCR process.

Markups applied and viewed using two different OS systems may not appear in the same location where the markup was originally applied.  For example, markups applied when using a Windows XP machine, may not appear in the same location when viewed on a Windows Vista machine.

When installing Concordance Native Viewer, non-administrator users cannot successfully install the application. The Concordance Native Viewer executable is not found.  Concordance Native Viewer requires Microsoft Windows Administrator privileges for installation.

When using the Thumbnails pane, document thumbnails may not appear.  Click View > Toggle Thumbnails to refresh the Thumbnails pane and display the document and pages.

Thumbnails pane closes when navigating between documents or pages.

Setting the font size in the Font dialog box of the Edit Headers and Footers dialog is not reflected in the UI after closing and reopening the dialog box.  Once the font size is set, the correct font size appears in the produced or printed output.  The size is simply not retained in the UI and always reverts to size 10.

When using the CNV Printing option to print PDF documents to a PDF Distiller or a PostScript printer in Concordance, the printouts print inverted (black background and white foreground).  To print to a PDF Distiller or a PostScript printer, produce the files as PDF documents using the Production module and then print the produced documents.

Installation of Concordance Native Viewer requires that the application be installed on individual workstations/desktops.

When printing Concordance Native Viewer documents that include redactions, the redactions print with the default level of transparency applied, revealing the text below.  To print opaque redactions, run the document(s) through the production process to create a new document(s) and then print the document(s).

The Markup History pane does not display any markup information for a secondary database of a concatenated set of databases.

When uninstalling CNV, the BravaDesktop application is not uninstalled.  Because CNV is tightly integrated with the BravaDesktop application, it is recommended that you manually uninstall the BravaDesktop application first then uninstall CNV to remove all BravaDesktop files and folders.  You do not need to uninstall the BravaDesktop application if you are reinstalling CNV due to an expired license.

When setting production parameters, strikeout, highlight, and underline are all included if only one is selected.

A "Subscription" license displays as "Standard" in the About Concordance Native Viewer dialog box.

Concordance Desktop

 

 

 

Copyright © 2022 CloudNine™. All rights reserved.

 

Concordance® | Concordance® Native Viewer | Concordance® Image | Concordance® FYI™