February 14, 2019Reveal 7.1 SP10 Release Notes

2North America 318 W Adams St, Suite 1607 / Chicago, IL 60606, USAEurope 96 Upper Drumcondra Rd / Dublin 9, Ireland

Reveal 7.1 SP10 Release Notes Features

Column Filtering ? ? ? ? .? ? ? ? ? ? ? ? ? ? ? ................... 3

Assigning multiple field profiles to a team ? ? ? ....................... 5

Upgrade to Imaging Software ? ? ? ? ? ? ? ............................. 5

Family Relationship Identifier Field ? ? ? ? ? ? ....................... 6

Handling of Common Words with Elastic Translation .........? .. 7

Stay in Redaction Mode ? ............................................................. 8

Search for Custom Document IDs ................................................ 9

New API Endpoints .? ................................................................... 10

API Patches ? ? ............................................................................. 10

Patches (7.1 SP10) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? .. 11

3

Column Filtering

Column filtering has been one of our most-fielded feature requests from our users over the past months. We are very glad to finally introduce this feature in Reveal 7.1 SP10.

You can now filter your documents using column headers similar to how one would filter in a spreadsheet application. This permits you to search and cull your documents right from the review window:

Click on the filter icon highlighted below to show this new filter row:

Features

Column-header filtering

4

Column Filtering cont.

You can simply filter by typing in the box above a field and pressing enter. By default, wildcards are added on both ends of your text. So entering "Micro" into the filter box and hitting enter will also return documents containing "Microsoft." For more complex searching, you can click on the filter button next to a columns filter box as shown below:

From there, you have the same searching options as in the Advanced Search section of Reveal. For example, clicking on "Has Any" will pop up a window with values present in the field:

As in other areas of Reveal, selecting terms in this screen and clicking "Filter" will return results based on the terms you selected. The "Count" column represents counts of documents with that term in your current list. Values with a count of 0 are still shown in this window.

Please note: We currently support filtering on text fields and will be adding additional field types such as date, folder, and tag fields in upcoming releases. We will also be expanding column header filtering to the search screen.

5

Assigning multiple field profiles to a team

In prior versions, teams could only be associated with a single field profile. Multiple teams would have to be created in order to assign multiple field profiles to the same group of users.

To streamline this workflow, we now allow a team to be associated with any number of field profiles:

Upgrade to Imaging Software

We have made changes to our imaging software that allows users to receive updates and bug fixes faster and more reliably than was previously possible. Imaging improvements will be available to all users immediately once applied to our global systems, and will no longer require the intervention of software support.

We have added measures to ensure that all pages of a document use the same version of the imaging software. This ensures that all pages of a document are consistently imaged while allowing other documents to be imaged using newer versions of the imaging platform.

6

Family Relationship Identifier Field

We have added in a new calculated field in the document grid to show if a document is a parent, child, or a standalone document without a family. Parent documents will have a value of "Parent" while child documents will have a value of "Child". Standalone documents, those without a family, will have have an empty value in the Family Relationship field.

Family Relationship Column

7

Upgrades to Handling of Common Wordswith Elastic Translation

We have updated our Elastic Translation to better handle the use of common words in searches:

Boolean keywords such as "and" are now treated literally when used in quoted phrases. This means that proximity searches that contain common words will more closely align with user expectations.

Please note: Boolean terms such as "and" must be removed from your common word list before they become searchable.

8

Stay in Redaction Mode

When performing redactions, the user will now be placed in a redaction mode that allows the user to make multiple redactions without needing to go back and click the redaction button each time. After clicking the redaction button, you will now see the following:

As a shortcut, the user can press the "R" key to enter this redaction mode. When done placing your redactions, you can cancel out of this mode by either hitting the escape button, or by clicking the "Stop Annotation" button (as shown above).

"Stop Annotation" button

9

Search for Custom Document IDs

We have added the ability to perform Document ID searches using custom ID fields. Previously, users were able to search on only Begdoc, Itemid, or an Image Set number. Now, as long as a field is set to be a Document Number Field, it will be available for ID search:

