Reveal 7.1 SP5 Release Notes

Transcription

1 Reveal 7.1 SP5 Release Notes August 14, 2018

2 Reveal 7.1 SP5 Release Notes Features Production Imaging and Stamping in One Pass Reveal will now image and stamp production documents in a single pass as opposed to multiple passes. Previously, the process was: 1. Reveal opens a native for imaging; 2. Reveal generates an image; 3. Reveal write the image to disk; 4. Reveal opens this image on disk for stamping; 5. Reveal creates a new stamped image; and 6. Reveal writes this new stamped image to disk. We have reworked the activities so the steps 3 and 4 can be removed from the workflow, eliminating significant I/O. As a part of this feature, we have changed how re-running of error documents is handled. For example, assume we have a password-protected PDF file. When we run production processing on this document, it will error and take one Bates number for its slip-sheet. We then replace this PDF with a version that is not password-protected. When we re-run errors in Reveal, the document will be stamped with the one original Bates number, then suffixed with _0002, _0003, etc. for each additional page the document gained during the error re-processing. If a document gets smaller when it is re-processed as an error, any extra unfilled Bates numbers will have slip sheets inserted with the following text: "This page intentionally left blank by the Reveal production process. The document was fewer pages than expected and no document content was omitted from these pages."

3 Switch Field Profile on Production Export Screen Users creating production exports can now select the active field profile on the production export screen: Previously, if a user wanted to change the field profile they were using for a production they would have to navigate away from the production export screen. We have streamlined this by allowing users to change their field profile for the purposes of a production export.

4 Overwriting Existing Images/Bates with Database Update We have added the ability for users to create database update jobs to overwrite previously-created images. In the past, Reveal would simply show an error if a database update were going to overwrite images. Now the follow pop-up will appear in the event your job will overwrite images in a set: Please use caution when overwriting documents in this manner, as the overwrite function can overflow into subsequent documents. For example, see the below scenario: 1. I produce a PDF with 1 page; 2. I run a database update for this production; 3. I realize that the PDF had imaged incorrectly the first time around and want to reproduce it; 4. I replace the PDF with a version that images correctly; 5. I re-produce just the PDF with its previously-used Bates number, taking up 5 pages; 6. I run a database update on the new production containing just the PDF I re-ran. In this case, overwriting with the new larger number of pages will overwrite the images for not only the document itself, but any documents sharing pages Bates numbered in the overwritten range. Overwritten documents will still have their old Bates numbers in their metadata, but will no longer have production images for those overwritten Bates numbers.

5 Exclude Documents from Production Imaging using Work Folder Users now can now exclude documents from imaging based on the contents of a work folder: You can still use file extension for exclusion as before, but now we provide the ability to exclude on a work folder as well. This change makes it easier for users to create image productions, while excluding specific sets of documents for privilege or otherwise.

6 Custom Default Field Sort Order Project managers can now set default sort orders for specific field profiles, as opposed to a single default across a case: Previously, if a user set a custom sort order then changed their field profiles or logged out of the tool, they would lose the alterations they made to their sort order. Some teams prefer to review documents in a specific order, e.g. by Sent Date or Custodian. Reveal will now remember a custom default sort ordering per field profile that can be altered by case project managers:

7 Patches Small wording, sizing, and coloring fixes on various Operations Center and Reveal pages. Fixed issue that caused various pop-up windows in Reveal to display with incorrect sizes. Fixed issue that caused UTF-8 tag information to be displayed as question-marks on the review metadata pane and in production exports. Removed stop words for new cases going forward from database full-text indexes. In some cases, this was causing specific searches to come back with more results than they should have. When filtering the Summary report for a production s preprocessing step, any filters entered will now be carried forward into any export you perform. A user filtering to show only error docs can now export just those filtered lines, instead of the entire summary report. Fixed issue allowing users to create production exports from incomplete production jobs. Previously a user could run preprocessing on an image-based production job, then create a production export from it. Because no documents were images in preprocessing, no files would be output in the production export.