Known issues

For Processing Sets that contain large amounts of data sources, clicking the File Errors link from their Processing Set page can fail to navigate to the Files tab, and instead show a 404 error. This problem occurs when a Processing Set contains approximately 140 or more Data Sources.

To work around this issue, navigate directly to the Files tab, select the Current Errored Files view, and add a condition to filter the view by Data Source - selecting the data sources from the current Processing Set.

When a user clicks the "Install" button in the Application Library to install an application to specific workspaces, a dialog displays the error message "There are no views." The workaround is to go to the workspace to select that application from the library.

If someone tries to save a document that was previously coded with a user that has since been removed from the workspace, the save fails. This can also happen if the user was not mapped to a system user during an ARM restore. In either case, this works fine in classic.

This only happens if the user field is on the layout and editable. These are a few potential workarounds, in order of feasibility:

* Set the user field to read only.

* Remove the user field from the layout

* *Scenario 1 only (see below):* Add the user back to the workspace

* *Scenario 2 only*: Re-create the deleted user, add them to the workspace, then manually re-code the affected documents with that user. Mass Edit can be used to make this process easier

* *Scenario 3a only*: Create the missing user, then manually re-code the affected documents with the same user. Mass Edit can be used to make this process easier

* *Scenario 3b and 3c only*: Manually re-code the affected documents with the same user. Mass Edit can be used to make this process easier

* Code the documents with another user.

Steps to reproduce in 10.3:

1) Create a Report and tag Search Term Report

2) Any Index and any saved search is fine, no hits need to actually come back

3) Add 10 or more long STR terms (15 example terms using the ticket description are in the attached ""STR overlapping term example.csv"" file.

4) Run the STR

5) Open the term report and notice that the terms start overlapping when they are long enough.

Expected Behavior: The terms are spaced properly so they can be read easily.

Actual Behavior: The terms overlap and are difficult to read."

Steps to reproduce:

1. Create a multiple choice field on the document object.

2. Add 1 choice with 2 child choices via Choices Tab and Save.

3. Open any document.

4. Edit the layout and add this the choice field from step 1 as a check box list to a layout and save.

5. Click Edit and open Choice Editor by clicking the Manage link under the field created in step 1.

6. Click the alphabetize button to reorder the choices.

7. Click Save and Close.

Expected: The layout reflects the changes made to the layout.

Actual: The layout does not reflect the changed made to the layout."

Large RSMF Files Lose Attachments - Backport On-prem. Reported issues:

1: Attachments are NOT being extracted for large files. The file gets processed and can be viewed but no attachments.

2: No error is generated to tell me attachments are missing.

Fix details: The issue is tied to a limitation of Chilkat when processing such abnormal file sizes. The engineering team has added better error detection and handling to inform the customer if such limits are reached."

There is a known issue where Elusion Tests will not complete in a timely fashion due to one (or more) documents being assigned to a reviewer who is no longer active in the review. In the latest Chrome and Edge browsers, an unsaved document is not automatically freed upon closing the browser, clicking browser back button, refreshing browser, or clicking "Return to document list". Freeing a document allows it to be reviewed by another reviewer.

It takes one hour post the user logging out of Relativity for the document to be unassigned. This impacts the elusion test if the user leaves the viewer without saving the document, the elusion test document won't be available for another user until one hour after the user logs out of Relativity. If this document needs to reviewed by a different reviewer before the timeout, customer support can free the document.

When using the native text extraction option, header or footer text from Excel documents that have a different header/footer on alternating pages will be missing from the document's extracted text. This is not an issue when using Processing instead.

The implementation of the changes:

• “View Nearby Clusters” feature should have the same filtering interactions revisions but this sub-feature wasn’t identified in original requirements

When a user upgrades Case Dynamics to a Foxglove or above version, they will not see the people that were linked in the Offline Report prior to the upgrade. This issue stems from a problem with our migration code where people listed in the Person object are converted into Key People (on the Entity object) and must be relinked using the Key People (Entities) field on the Report Set object. This second step is not taking place.

There is a workaround for users where they can find the people (now Key People) that were not re-linked to the Offline Report(s) during the migration. The user can create a custom view on the Report Set object where the, Name, Report Set People and Key Entities fields are listed. Once the view is created, the user can go to the Report Set tab, open the new view and see the Key Entities that need to be relinked to the Report. Once the user finds the people that need to be relinked, they can go into the Offline Reports and manually link the Key People (and regenerate the report) or use the RDC to do an overlay

Produced Images with header and footer applied will be blank for the two following image properties:

Tall Skinny Image

Image Width in Pixels < (8.5*dpi)/3

Image Height in Pixels > (11*dpi)/3

or

Short Wide Image Image Width in Pixels > (8.5*dpi)/3

Image Height in Pixels < (11*dpi)/3

When setting up conditions for the Timeline Builder using the Is Like and Is Not Like operators, no results are rendered.

For customers who are using Workspace Portal, the version packaged in the 10.2 version of Relativity/RelativityOne can break existing integration with prior versions if the context user for the Workspace Portal OAuth client does not have the following email address: wp@relativity.one.  

Mitigation requires the following steps:

• Navigate to the OAuth client used for Workspace Portal in the satellite instances and identify the configured user.
• Navigate to the Users tab and search for the user identified in Step
  • 1. If the configured user is an active user in the system or not a specific user for the Workspace Portal app (including Relativity Admins or a Relativity Service Accounts), then a new user must be created and added to the group
  • 2. For more instructions, see here.
  • 3. Edit the user and replace its email with the required by Workspace Portal: wp@relativity.one

Resolution steps are also in this KnowledgeBase article.

In certain cases the status of document error instance in set to In-Progress, but should be Ready to Retry.

Steps:

• Run a Discover and Publish job, which will generate 3 errors for the same file ID.
• Resolve the publish problem and Re-Publish the set.

Results:

• The publish error is resolved and is marked as Retried - Expected.
• The document error is marked as In-progress when Republish started, but never got flipped to Ready-to-Retry when the job completed. - Not Expected, should be marked as Ready to Retry, since there are two more errors with the same status.

When exporting images from workspace to workspace using the options of:

* Append

* Copy Images Yes

* copy files to repository No

Then running a production set with the migrated documents the images lose their extension. The fix is provided in Relativity v.10.0 .

Hold Admin

9.5

After you activate the User & Group Operations feature, Relativity continues to use the legacy functionality to delete users and groups rather than the new optimized distributed job process. As a workaround, you can use the following steps to delete users or groups when you many workspaces in your Relativity instance:

To delete a group, remove the group from all the workspaces and then delete the group.

To delete a user, remove the user from all the groups it is in and then delete the user.