Current Version | Known Issues | Resolved Issues | History

Issues

Fixed in Version

•Signature images were overlapping text in MSG files.  

•Concordance Viewer was not properly showing/printing oversized tables or images after being converted to PDF.

1.09.01.06

•Not all punctuation characters entered in New Database Load File import wizard are saved.

•Resolved an issue resulting in an error when trying to import a CSV file.

•Fixed display of incorrect error "invalid production number field" showing when performing a production with an existing field.

•Corrected issue where multiple users were allowed to apply redactions at the same time to the same document.

•Fixed issue where the database document count updates when table or review mode is opened after running a search.  

•Resolved an issue that was preventing production from continuing after hitting certain corrupt files.

•Corrected issue where an exception was not properly caught when attempting to overlay using delimiters other than Concordance defaults.  

1.09.00.90

•In the new viewer, if the sticky markup option is selected and a redaction is applied, the reason for redaction may fail to save. To avoid any issues, select the sticky markup option, select the redaction tool, select the reason for redaction (even if it shows in the markup properties toolbar), and then apply the redaction. This issue is limited to use of the sticky markup tool for the first time.

•Using the new viewer, files located on a server were unable to be displayed properly and would generate an error.  

•Users were receiving a "locked for edit" error in the viewer when no one else was in the database.  This happened when the original user was unexpectedly disconnected from the server.  

•Low resolution monitors were unable to display the lower part of the left toolbar/document in the new viewer.  Minimum size is 400 x 300, and the viewer will uniformly stretch on resizing.  

1.08.06.04

•In the process of directly appending DAT and OPT files to an existing load file database, the import wizard may report "The selected OPT file is not valid. Please select another OPT file."  If the OPT is valid, the message is removed when the image key is selected or other wizard value is updated.

•Right clicking and selecting sort direction on connect screen columns fails to sort. Click column header as workaround.

•Overlay of an existing load file database requires field names in DAT to be in all capital letters.

1.08

•A space in Windows user profile will generate a Failure to correctly parse command line arguments error when going to Tools > Production.  

•Users may tag the results of a Search for “Documents with Redactions,” however tagging the query and attachments will result in all database documents being tagged. Users should first tag the result set and query that tag before tagging with attachments.

•Database, Matter, and User group cannot share the exact same name.

1.07.10.31

•All Users Group could not be removed once it has been added to a matter.

•User Groups added to the All Users Group matter could not be removed.

•Duplicate entries were displayed under the All User Group matter in the Admin Console.

•The list of User Groups would not re-expand after synchronizing.

•New sort layouts were not saved.

•Databases in the Smart Path directory are not automatically registered following the autoscan.

•The ATTACHRANGE prefix is duplicated when a MSG file is appended to an Email and Attachments database if the CNDCN prefix was customized during the initial import of a PST file.

1.06

•When manually registering a Concordance 10.x e-mail or load file database, an Awaiting Conversion message appears in the Admin Console Database Status column and does not change to Online, indicating that the database has not been converted. This occurs only when the database has not been properly prepared for the conversion.

1.04

•When creating a DAT database, if you create two OCR fields and name the second field with an 1 or 01 instead of a 2 or 02 (example: OCR & OCR01 instead of OCR & OCR02), it will cause the import to fail.

1.03

•Clicking on the Help link in Help About opens the Desktop folder instead of the Answer Center.

•Concordance Desktop is slow to launch when auto snapshot is turned on, and the user no longer has access to the database.

•When records are not in the exact same order in both the DAT and OPT files during an import, not all the records are imported. The error listed in the log file states that the files already exist in the database.

•When using the Redlines migration utility on TIFFs that were created by LAW defaults which are Resolution Unit 2 tiff causes Brava to create a different resolution PDF which then moves the redaction from its intended location.

•Error occurs stating that data will be lost, after adding a new field to a new database.

•When importing a PST file into an Email database, the MODDATE and CREATIONDATE fields reflect the date of the import instead of the date the attachment was actually modified.

•The hyperlink on the current document is not being updated/refreshed after adding a new field to the database.

•When exporting a DAT file from a concatenated set, only the main database DAT file is exported properly.

•In some rare instances, an EXCHARGSRECV_ERROR message is displayed when attempting to connect or open the Admin Console in a Windows 10 Virtual Machine (VM) environment. Should you receive this error message, contact Support for a work around.

•Windows could not start the Concordance Server service on Local Computer Error 1053: The service did not respond to the start or control request in a timely fashion.

•When reopening the Customize dialog box for Field Settings, the fields previously created are no longer visible.

1.02

•Quick search does not execute a previous search from the quick search list if the query was originally created from the right-click menu in the Tags pane.

1.01

•When importing documents with Right-To-Left (RTL) languages, such as Arabic, the imported text may be incorrectly justified to the left side.

1.00