The ID Search dropdown on the Search screen will now appear as such:

10

New API Endpoints

We have introduced new API endpoints to further enable developers who are actively integrating their software with Reveal.

/api/License

- Retrieves Reveal license information, including expiration date and user count.

/api/License

- Updates Reveal license information and allows integrated applications to update a license key.

/api/Cases/LookupLoginToken

- Allows a Reveal-provided security token to be associated to an active session's user and case.

API Patches- The API now correctly checks to make sure that creating a new user will not cause an

instance to go over its licensed user limit.

- The API now allows the modification of user information when an instance is at the maximum licensed users.

See full API documentation for further information:

http://bit.ly/Reveal-API

PUT

GET

GET

11

Patches

- Changed Windows application icons for Ops Center case creation

pop-up.

- Ops Center will now notify user when it is out of version sync with the

expected version contained in the User Management Database.

- Added measure to prevent Reveal Windows services from running

when out of version sync with the User Management Database.

- Modified Brainspace tab to prevent a separate Brainspace pop-up

window from being created.

- Added measures to prevent "Indexing Initialization has not been called"

error while indexing.

- Switch logic for "IndexExcludeMetadataForTextFileExtensions" system

setting to be inclusive rather than exclusive. Now only MSG and EML

files will have metadata extracted during the indexing process. This

change will prevent hidden metadata from being added to indexable

body text. All metadata will still be indexable, as expected, by using

advanced or metadata searches.

- Corrected issue where self-assigned documents would not show up

under a user 's list of owned assignments under some circumstances.

- Corrected issue where the installer was putting the log file directory in

an unexpected location.

- Corrected issue where the alert for searching on common words

contained multiple instances of the same word.

- Updated standard system settings to use an alternative method to

index TXT files if initial text extraction fails. This will resolve false

"Format not Supported" indexing errors.

12

Patches cont.

- Updated Brainspace export functions to allow for automatically

sending CMML scores to Reveal.

- Corrected issue where the Brainspace connector would not allow

users to update their Reveal credentials when they were changed

or expired.

- Reveal favicon updated across all sites.

- Corrected issue where removing a field from a field profile, that is also

in a tag profile, removed all teams from the tag profile as opposed to

only the necessary team.

- Added more specificity to errors generated during the loading of

images via an OPT file.

- Fixed issue where the Brainspace connector would error when a user 's

password contained the pound sign.

- Alerts will now be set when image annotations are overwritten by bulk

imaging. The exact text for the alert is taken from the system setting

"AlertAnnotationFileRemovedDuringBulkImage".

- Native productions will now use a document 's Begdoc instead of

a placeholder for document numbering when set to "Use Original Numbers".

- Changing a case from Perceptive to Elastic will now automatically

update the case's index paths to their correct value.

- Corrected issue where exporting a metadata CSV would format

incorrectly if a field contained both double-quotes and a comma.

- Corrected issue where Elasticsearch would escape some characters

twice, causing certain searches to fail.

13

Patches cont.

- We have altered our default log formatting to allow for easier log

aggregation and automated parsing. Clients using log monitoring

applications should contact Reveal support with any monitoring

concerns.

- We have disallowed the export of the calculated "Relevance" field, as it

is only used to display scores for search results. We have also

disallowed default sorting on this field, as it is only populated when

returning search results.

- Corrected issue where Production Jobs would not show up for

database updates if they generated zero images after an error re-run.

- Added "AllowSymbolicFileLinks" system setting to disallow the creation

of Production Exports with symbolic links. Symbolic links cannot be

created across network locations, so this had previously caused some

setups to error on Production Export.

- Corrected issue where Production Export would error if you modified

and re-ran a Production Export to overwrite old exported data.

- Removed formatting error popup from Email Threading that would

appear in almost all threading jobs.

- Added permission for disallowing a user from seeing the Users

sub-tab within the Admin screen.

- Corrected issue where a Production Export job would try to access

images that did not exist.