Nuix Discover On-Premises Release Notes

Introducing the Bulk Annotations feature

The Bulk Annotations feature allows users to apply highlights or redactions to multiple documents simultaneously.

Apply bulk annotations on the Documents page

You can apply annotations to multiple documents at the same time.

To apply bulk annotations:

1. On the Documents page, in the List pane, select the check box next to the documents that you want to apply bulk annotations to.
2. On the Tools menu, under Processing, select Bulk annotations.



The Bulk annotations window appears.

3. On the Exclusions page, the documents that you selected for bulk annotation are sorted by the number of documents that will be submitted for bulk annotation and the number of documents that will not be submitted. In the Document must be excluded area, you can search for documents that will not be annotated using the Bulk Annotations feature. Click a number to see the list of affected documents. Click Next.



Note: Documents must be imaged in PDF format prior to using the Bulk Annotations feature.

4. On the Terms page, in the Option list, select one of the following:
• Advanced query syntax: Enter the search terms and operators to identify the text that you want to highlight or redact.



• Search Term Families: Select the search term family that identifies the terms you want to highlight or redact.



Note: The Document count column displays only the number of base documents and not renditions.

5. Click Next.
6. On the Annotation page, select either of the following options:
• Redaction: Click the box for the color of the redaction. You can select only black or white. Select the label for the redaction in the list.



• Highlight: Select a highlight option from the list.



7. Click OK.

The application submits the annotation job.

View documents displaying bulk annotations

After the bulk annotation job is completed, you can view the annotations in the Annotations List pane, which you can access from the Image viewer in the View pane.

Tip: To find the documents with bulk annotations, you can run a search on the Search page using the following search criteria: Bulk Annotation Status is Succeeded.

To view bulk annotations:

1. On the Documents page, in the List pane, select one or more documents.
2. In the View pane, in the Image viewer, click the Annotation List button on the vertical toolbar.



The Annotation List pane contains the following columns:

• Annotation type: Select an annotation type to display. Options are Black redactions, White redactions, and Highlights.
• Label/Name: Filter by the label or the name of the annotation.
• Mass coded: The mass coded icon indicates if it was a mass action to multiple documents at once. You can filter documents by Single coded or Mass coded.
• Page: Displays the list of pages containing annotations in ascending or descending order. You can also filter the list of pages by entering a number that the page number you are looking for is less than, greater than, or equal to.
• Term: This column displays the term used for the annotation. Enter text to filter by a specific term.
• Type: This column displays the source of the terms in the Term column. You can filter on any of the following types:
• Advanced query syntax
• Search term families
• Word or phrase
3. To view the annotations on a specific page in the document, in the Annotation List pane, in the Page column, click a link.

The page with the annotations appears in the Image viewer.

Delete bulk annotations

To delete annotations added with the Bulk Annotations feature:

1. On the Documents page, in the List pane, select one or more documents.
2. In the View pane, in the Image viewer, click the Annotation List button on the vertical toolbar.
3. Click the annotation or annotations that you want to delete.
4. Click the Delete button.

Audio: Updated language models for the audio transcription feature

Nuix Discover uses the IBM Watson Speech to Text service for the audio transcription feature.

On September 15, 2022, IBM deprecated the previous-generation language models and supports only the next-generation language models.

Per IBM, “Next-generation models have higher throughput than the previous-generation models, so the service can return transcriptions more quickly. Next-generation models also provide noticeably better transcription accuracy.”

In preparation for this change, we migrated the previous-generation language models to the next-generation language models in Nuix Discover. We also added four new language models.

For information about the IBM Watson Speech to Text next-generation language models, see Next-generation languages and models | IBM Cloud Docs

As of this release, the following next-generation language models are available in Nuix Discover:

• Arabic (Modern Standard)
• Chinese (Mandarin)
• New: English (Australian)
• English (UK)
• English (US)
• French
• New: French (Canadian)
• German
• New: Italian
• Japanese
• Korean
• Portuguese (Brazilian)
• Spanish
• New: Spanish (Latin America)

The following previous-generation language models were available in Nuix Discover until version 10.11.001:

• Arabic (Modern Standard)
• Brazilian Portuguese
• Chinese (Mandarin)
• English (UK)
• French
• German
• Japanese
• Korean
• Spanish

Conditional Coding pane and Memo Editor pane: New user interface when linking to transcripts or transcript pages from a memo field

When you add a link to a transcript from a memo field in the Conditional Coding pane or the Memo Editor pane, the Link transcript dialog box now has a new user interface. The functionality is the same.

To access this dialog box from the Conditional Coding pane, in a memo field in a coding template in the Conditional Coding pane, double-click text, and then click Transcript link on the inline menu.

To access this dialog box from the Memo Editor pane, double-click text, and then click Transcript link on the inline menu.

Related pane: Find and view hash duplicate documents in the Similar section in the Related pane

When you select documents in the List pane, the application includes hash duplicate documents that you can now view in the Similar section in the Related pane.

Hash duplicate documents have a similarity of 100.

The master duplicate document appears as the first document in the list in the Similar section.

In the Similarity column, the bold green type indicates the master duplicate document.

Tip: Hover over the number to in the Similarity column to display the tooltip for the Master duplicate document.

The individual duplicate documents appear after the master duplicate document. The number in the Similarity column appears in bold black type to indicate an individual duplicate document.

Tip: Hover over the number in the Similarity column to display the tooltip for an Individual duplicate document.

Note: The application displays other similar documents and the similarity scores after the individual duplicate documents.

Manage Documents > Bulk Annotations: Administer the Bulk Annotations feature

The Bulk Annotations feature allows users to apply highlights or redactions to multiple documents simultaneously. This section describes how to administer this feature.

Grant group leaders and group members administrative access to the Bulk Annotations page

You can grant group leaders and group members access to the Manage Documents > Bulk Annotations page.

Enable the Bulk Annotations feature

To enable the Bulk Annotations feature, administrators must grant users access to the Processing - Bulk annotations feature.

To grant or deny access to this feature:

1. On the Case Home page, under Security, click Features.
2. In the row for Processing - Bulk annotations, under a group column, click the Allow or Deny option.

Enable bulk annotation system fields

Administrators can make bulk annotation system fields available to user groups. The fields appear as search criteria that the user can select on the Search page and as columns to display in the List pane.

The following system fields are available:

• Bulk Annotation ID: The job ID of the bulk annotation job that was submitted.
• Bulk Annotation Reverted ID: The job ID of the reverted bulk annotation job that was submitted.
• Bulk Annotation Reverted Status: The current status of the reverted bulk annotation job.
• Bulk Annotation Status: The current status of the bulk annotation job.

View documents displaying bulk annotations

To view the annotations in your document:

1. On the Manage Documents > Bulk Annotations page, on the Bulk annotation jobs tab, click the number displayed next to your job ID in the Documents column.
2. On the Documents page, in the List pane, select the document in which you want to view the annotations.
3. In the View pane, in the Image viewer, click the Annotation List button. The Annotation List pane displays the number of annotations and the page on which those annotations appear.

View Bulk annotation job properties

Administrators can view the properties and progress of bulk annotation jobs on the Bulk annotation jobs and Reverted jobs pages.

To view information about bulk annotations and reverted jobs:

1. On the Case Home page, under Manage Documents, click Bulk Annotations.
2. Select the Bulk annotation jobs or Reverted jobs tabs to view a list of jobs.



The columns that appear on these pages provide information such as Job ID, the number of documents annotated, the search terms or search term family used, the number of search terms identified, the number of annotations applied, and the name of the user who created the job.

Revert previously annotated documents

If you have applied bulk annotations to a selection of documents, you can revert the bulk annotations job such that the annotations are removed. When you revert a bulk annotation, the application does the following:

• Removes the highlights or redactions from the document.
• Adds information about the reverted job to the Reverted jobs tab.

To revert a bulk annotation job:

1. On the Case Home page, under Manage Documents, click Bulk Annotations.
2. On the Bulk annotation jobs page, select the check box next to the bulk annotation job that you want to revert.

Note: You can revert annotations only for documents that were previously annotated using the Bulk Annotations feature. If you revert a bulk annotation job, all annotations that were applied using the Bulk Annotations feature are removed, including annotations modified manually.

3. On the toolbar, click Revert.
4. In the Revert bulk annotations dialog box, click OK.

The application reverts the bulk annotations in the chosen document set. A dot appears in the Reverted column on the Bulk annotations page, and a new line appears on the Reverted jobs page that displays the details of the reverted job.

Download a bulk annotations report

To download a bulk annotations report to an .xls format:

1. On the Case Home page, under Manage Documents, click Bulk Annotations.
2. On the toolbar, click Download report.

Case Setup > System Fields: Values for Concept Analysis Status field renamed

The following values for the Concept Analysis Status field are renamed as follows:

• Completed with Entities is now named Completed With Concepts
• Completed with no Entities is now named Completed With No Concepts

Portal Management > Processing > Enhancements to the data filtering stage of an Ingestions job

As part of the ongoing effort to enhance the processing performance of Ingestions, to optimize the performance of the Data Filtering stage of an Ingestions job, the following four individual tasks are now a single data filtering task:

• Filter by Date Range
• Filter by excluded files
• Filter by NIST
• Filter by De-duplication

Connect API Explorer: Update to case comparison operators

The Connect API Explorer now contains a new filter operator (op) when querying case data. Case operators used to support comparison patterns for LIKE, used for strings, and EQUALS, used for everything else. Now, a user can query case data using other comparison patterns against dates, strings, and numbers expanding upon the original operators.

String operators:

• Like
• StartsWith
• Equals
• NotEquals
• HasValue
• HasNoValue

Number and Date operators:

• Equals
• LessThan
• LessThanOrEqual
• GreaterThan
• GreaterThanOrEqual
• NotEquals
• HasValue
• HasNoValue

Sample query:

{
  cases(
    filter: {name: {op: Like, value: “enron”}, 
      caseCreatedDate: {op: LessThanOrEqual, value: “2020-02-12”}, 
      organizationId: {op: Equals, value: 6}}
  ) {
    id
    name
    caseCreatedDate
  }
}

Sample query results:

{
  “data”: {
    “cases”: [
      {
        “id”: 6077,
        “name”: “Clean_Enron”,
        “caseCreatedDate”: “2017-10-16T17:44:04.95Z”
      }
    ]
  }
}

Connect API Explorer: Query saved searches

You can now query saved searches, using the savedSearches query, and retrieve their related data.

Parameters and filters available are:

• id
• name
• createdDate
• createdByUser

Sample query:

query cases {
  cases(ids: [1, 5]) {
    savedSearches {
      id
      name
      createdDate
      createdByUser {
        id
        userName
      }
    }
  }
}

Sample query results:

{
  “data”: {
    “cases”: [
      { “name”: “Acme6_PM2”, “savedSearches”: [] }
      ,
      {
      “name”: “Clean_Enron”,
      “savedSearches”: [
      {
      “id”: 15,
      “name”: “[PERF] - RW - DO NOT DELETE FO FOO”,
      “createdDate”: “2016-03-15T22:48:46.743Z”,
      “createdByUser”:
      { “id”: 181, “userName”: “lsimpson” }
      },
      {
      “id”: 11,
      “name”: “[PERF] [WF] [VC] - DO NOT DELETE FO FOO”,
      “createdDate”: “2016-02-13T00:13:25.613Z”,
      “createdByUser”:
      { “id”: 2, “userName”: “abuckholt” }
    }
    ]
  }
  ]
  }
}

Connect API Explorer: caseCreate mutation updates

The caseCreate mutation now contains a few new conditional updates based on the organizationId field.

• When running the caseCreate mutation, it uses the organization’s default settings for servers and file repositories. However, if an organization’s default settings are not set, a message appears stating Organization defaults are not set for required servers or repositories.
• If you do not provide an organization ID in the mutation, the application uses the user’s organization ID.
• But, if the provided organization ID is not valid, a message appears stating Invalid organizationID input.
• If the provided organization ID is valid, the application creates a new case under that ID. When the application creates this case, it schedules case metrics jobs based on the organization settings. But, if these settings do not exist, the case metrics job runs monthly.

Required fields:

• caseName
• organizationId

Optional fields:

• Description
• scheduleMetricsJob

Sample mutation:

mutation {
  caseCreate(
    input: {organizationId: 1, caseName: “Cookie Monster”, description: “nom nom nom”, scheduleMetricsJob: true}
  ) {
    case {
      id
    }
  }
}

Connect API Explorer: importJobAddDocuments mutation updated for creating links

The importJobAddDocuments mutation now allows users to create links between person values and organization values within a case. To successfully import these links, you need to create and execute the following three mutations: The first to create the import job, the second to import the data containing the links, and the last to run the import job request.

Sample mutation to create the import job and retrieve a job ID:

mutation MyJobCreateMutation {
  importJobCreate(caseId: 6077
    input: {
      name: “Import People and Organization Links”
    }
  )
  {
    rdxJobId
  }
}

Results of the import job creation with needed job ID:

{
  “data”: {
    “importJobCreate”: {
      “rdxJobId”: 68
    }
  }
}

Sample import mutation using the created job ID:

mutation MyJobAddMutation {
  importJobAddDocuments(
    caseId: 6077
    input: {
      rdxJobId: 68,
      documents: {
        documentId: “POLinks_00000002”,
        correspondence: [
          {type: “From”,
            people: “fromme@from.com”,
            action: InsertUpdate},
          {type: “To”,
            people: “tome@to.com”,
            orgs: “I work at To”,
            action: InsertUpdate,
            linkPeopleOrg: Insert},
          {type: “To”,
            people: “justme@me.com”,
            orgs: “Me”,
            action: InsertUpdate},
          {type: “CC”,
            orgs: “Copy for everyone”,
            action: InsertUpdate},
          {type: “CC”,
            people: “aperson@everywhere.com”,
            orgs: [“Everywhere”, “Nowhere”],
            action: InsertUpdate,
            linkPeopleOrg: Insert}
        ]
      }
    }
  ) {
    documentCount
  }
}

Results of importing the link data:

{
  “data”: {
    “importJobAddDocuments”: {
      “documentCount”: 1
    }
  }
}

Sample mutation for running the import job:

mutation MyExecuteImportJobMutation {
  importJobSubmit(
    caseId: 6077,
    input: {
      rdxJobId: 69
    }
  )
  {
    rpfJobId
  }
}

How to contact Nuix Support

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Installation and deployment notes

For detailed information about client and system requirements, as well as upgrade and installation instructions for this release, see the following documents on the Nuix Customer Portal.

• Nuix Discover - Client Computer Requirements
• Nuix Discover - Hardware and System Requirements
• Nuix Discover - Upgrade Checklist
• Nuix Discover - Installation and Configuration Guide

Future version of Nuix Discover requires .NET Runtime 6.0.8 or later

The new Nuix Discover case-to-case migration feature, which will be released to on-premises clients in a future release in late 2022 or early 2023, will require the latest version of .NET Runtime 6.0.

We want to alert you to this change now so that you can plan accordingly.

Note: Once the release that includes the case-to-case migration feature is available, the installation will be successful only if .NET 4.8 and .NET Runtime 6.0.8 or later are pre-installed.

The link to the .NET Runtime 6.0.8 (or later) installer will be available on the quarterly release page for Nuix Discover on the Nuix Customer Portal.

You also can download the .NET Runtime 6.0.8 installer now from the .NET Runtime section on this page.

Supported upgrade paths

You can upgrade the following versions of Ringtail Legal and Ringtail to this version of Nuix Discover 10.x:

• Ringtail 8.0.1, 8.1, 8.2, 8.3, 8.3.1, 8.3.2, 8.4, 8.4.2, 8.5, 8.6
• Ringtail Legal 1.0.58

For versions of Ringtail Legal earlier than 1.0.57, you must first upgrade to Ringtail Legal 1.0.58, and then upgrade to Nuix Discover 10.x.

Note: When upgrading to Ringtail 8.6 or later from an earlier version, you must request an updated license.

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Nuix Discover support lifecycle for biweekly and quarterly releases

Note the following support lifecycle for biweekly and quarterly releases:

• Biweekly releases
• Nuix supports the last four biweekly releases.
• Example: 10.8.005, 10.8.004, 10.8.003, 10.8.002
• Quarterly releases
• Nuix supports the last four quarterly releases to on-premises clients.
• Example: 10.11, 10.10, 10.9, 10.8

Note: Nuix Discover provides service packs for quarterly releases for up to the latest four releases and for one year from the initial release date of the quarterly release.

Service parks for biweekly releases are provided for the four most recent biweekly releases.

For earlier releases that are no longer eligible for service packs, the Nuix Support Team provides best-effort support.

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Nuix Discover support lifecycle for Microsoft Windows Server and Microsoft SQL Server

The Nuix Discover support lifecycle for Microsoft products is communicated annually. For additional information about the Microsoft Lifecycle Policy, go to https://support.microsoft.com/en-us/lifecycle/search.

Note: Nuix Discover support for Windows Server 2016 and SQL Server 2016 ends on April 1, 2023.

The general support policy for Windows Server and SQL Server for Nuix Discover quarterly on-premises releases is as follows:

• Nuix Discover supports at least two versions of Windows Server and SQL Server for each release.
• Within one year of a newly released version of Windows Server or SQL Server, Nuix Discover supports those versions.
• Once Microsoft ends mainstream support for a version of Windows Server or SQL Server, Nuix Discover no longer support those versions.
• Nuix communicates a 12-month notice of support retirement with each quarterly on-premises release.

For detailed information about client computer requirements, see the Nuix Discover - Client Computer Requirements guide for this release. For detailed system and hardware requirements, see the Nuix Discover - Hardware and System Requirements guide for this release. These guides are available on the Nuix Customer Portal.

Improved Nuix Discover login experience

In previous versions, users who inadvertently navigated to the Login Service URL received an error message. System administrators are now able to configure the login experience such that users who go to the Login Service URL are redirected automatically to the appropriate portal URL.

For more information about the Login Service and how to configure it, see the Nuix Discover - Installation and Configuration Guide, which is available for download from the Nuix Customer Portal.

Conditional Coding: Customize the layout and zoom

In the Conditional Coding pane, you can now customize the layout of the coding field names and values in the Single coding and Mass coding views.

To customize the layout in the Conditional Coding pane:

1. On the Conditional Coding pane menu, select Options.
2. In the Options dialog box, under Layout, select one of the following options:



• Auto: With this option, which is selected by default, the application automatically adjusts the layout (top and bottom or left and right) of the field name and field values depending on the width of the pane.
• Top and bottom: If you select this option, the application always displays the field values underneath the field name.



• Left and right: If you select this option, the application always displays the field name on the left side of the pane and the field values on the right side of the pane.



3. Click OK.

You can also change the zoom level to increase or decrease the display size of the content in the Single coding and Mass coding views. A smaller zoom level can be useful for showing more information on the screen.

To change the zoom level:

1. From the Conditional Coding pane menu, select Options.
2. In the Options dialog box, under Zoom (%), adjust the percentage. The default setting is 100. The zoom percentage range is 75-150.
3. Click OK.

Conditional Coding: New Binders - Custom field for conditional templates

If your administrator added the Binders - Custom field to a conditional coding template, you can now code documents to the binders included in this field in the Conditional Coding pane.

Conditional Coding: New Issues - Custom field for conditional templates

If your administrator added the Issues - Custom field to a conditional coding template, you can now code documents to the issues included in this field in the Conditional Coding pane.

Conditional Coding: New Source/Attachments field for conditional templates

If your administrator added the Source/Attachments field to a conditional template in the Conditional Coding pane, you can use this field to see where a document is positioned within the tree of its related Source/Attachments documents.

The current active document appears in black type, and the related document IDs are links that you can click to open each document in a standalone window. The icon and tooltip to the left of a document ID indicate the document type, and the icon color represents the coded value of the quick code field (if configured).

The Source/Attachments field also appears in the System Fields section of the All Values template in the Conditional Coding pane.

View pane: Keyword summary

This release includes a new Keyword summary feature that enhances review productivity. You can now review hits in a document in a more efficient manner and focus your review on the specific content immediately around the keyword highlights enabled in the formatted and unformatted content views.

To use the Keyword summary feature:

1. In the View pane, in Formatted content or Unformatted content view, on the toolbar, click Keyword summary.



2. The layout changes and the application displays collapsed sections for only those parts of the document that contain hits. The layout also includes line numbers.



Note: If a document does not contain hits, the application does not collapse the sections, but does display line numbers.

Each section includes a number next to the header of the section to indicate the number of collapsed lines, as well as the following buttons:

• Expand more: Expands the section with several lines before and after a hit, providing additional textual context of a hit in the document.
• Collapse: Collapses the section. This button appears in place of the Expand more button after clicking that button.
• Expand all: Expands the entire section and allows you to view all content in a section.
• Collapse all: Collapses the entire section. This button appears in place of the Expand all button after clicking that button.
3. To revert to the standard view, on the toolbar in the View pane, click Keyword summary.

Browse pane: New Identities section

The Browse pane now includes a new Identities section. The identities that appear in this section are related to the Identity entity in a data model.

Note: If the Identities section does not appear in the Browse pane by default, you can add it to the Browse pane. To do so, from the Browse pane, select Options. In the Browse settings window, select Identities, and then click Save.

Translate: Italian available as a target translation language

You can now translate documents into Italian using the Microsoft or Google translation services available in the Translate tool or the Translate pane on the Documents page.

Case Setup > Conditional Templates: Add a Binders - Custom field

On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, you can now add the Binders - Custom field to a conditional template.

To add a Binders - Custom field to a conditional template:

1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, in the Add field list, select Binders - Custom.

Note: You can add only one Binders - Custom field to a coding template.

2. Click the Add field button.



3. In the Binders - Custom dialog box, select one or more binders and then click Save.



The Binders - Custom field appears at the bottom of the list of coding fields on the Coding fields page.

Tip: You can click anywhere on the row to drag and move the field to a new location in the template. You can click the blue link to adjust the issues in the Binders - Custom field.



4. The Binders - Custom field is then available in the Conditional Coding pane for the template, and reviewers can code documents to the binders in this field.

Case Setup > Conditional Templates > Coding fields: Add an Issues - Custom field

On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, you can now add the Issues - Custom field to a conditional template.

To add an Issues - Custom field to a conditional template:

1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, in the Add field list, select Issues - Custom.

Note: You can add only one Issues - Custom field to a coding template.

2. Click the Add button.



3. In the Issues - Custom dialog box, select one or more issues, optionally select the Include sub-issues check box before selecting a parent issue to include all of its child issues with it in the field, and then click Save.



The Issues - Custom field appears at the bottom of the list of coding fields.

Tip: You can click anywhere on the row to drag and move the field to a new location in the template. You can click the blue link to adjust the issues in the Issues - Custom field.



4. The Issues - Custom field is then available in the Conditional Coding pane for the template, and reviewers can code documents to the issues in this field.

To delete the Issues - Custom field from the template:

1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, select the check box next to the field.
2. On the toolbar, click Delete.

Case Setup > Conditional Templates > Coding fields: Add a Source/Attachments field

On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, you can now add the Source/Attachments field to a conditional template.

The Source/Attachments field displays a tree view of the document IDs of all source/attachment documents that are related to the active document. The document IDs of the related documents are links to open each document in a standalone window.

To add a Source/Attachments field to a conditional template:

1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, in the Add field list, select Source/Attachments.
2. Click the Add button.



The Source/Attachments field appears at the bottom of the list of coding fields.

Tip: You can click anywhere on the row and drag and move the field to a new location in the template.

3. The Source/Attachments field is then available in the Conditional Coding pane for the template, and reviewers can use the field to learn about the Source/Attachments documents that are related to the active document.

To delete a Source/Attachments field from the template:

Case Setup > Hierarchies: Preview a hierarchy

On the Case Setup > Hierarchies page, when you add a hierarchy, you can now preview the hierarchy before you save and run it to make sure that the hierarchy field and delimiter are useful.

The preview is limited to 10,000 documents and 1,000 nodes.

Note: You do not have to preview the hierarchy. After you set the properties for the hierarchy on the Properties page, you can skip to the Security page.

The hierarchy preview is available only when you add a new hierarchy. You cannot preview a hierarchy that you previously added. You can view the hierarchy in the Hierarchies section in the Browse pane on the Documents page.

Case Setup > Issues: Enhancements to cloning issues and child issues

You can now clone child issues as well as top-level issues. Previously, you could clone only top-level issues.

A Clone button is now available on the toolbar.

Previously, the Clone issue button was available next to the issue on the Case Setup > Issues page.

Note: You can clone only one top-level issue at a time. If you clone an issue, the application also clones the child issues and its subissues.

To clone a top-level issue:

1. On the Case Setup > Issues page, select a top-level issue.



2. On the toolbar, click Clone.
3. In the Clone issue window, confirm or modify the issue name.

The cloned issue appears in the list.

To clone a child issue:

1. On the Case Setup > Issues page, click the link for a top-level issue.
2. On the Child Issues page, select a child issue or issues.

Note: When you select a child issue, the application automatically selects any subissues of the child issue.

3. On the toolbar, click Clone.
4. In the Clone issue window, confirm or modify the issue name.
5. Click OK.

The cloned issue appears on the Case Setup > Issues > Child Issues page.

Case Setup > Issues: Move issues

You can now move top-level issues and child issues.

Note: If you move an issue, the application also moves the child issues and its subissues.

To move a top-level issue:

1. On the Case Setup > Issues page, select a top-level issue.



2. On the toolbar, click Move.
3. In the Move issues window, select a top-level issue or child issue destination for the issue you want to move.



4. Click OK.

The issue moves to the destination you selected.

To move a child issue:

1. On the Case Setup > Issues page, click the link for a top-level issue.
2. On the Child Issues page, select a child issue.

Note: When you select a child issue, the application automatically selects any subissues.

3. On the toolbar, click Move.



4. In the Move issues window, select a destination:
• A new top-level issue.
• An existing top-level or child issue.



5. Click OK.

The issue moves to the destination you selected.

Case Setup > People Identity: Updated user interface to enhance performance

The interface for the Case Setup > People Identity page (also referred to as the “Names Normalization” feature) has been updated to enhance performance when loading identities for large cases.

Previously, this page included a banner that displayed the following message: New people names have been added. Click Normalize to normalize the people names to an identity. View non-normalized names.

As of version 10.10.000, the following changes apply:

• The red banner and message no longer appear.
• The page now includes three tabs:
• Non-normalized: This tab displays the list of non-normalized names in the selected document set.
• Normalized: This tab displays all normalized names in the selected document set.
• All: This tab displays all normalized and non-normalized names in the selected document set.

The Download report and Assign identity buttons on the toolbar apply to the currently selected document set and tab.

Case Setup > System Fields: Italian now available as a target translation language

Italian is now available as an item for the Translation Languages field. If you grant a group permission to this field, group members can translate documents to Italian using the Translate tool or the Translate pane on the Documents page.

Manage Documents > Imports: Information about who created an import

On the Manage Documents > Imports page, a new column named Creator displays the name of the user who created an import. This information also appears on the Properties page for an import, under Import Details.

Manage Documents > Imports: Date format selected for a flat file import now appears on Properties page

The Date format that you selected for a flat file import on the Import Details page in the Import window now appears on the Properties page under Load File Details after the import.

Manage Documents > Ingestions: New system fields to support Nuix Engine multimedia file types

Three new system fields are now available on the Case Setup > System Fields page, as described in the following table. These fields are populated in Nuix Discover when you ingest the following multimedia file types using the Nuix Engine.

• Nuix Engine multimedia file type:
• ISO Media Type:
• Nuix Discover system field: [Meta] ISO Media Type
• Description: Type of media file
• Multimedia Video Codec:
• Nuix Discover system field: [Meta] Multimedia Video Codec
• Description: Compression standards used to code or decode a video file. Requires an FFmpeg plugin.
• Multimedia Audio Codec:
• Nuix Discover system field: [Meta] Multimedia Audio Codec
• Description: Compression standards used to code or decode an audio file. Requires an FFmpeg plugin.

Note: You can update to these fields when using the Imports feature.

Manage Documents > Ingestions: Bloomberg Mail XML files and TAR attachments no longer create duplicate documents

When you ingest Bloomberg Mail XML files (that is, not chat) and corresponding attachments (TAR), the application no longer ingests the TAR file separately.

Note: TAR is short for Tape Archive and is a file in the Consolidated Unix File Archive format.

Previously, the application ingested the TAR file separately, which resulted in duplicate email attachments in Nuix Discover after ingestion.

Portal Management > Errors: Enhanced performance and new check box to view legacy errors

In version 10.10.000, the application changed the method for storing errors and created a new table in the portal database to populate errors. This change was made to enhance performance.

To view the errors for versions up until version 10.9.005, select the See legacy errors check box.

Note: Errors are written only to the new table for versions 10.10.000 and higher.

Portal Management > Cases and Servers > Case cloning: Restricted user assignment setting now retained when cloning a case

When you clone a case, the application now retains the setting for the Restricted user assignment, which is available on the Properties page for a case.

Note: The application also retains the setting when you clone a case—even if you select the Clear data check box on the Case Details page in the Clone case window.

How to contact Nuix Support

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Supported upgrade paths

You can upgrade the following versions of Ringtail Legal and Ringtail to this version of Nuix Discover 10.x:

• Ringtail 8.0.1, 8.1, 8.2, 8.3, 8.3.1, 8.3.2, 8.4, 8.4.2, 8.5, 8.6
• Ringtail Legal 1.0.58

For versions of Ringtail Legal earlier than 1.0.57, you must first upgrade to Ringtail Legal 1.0.58, and then upgrade to Nuix Discover 10.x.

Note: When upgrading to Ringtail 8.6 or later from an earlier version, you must request an updated license.

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Nuix Discover support lifecycle for biweekly and quarterly releases

Note the following support lifecycle for biweekly and quarterly releases:

• Biweekly releases
• Nuix supports the last four biweekly releases.
• Example: 10.8.005, 10.8.004, 10.8.003, 10.8.002
• Quarterly releases
• Nuix supports the last four quarterly releases to on-premises clients.
• Example: 10.10, 10.9, 10.8, 10.7

Note: Nuix Discover provides service packs for quarterly releases for up to the latest four releases and for one year from the initial release date of the quarterly release.

Service parks for biweekly releases are provided for the four most recent biweekly releases.

For earlier releases that are no longer eligible for service packs, the Nuix Support Team provides best-effort support.

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Nuix Discover support lifecycle for Microsoft Windows Server and Microsoft SQL Server

The Nuix Discover support lifecycle for Microsoft products is communicated annually. For additional information about the Microsoft Lifecycle Policy, go to https://support.microsoft.com/en-us/lifecycle/search.

Important: Nuix Discover support for Windows Server 2016 and SQL Server 2016 ends on April 1, 2023.

The general support policy for Windows Server and SQL Server for Nuix Discover quarterly on-premises releases is as follows:

• Nuix Discover supports at least two versions of Windows Server and SQL Server for each release.
• Within one year of a newly released version of Windows Server or SQL Server, Nuix Discover supports those versions.
• Once Microsoft ends mainstream support for a version of Windows Server or SQL Server, Nuix Discover no longer support those versions.
• Nuix communicates a 12-month notice of support retirement with each quarterly on-premises release.

Note: For detailed information about client computer requirements, see the Nuix Discover - Client Computer Requirements guide for this release. For detailed system and hardware requirements, see the Nuix Discover - Hardware and System Requirements guide for this release. These guides are available on the Nuix Customer Portal.

Installation and deployment notes

For detailed information about client and system requirements, as well as upgrade and installation instructions for this release, see the following documents on the Nuix Customer Portal.

• Nuix Discover - Client Computer Requirements
• Nuix Discover - Hardware and System Requirements
• Nuix Discover - Upgrade Checklist
• Nuix Discover - Installation and Configuration Guide

Tools menu: Updates to the Load search file tool

This release includes the following updates to the Load search file tool:

• Support for the Page Label, [RT] MD5 HASH, and [RT] Family MD5 HASH fields.
• When using the Load search file tool on the Tools menu on the Documents page, as shown in the following figure, you can now search for documents that include a list of hash values by selecting the [RT] MD5 HASH or [RT] Family MD5 HASH field in the Field list. You can now also select the Page Label field from this list.



Note: Previously, you could select the Document ID or Entity ID, as well as the Main ID, options under ID Type. These options are now available in the Field list, shown in the previous figure.

If the application does not find matching documents or entities, the application indicates that on the Not Found page in the Load Search file window.

Tools menu: Renumbering tool

The Renumbering tool on the Tools menu on the Documents page is now located in the Processing group, as shown in the following figure. You can still search for the Renumbering tool using the search box.

Enhancements to search settings

On the Documents or Search pages, you can now rerun and change the context of your current search to display Renditions (instead of base documents), Threading, and Sources and attachments, as shown in the following figure.

Previously, the Renditions, Threading, and Sources and attachments buttons on the Documents and Search pages were non-clickable icons and indicated the search preferences settings that you set on the Search page or on the User name menu, but you could not click these icons. The icons are now clickable buttons that you can use to change the context of your current search.

After you click a button, the background changes from white to dark blue to indicate the change to your search results, for example, for Renditions, as shown in the following figure.

If you select the Threading button, the Sources and attachments button appears with a light blue background, as shown in the following figure, because threaded documents include sources and attachments.

Additional information

• The application captures any changes to the search settings in the search history.
• When you change your search settings for your current search using the buttons on the Documents or Search pages, the changes are not applied to your default search preferences that you typically set on the User name > Search preferences menu or using the Search preferences check boxes on the Search page.
• If an orange warning icon, as shown in the following figure, appears, it is not clickable. This warning indicates that your search contains one or more documents to which you do not have access, such as when accessing a previous search result that contains documents to which you no longer have access. Contact your administrator if you think that you received this warning in error.

Chat: Updated behavior for importing and displaying join and leave events

When a “join” or “leave” event is provided in a chat document, it is included as part of the conversation in the View pane in the Documents window as follows:

• Join and leave events in chat documents are displayed as regular messages, except:
• If no “sender” value is provided:
• For a join event, the message text is “JOINED: {recipient}.
• For a leave event, the message text is ”LEFT: {recipient}.
• If a “sender” value is provided:
• For a join event, the message text is “JOINED:{recipient} added by {sender}.
• For a leave event, the message text is ”LEFT: {recipient} removed by {sender}.
• The user listed to the left of the messages in the View pane is the recipient (the user who joined/left).
• If a join or leave event has multiple recipient values, the application creates a separate join or leave message for each recipient. Each message will have the same “sender” value.
• Join and leave events appear in the summary table at the top of the View pane as follows:
• JOI column header: Number of join events for each recipient.
• LEF column header: Number of leave events for each recipient.
• In Formatted content view, to highlight the join and leave events in the conversation as well as messages, select the JOI or LEF column header in the summary table. To highlight only join or leave events, select the value in the JOI or LEF column. An example is shown in the following figure.

Note: Chat documents are typically promoted from Nuix Workstation or Nuix Investigate® to Nuix Discover.

Analysis > Search Terms: Counts for hits apply only to base documents

On the Analysis > Search Terms page, the counts for hits now include only hits in base documents. Previously, the counts included hits in base documents and renditions.

Case Setup: Search Term Families: Hyphens now retained in search terms

On the Case Setup > Search Term Families page, when you include a hyphen in the Term label of a search term, for example, first-class, the application now retains the hyphen for the Term query, as shown in the following figure.

Previously, when you saved the search term, the application retained the hyphen for the Term label, but removed the hyphen from the Term query, as shown in the following figure.

To ensure that hyphens are retained, a portal or system administrator must also check that one of the following two options are selected under Hyphens on the Portal Management > Settings > Indexing: Options page (for the portal) or the Cases and Servers > [Name of case] > Indexing: Options page (for the case), as shown in the following figure.

• Treat as searchable characters
• Apply all rules

As an example, if you select Apply all rules, three entries are in the index for any text that includes a hyphen, and first-class is indexed as follows:

• first-class
• firstclass
• first class

Note: This has always been the case. This information serves only as a reference in the context of this update.

Case Setup > Search Term Families: Document count now includes only base documents

On the Case Setup > Search Term Families page, the Document count column now includes only base documents. Previously, the column included base documents and renditions.

Note: For this change to take effect, you must reprocess the search term families.

Manage Documents > Imaging - Automated: Updated Slipsheet count link to include additional documents with slipsheets

On the Manage Documents > Imaging – Automated page, when a user clicks on the link for a value in the Slipsheet count column, the search results that appear on the Documents page now include the search strings “Imaging Warnings” IS “Slipsheet - User-specified” and “Imaging Warnings” IS “Slipsheet - Imaging Failed”. In previous versions, these search strings were not included when a user clicked on the link in the Slipsheet count column.

Manage Documents > Imports: Preserve field mapping for one-to-many case fields

In previous versions, if a load file field was mapped to multiple Nuix Discover case fields (in the Import window on the Field Map page), only the first field mapping was preserved in subsequent import jobs using the same load file. Now, all field mappings are preserved when the user submits subsequent import jobs using the same load file.

As shown in the following figure, the [Meta] Document Kind field is mapped to two case fields, [Meta] Document Kind and Document Type.

Manage Documents > Ingestions: NIST list updated - September 2021

The Ingestions feature now uses an updated version of the NIST list, released in September 2021. For more information, go to https://www.nist.gov/itl/ssd/software-quality-group/national-software-reference-library-nsrl/nsrl-download/current-rds.

Manage Documents > Productions: Allow users to select placeholder page and font size

On the Production Rules page, users can now select the page and font size of placeholder pages in the Placeholder area. To make changes to the Placeholder area, in the Rules column, select Custom Placeholder. To determine the page size, under Placeholder, select either Letter or A4. To determine the font size, select a number in the Font size list. The default values for both of the fields are taken from case settings. Any changes you make to the Placeholder area on the Production Rules page override the defaults for that production.

Transcripts: Transcript search error now resolved: Requires reloading of affected transcripts

Previously, an error occurred when using the Find feature in Transcripts. The hits went to the wrong page or line number.

This issue is now resolved; however, you must reload any affected transcripts that you loaded into the case for Nuix Discover versions 10.5.001 through 10.9.004.

Cases and Servers > Cases > [Name of case] > Indexing options: Message appears in banner

The following message appears on the following pages on the Cases and Servers > Cases > [Name of case] page, as shown in the following figure: Case indexes must be rebuilt for changes to take effect after making updates on this page.

• Indexing: Options
• Indexing: Noise Words
• Indexing: Alpha Standard
• Indexing: Alpha Extended
• Indexing: Thesaurus
• Indexing: Stemming Rules
• Indexing: File Type Rules

Cases and Servers > Cases > [Name of case] > Content: File Type Rank: Message appears in banner

On the Cases and Servers > Cases > [Name of case] > Content: File Type Rank page, as shown in the following figure, the following message now appears in the banner: Indexing and Enrichment must be run for changes to take effect after making updates on this page.

Portal Management > Reports: New non-billable column on the Usage and Hosted Details pages

On the Usage and Hosted Details pages, the Non-billable column now appears by default next to the Case column, as shown in the following figure.

You can filter the results in this column. By default, the column is not filtered. Set the filter to No to show only cases that are billable.

If you select Yes, the non-billable cases appear in this column and a dot indicates that the case is non-billable, as shown in the following figure.

Portal Management > Processing: Updates to the Daily Case Metrics job

When a scheduled Daily Case Metrics job runs on the last day of the month, the job now includes all stages, that is, the same stages as a full Gather Case Metrics job. So, the Daily Case Metrics job updates all of the “active” statistics and the statistics for Orphan (GB), Missing (GB), File transfer data (GB), and Archive data (GB).

Connect API Explorer: Update to the importJobAddDocuments mutation for identifying page number when applying annotations

The importJobAddDocuments mutation now has an additional field for identifying the page number locating applied annotations called filePageNumber. This field must contain a positive integer and must be within the range of total pages contained within the document. For example, if the document is a 5-page PDF, the filePageNumber field can contain any number between 1 and 5. If the filePageNumber value is set to 2, the annotation appears on the second page of the PDF.

Note: The filePageNumber field replaces the use of the filename field.

Sample mutation using the fileName field:

mutation MyOldSampleMutation {
  importJobAddDocuments (
    caseId: 5,
    input: {
      rdxJobId: 38
      documents: {
        documentId: “Annotation_00000001”,
        pageaction: InsertUpdate,
        pages: {
          pagenumber: 1,
          path: “\\Annotation_00000001.pdf”,
          pagelabel: “Annotation_00000001”
          },
        annotations: {
          fileName: “Annotation_00000001.pdf”,
          pageNumber: 2,
          type: REDACTION,
          name: “Attorney-Client Privilege”,
          label: “Attorney-Client”,
          color: BLACK,
          x1: 100,
          x2: 400,
          y1: 100,
          y2: 400
        }
      }
    }) {
    documentCount
  }
}

Sample mutation using the filePageNumber field:

mutation MyNewSampleMutation {
  importJobAddDocuments (
    caseId: 5,
    input: {
      rdxJobId: 38
      documents: {
        documentId: “Annotation_00000001”,
        pageaction: InsertUpdate,
        pages: {
          pagenumber: 1,
          path: “\\Annotation_00000001.pdf”,
          pagelabel: “Annotation_00000001”
        },
        annotations: {
          pageNumber: 1,
          filePageNumber: 2,
          type: REDACTION,
          name: “Attorney-Client Privilege”,
          label: “Attorney-Client”,
          color: BLACK,
          x1: 100,
          x2: 400,
          y1: 100,
          y2: 400
        }
      }
    }) {
    documentCount
  }
}

Connect API Explorer: Update to the importJobAddDocuments mutation with new notes field

The importJobAddDocuments mutation has a notes field, that is an array, for specifying what notes will populate in the document.

Required fields:

• Id: A unique integer value assigned to each individual note within a document.
• noteText: The text of the note.

Optional fields:

• category: A category identifying the note. If the entered category does not already exist, the new value creates a new category. When providing no new value, the category is set to Uncategorized.
• userName: The name of the user who created the note. The userId automatically populates with the note when the provided name matches a known user. Otherwise, the note assignment is set to the user performing the import.
• dateStamp: The date of the notes last modification. If left blank, the date populates with the current date and time.
• isPrivate: Indicates whether the note is a private note.
• parentNoteId: The ID of the parent note for a note that is a reply.
• noteTextHtml: Contains the text of the note with the HTML formatting.
• isAnnotation: Indicates if the note is an annotation that appears on a specific page of the document.
• pageNumber: For notes that are annotations, this value indicates the page record on which the note is located.
• filePageNumber: For notes that are annotations, this value indicates the page of the file on which the note is located.
• Coordinates:
• x1: The x1 coordinate for the note.
• x2: The x2 coordinate for the note.
• y1: The y1 coordinate for the note.
• y2: The y2 coordinate for the note.

Sample notes mutation:

mutation MyNoteSampleMutation {
  importJobAddDocuments (
    caseId: 5,
    input: {
      rdxJobId: 300,
      documents: {
        documentId: “Annotation_00000001”,
        pageaction: InsertUpdate,
        pages: {
          pagenumber: 3,
          path: “\\Annotation_00000001.pdf”,
          pagelabel: “Annotation_00000001”
        },
        notes: {
          id: 10,
          noteText: “Sample note text”,
          x1: 10,
          x2: 20,
          y1: 10,
          y2: 20
        }
      }
    }) {
    documentCount
  }
}

Connect API Explorer: importJobAddConversations mutation has new chatHistoryStart field

The importJobAddConversations mutation contains a new chatHistoryStart field that identifies the date and time of a participant’s earliest access to messages in a chat. The chatHistoryStart field is optional, and if provided, all conversation records that are part of the same overall conversation will have the same value for a participant.

Sample chat participant mutation:

mutation MyChatMutation {
importJobAddConversations (
  caseId: 5,
  input: {
    rdxJobId: 10,
    conversations: {
      conversationId: “Conv123456”,
      participants: [
        {
          id: “test1@nuix.com”,
          chatHistoryStart: “2020-02-03T13:49:06.846Z”
        }
        ],
      channelName: “TestChannel”,
      documentId: “DocID00001”,
      fields: {
        name: “Custodian”,
        values: “Test1”
      }
    }
  }) {
    conversationCount
  }
}

Connect API Explorer: Query update for retrieving caseUserCategory data

The query function contains a new caseUserCategory field that will retrieve the user categories and case groups of each user assigned to the identified case.

Sample query:

query UserCaseReport {
  cases(id: 7096) {
    id
    name
    groups {
      id
      name
      users {
        id
        caseUserCategory
      }
    }
  }
}

Sample query results:

{
  “data”: {
    “cases”: [
      {
        “id”: 7096,
        “name”: “1_Acme6_PM2”,
        “groups”: [
          {
            “id”: 1,
            “name”: “NDAdmin”,
            “users”: [
              {
                “id”: 7436,
                “caseUserCategory”: “GroupMember”
              },
              {
                “id”: 7437,
                “caseUserCategory”: “GroupMember”
              },
              {
                “id”: 7438,
                “caseUserCategory”: “GroupMember”
              },
              {
                “id”: 7439,
                “caseUserCategory”: “GroupMember”
              },
              {
                “id”: 7440,
                “caseUserCategory”: “GroupMember”
              },
              {
                “id”: 6311,
                “caseUserCategory”: “Administrator”
              },
              {
                “id”: 1,
                “caseUserCategory”: “Administrator”
              },
              {
                “id”: 101,
                “caseUserCategory”: “Administrator”
              },
              {
                “id”: 6,
                “caseUserCategory”: “GroupMember”
              },
              {
                “id”: 5289,
                “caseUserCategory”: “Administrator”
              }
            ]
          },
          {
            “id”: 2,
            “name”: “Review”,
            “users”: [
              {
                “id”: 6311,
                “caseUserCategory”: “Administrator”
              }
            ]
          }
        ]
      }
    ]
  }
}

How to contact Nuix Support

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Supported upgrade paths

You can upgrade the following versions of Ringtail Legal and Ringtail to this version of Nuix Discover 10.x:

• Ringtail 8.0.1, 8.1, 8.2, 8.3, 8.3.1, 8.3.2, 8.4, 8.4.2, 8.5, 8.6
• Ringtail Legal 1.0.58

For versions of Ringtail Legal earlier than 1.0.57, you must first upgrade to Ringtail Legal 1.0.58, and then upgrade to Nuix Discover 10.x.

Note: When upgrading to Ringtail 8.6 or later from an earlier version, you must request an updated license.

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Nuix Discover support lifecycle for biweekly and quarterly releases

Note the following support lifecycle for biweekly and quarterly releases.

• Biweekly releases
• Nuix supports the last four biweekly releases.
• Example: 10.8.005, 10.8.004, 10.8.003, 10.8.002
• Quarterly releases
• Nuix supports the last four quarterly releases to on-premises clients.
• Example: 10.8, 10.7, 10.6, 10.5

Note: Service packs for quarterly releases are provided for up to the latest four releases and for one year from the initial release date of the quarterly release.

Service parks for biweekly releases are offered for the four most recent biweekly releases.

For earlier releases that are no longer eligible for service packs, the Nuix Support Team will provide best-effort support.

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Nuix Discover support lifecycle for Microsoft Windows Server and Microsoft SQL Server

The Nuix Discover support lifecycle for Microsoft products is communicated annually. For additional information about the Microsoft Lifecycle Policy, go to https://support.microsoft.com/en-us/lifecycle/search.

Important: Nuix Discover support for Microsoft Windows Server 2016 and Microsoft SQL Server 2016 will be discontinued on April 1, 2023.

The general support policy for Microsoft Windows Server and Microsoft SQL Server for Nuix Discover quarterly on-premises releases is as follows:

• Nuix Discover will support at least two versions of Microsoft Windows Server and Microsoft SQL Server for each release.
• Within one year of a newly released version of Microsoft Windows Server or Microsoft SQL Server, those versions will be supported by Nuix Discover.
• Once Microsoft ends mainstream support for a version of Microsoft Windows Server or Microsoft SQL Server, those versions will no longer be supported by Nuix Discover.
• A 12-month notice of support retirement will be communicated with each quarterly on-premises release.

Note: For detailed information about client computer requirements, see the Nuix Discover - Client Computer Requirements guide for this release. For detailed system and hardware requirements, see the Nuix Discover - Hardware and System Requirements guide for this release. These guides are available on the Nuix Customer Portal.

For detailed information about client and system requirements, as well as upgrade and installation instructions for this release, see the following documents on the Nuix Customer Portal.

• Nuix Discover - Client Computer Requirements
• Nuix Discover - Hardware and System Requirements
• Nuix Discover - Upgrade Checklist
• Nuix Discover - Installation and Configuration Guide

View pane > Chat: When sorted by Document Title, conversations now appear in order, regardless of length

In previous versions, when viewing a chat conversation in the View pane on the Documents page, if you looked at a set of documents that represented all of the parts of a conversation and sorted by Document Title, the conversations would not appear in order if there were more than nine parts. This behavior occurred because the first number that appeared in the Document Title was not padded.

In this release, if the Document Title reads “Part X of Y,” the X value is padded to the same number of digits as the Y value. As a result, conversations with more than nine parts are displayed in order.

Example:

• Previous versions: Part 1 of 12
• This and future versions: Part 01 of 12

View pane > Chat: Join and leave events and reactions displayed

If an administrator configures the Connect API Explorer importJobAddMessageEvents mutation to include join and leave events for imported chat messages, these events now appear in the View pane on the Documents page.

Similarly, if an administrator enters the value Reaction in the type input field in the importJobAddMessageEvents mutation, reactions to messages appear in the View pane. A “reaction” to a text message is typically a heart, thumbs up, thumbs down, laugh, exclamation point, and so forth, rather than a typed reply to the message. The following figure shows the View pane with join and leave events as well as reactions.

For information about the importJobAddMessageEvents mutation, see Connect API Explorer: Include reaction event in importJobAddMessageEvents mutation in this document.

Note: You can also view chat documents in Nuix Discover when you promote chat items from Nuix Workstation or Nuix Investigate® to Nuix Discover.

Join events and counts appear in the JOI column. Leave events and counts appear in the LEF column. Reactions appear in line with the message the user responded to. Reactions appear as text (“Thumbs up,” “Like”) rather than images.

Case Setup > Hierarchies: Hierarchies feature now supports user-created text and memo fields

Case administrators can now add any user-created text and memo fields to a hierarchy.

Group leaders who have permission to access the Hierarchies feature on the Case Setup page can add only the user-created text and memo fields that they have access to.

Manage Documents > Automated Imaging: User interface changes to Settings

This release includes two user interface changes to the Manage Documents > Imaging-Automated > Settings window.

• On all pages of the Settings window, to validate the required settings, you must click Save on each page of the window.
• On the Excel page, in the Margins section, the settings for each of the options have changed from radio buttons to lists, as shown in the following figure.
• In the updated user interface, a list with the following two options appears for each of the Margin settings: Original and Custom. If you select Custom, a text box appears to the right of the list. Use this text box to specify the margin size.

Manage Documents > Imports: Delimiter for imported or new one-to-many fields defaults to a semicolon

On the Field Map page in the Import window, when you set the Action to Import to or New for one-to-many fields, the value in the Delimiter column now defaults to a semicolon ; (59), as shown in the following figure.

Note: Cloned import jobs retain the original delimiter settings.

Manage Documents > Imports: User interface usability enhancement

When you add an import job using the Import window in the Manage Documents section, you can now click outside of the Import window and the window will no longer close. To close the window, you can click Cancel or submit the job.

Important: Previously, if you clicked outside of the window, the window closed. You could, however, click the Add button on the toolbar on the Manage Documents > Imports page to retrieve your in-progress settings. That is no longer the case.

Manage Documents > Imports: Retain in-progress settings for your import job

You can now retain the settings for an in-progress import job.

To retain the in-progress settings for your Import job:

1. In the Import window, on the Schedule page, select Place on hold, and then click Save as draft, as shown in the following figure.



The window closes.

2. To continue with the import job settings, on the Manage Documents > Imports page, in the Name column, click the link for your draft import job.

Manage Documents > Imports: New level separator for levels-based Document ID

The new Level separator option, shown in the following figure, is available on the Document ID page in the Import window, if you select Get Next - Levels based under Document ID.

This option uses a period by default, but you can replace the period with a different single character.

Note: If you provide a disallowed character, the application notifies you.

Tip: This setting is used to separate the levels in the Document ID. To view the format of the Document ID, click the View Document ID link.

After the job completes, this setting also appears on the Properties page of the import job.

Portal Management > Cases and Servers: Edit the billable status for multiple cases

On the Portal Management > Cases and Servers page, you can now edit the billable status for multiple cases.

To edit the billable status for multiple cases:

1. On the Portal Management > Cases and Servers page, select one or more cases.
2. On the toolbar, from the More menu, select Bulk edit.
3. In the Bulk edit window, on the Billable Status page, select the Replace with option, as shown in the following figure.

Note: If you select the No change option, the non-billable status is not changed for any cases.



4. In the list, select Billable or Non-billable.
5. Click Save.

Portal Management > Cases and Servers > Cases: Non-billable column

A new column named Non-billable is now available on the Portal Management > Cases and Servers > Cases page.

You can filter the column to display billable or non-billable cases, as shown in the following figure.

If a case is non-billable, a black dot appears in this column for a case or cases.

Note: A system administrator can select the Non-billable option on the Properties page for a case.

Portal Management > Errors: New option to view errors for the last one (1) day

On the Portal Management > Errors page, you can now view errors for the last one (1) day, as shown in the following figure.

Portal Management > Settings: New portal option for authentication to a secured Elasticsearch cluster

The following new portal option, shown in the following figure, is available on the Portal Management > Settings > Portal Options page: User audit log service Elasticsearch API key.

The user audit log service now supports using an Elasticsearch API key and ID for authenticating to a secured Elasticsearch cluster. To connect to a secured Elasticsearch cluster, enter the Elasticsearch API key and API ID as a JSON string into this setting.

To configure this option:

1. On the Portal Management > Settings > Portal Options page, in the User audit log service Elasticsearch API key box, provide a JSON string {“ElasticsearchApiKey”:“*******”,“**ElasticsearchApiId”:“*******”} containing the Elasticsearch API key and API ID to use for authentication.



2. Click Save.

Portal Management > Cases and Servers > Cases > Case Options: New case option to enable PDF compression for exports

A new option named Export - PDF compression is now available on the Portal Management > Case and Servers > Cases > Case Options page.

Note: This option is selected by default.

If selected, PDF documents are compressed before being exported in order to reduce the size of the export. In certain cases where PDF exports are running but stop progressing, clearing this option may help resolve the issue.

Portal Management > Reports: New column for Parent Organizations

On the Usage, Hosted Details, and Users pages in the Portal Management > Reports section, system administrators can now configure the table to display the Parent Organization column and information. This column does not appear by default.

The previous Organization column is now used to display information about a suborganization of the parent organization.

If configured to appear in the table, the Parent Organization column appears to the left of the Organization column, as shown in the following figure.

Connect API Explorer: Include reaction event in importJobAddMessageEvents mutation

When using the importJobAddMessageEvents mutation, if the value Reaction is entered in the type input field, the content of the message event is included as a reaction to the conversation. These reactions appear immediately after the parent message as defined by the parentEventID field. If the message has both replies and reactions, all reactions appear first.

Note: Be aware that some replies may also have reactions, and reactions are not counted in the message counts.

The following is an example of the message event import job to input the message events and retrieve a total count of those events.

Sample mutation:

mutation MySampleMutation {
  importJobAddMessageEvents
  (
    caseId: 5,
    input: 
    {
      rdxJobId: 52090,
      messageEvents:
      {
        eventId: “12001”,
        parentEventId: “Parent120”
        conversationId: “121212”,
        content: “”:like:“,
        type: ”Reaction“
      }
    }
  ) 
  {
    messageEventCount
  }
}

Sample mutation results:

{
  ”data“: {
    ”importJobAddMessageEvents“: {
      ”messageEventCount“: 1
    }
  }
}

Connect API Explorer: Import binders using the importJobAddDocuments mutation

The importJobAddDocuments mutation contains a new binders object allowing users to populate existing binders as well as create new binders. If the user provides a binder value that matches an existing binder, the document will be added to the existing binder. Otherwise, a new binder is created. Permissions will not be assigned to any new binders generated, are set as shared, will not be security override type binders, and will not be mobile binders. If a binder name already exists, a new binder will not be created.

Sample mutation:

mutation MySampleMutation{
  importJobAddDocuments(caseId: 4070,
  input: {
    rdxJobId: 4128,
    documents: {
      documentId: ”ACTEST_00000001“,
      binders: {
        values: [”Binder 1“,”Binder 2“]
      },
      fields: {
        name: ”All Custodians“,
        action: Append,
        values: ”Custodian from API“
      }
    }
  }){
    documentCount
  }
}

Connect API Explorer: Import issues using the importJobAddDocuments mutation

The importJobAddDocuments mutation contains a new issues object allowing users to populate existing issues as well as create new issues. If the user provides an issue value that matches an existing issue, the document will be added to the existing issue. Otherwise, a new issue is created. Permissions will not be assigned to any top-level issues.

Note: The issue values field should contain the full issue path, where the issue depth is indicated with the backslash or forward-slash characters, as shown in the following sample mutation.

Sample mutation:

mutation MySampleMutation{
  importJobAddDocuments(caseId: 4070,
  input: {
    rdxJobId: 4128,
    documents: {
      documentId: ”ACTEST_00000001“,
      issues: {
        values: [”Top Issue/subissue 1“,”Top Issue/subissue 2“]
      },
      fields: {
        name: ”All Custodians“,
        action: Append,
        values: ”Custodian from API“
      }
    }
  }){
    documentCount
  }
}

Connect API Explorer: Generate levels based on Document ID in importJobCreate mutation

In the importJobCreate mutation, there is a new LevelBased option within the documentIdType field. When creating an import job that is LevelBased, the specified docId will be the selected levels, with each separated by the character indicated in the levelSeparator field. After the last level, the levelSeparator character is added and a sequential padded number is added to each document.

For example, if three documents are loaded to level Imports/API/0001, and the levelSeparator is the period character, and the levelBasedPadding is set to the number four, the docId values will be Imports.API.0001.0001, Imports.API.0001.0002, and Imports.API.0001.0003.

Note: The levelSeparator value can only be a single character and must be allowable in a docId. If a character is not entered, the default is a period.

The levelBasedPadding value can only be between 3 and 6. If a value is not entered, the default is 4.

Sample mutation:

mutation MySampleMutation {
  importJobCreate (
    caseId: 5,
    input: {
      levelSeparator: ”.“,
      levelBasedPadding: 4,
      documentIdType: LevelBased,
      level: ”Imports/API/0001&ld”quo;
    }
  ) {
    rdxJobId
  }
}

Login Service version 2.5.7 is available and required

• The Login Service requires configuration changes and MUST be upgraded to version 2.5.7 BEFORE upgrading to Nuix Discover version 10.8.005.

Important: For detailed instructions on configuring and upgrading the Login Service to version 2.5.7, see the Nuix Discover 10.8 Installation and Configuration Guide and the Nuix Discover 10.8 Upgrade Checklist, which are available for download on the Nuix Customer Portal.

• This version includes various security enhancements and is fully compatible with Nuix Discover 10.8.004.

Updates to the User Audit Log Service

The following updates have been made to the User Audit Log Service:

• The User Audit Log Service is now version 1.4.3.
• This version of the service now supports Elasticsearch version 7.13.3.
• The service now dynamically detects the Elasticsearch version and no longer requires an environment variable setting.
• An upgrade to this version of the service is optional.

Nuix Discover Deployer version 3.2.43 is now available

• This version of the Deployer includes the ability to run in a FIPS environment in addition to other security enhancements.
• This version resolves the following issues:
• TLNAIL-85: SQL server name field values are case sensitive, which can cause rs_tempdb upgrade failures.
• TLNAIL-105: A warning is not displayed if the Coordinator publish step fails to update the URL rewrite rule.
• The upgrade to this version is optional.

How to contact Nuix Support

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Supported upgrade paths

You can upgrade the following versions of Ringtail Legal and Ringtail to this version of Nuix Discover 10.x:

• Ringtail 8.0.1, 8.1, 8.2, 8.3, 8.3.1, 8.3.2, 8.4, 8.4.2, 8.5, 8.6
• Ringtail Legal 1.0.58

For versions of Ringtail Legal earlier than 1.0.57, you must first upgrade to Ringtail Legal 1.0.58, and then upgrade to Nuix Discover 10.x.

Note: When upgrading to Ringtail 8.6 or later from an earlier version, you must request an updated license.

Nuix Discover support lifecycle for biweekly and quarterly releases

Note the following support lifecycle for biweekly and quarterly releases.

• Biweekly releases:
• Nuix supports the last four biweekly releases.
• Example: 10.8.005, 10.8.004, 10.8.003, 10.8.002
• Quarterly releases:
• Nuix supports the last four quarterly releases to on-premises clients.
• Example: 10.8, 10.7, 10.6, 10.5

Note: Service packs for quarterly releases are offered for up to the latest four releases and for one year from the initial release date of the quarterly release.

Service parks for biweekly releases are offered for the four most recent biweekly releases.

For earlier releases that are no longer eligible for service packs, the Nuix Support Team will provide best-effort support.

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Nuix Discover support lifecycle for Microsoft Windows Server and Microsoft SQL Server

The Nuix Discover support lifecycle for Microsoft products is communicated at the beginning of each year.

Note: For additional information about the Microsoft Lifecycle Policy, go to https://support.microsoft.com/en-us/lifecycle/search.

The general support policy for Microsoft Windows Server and Microsoft SQL Server for Nuix Discover quarterly on-premises releases is as follows:

• Nuix Discover will support at least two versions of Microsoft Windows Server and Microsoft SQL Server for each release.
• Within one year of a newly released version of Microsoft Windows Server or Microsoft SQL Server, those versions will be supported by Nuix Discover.
• Once Microsoft ends mainstream support for a version of Microsoft Windows Server or Microsoft SQL Server, those versions will no longer be supported by Nuix Discover.
• A 12-month notice of support retirement will be communicated with each quarterly on-premises release.

Note: For detailed information about client computer requirements, see the Nuix Discover - Client Computer Requirements guide for this release. For detailed system and hardware requirements, see the Nuix Discover - Hardware and System Requirements guide for this release. These guides are available on the Nuix Customer Portal.

Browse: All Custodians

The Browse pane now includes a section named All Custodians, as shown in the following figure.

This section appears by default for new users and is located under the Assignments section.

Note: If a user does not have access to the All Custodians system field, the All Custodians section appears, but does not contain any values.

Note: Existing users must add the All Custodians section to the Browse pane.

Use the following procedure to add the All Custodians section to the Browse pane.

1. On the Documents page, in the Browse pane, on the menu on the toolbar, select Options.
2. In the Browse settings window, select the check box next to All Custodians, and then click Save.

The All Custodians section appears in the Browse pane.

Search for entity IDs using the Load search file tool

You can now search for a list of entity IDs using the Load search file tool on the Tools menu on the Documents page. Previously, you could search only for Document IDs or Main IDs. As the source, you can now enter text. Previously, you could upload only a text file.

Use the following procedure to search for entity IDs.

1. On the Tools menu on the Documents page, select Load search file.
2. In the Load search file window, on the New Search page, in the Results with this entity list, select a data model entity, for example, Person, as shown in the following figure.

Note: Document is the default selection.



Note: After you select an entity ID, the option under ID Type changes to the entity type that you selected, as shown in the following figure.



3. Under Source, do one of the following:

Note: For either method, each line must contain a single entity ID or an entity ID range. To load a range of IDs, provide the first ID and the last ID of the range, separated by a vertical bar (|). Example: Person-02068|Person-02077.

• To upload a .txt file, leave the Text File option selected, click Browse, select a file, and then click Open.

Note: The file must be in a text (.txt) format.

• To enter text for your search, select Enter Text, and then enter text in the box, for example, as shown in the following figure.



4. Click Next.

The results appear on the Results page, as shown in the following figure.



Tip: You can click the link for the documents to access them on the Documents page.

If any documents were not found, you can view the results on the Not Found page.

5. Click Finish.

Case Setup > System Fields: New fields for chat

The following two new system fields are populated in Nuix Discover for chat items promoted from Nuix Workstation or Nuix Investigate® to Nuix Discover (SaaS).

• [Meta] Chat Conversation Start Date: This is the date of the first message in all parts of the conversation. For a conversation that is not split, or the first part of a split conversation, this will always be the same as the [Meta] Chat Start Date.
• [Meta] Chat Conversation Start Time: This is the time of the first message in all parts of the conversation. For a conversation that is not split, or the first part of a split conversation, this will always be the same as the [Meta] Chat Start Time.

Manage Documents > Imaging: Support for HEIC and HEIF files

The Imaging feature now supports High Efficiency Image Container (HEIC) and High Efficiency Image Format (HEIF) file types.

Manage Documents > Imports: [RT] DPM File ID and Evidence Job ID fields prevented from being imported

Nuix Discover now prevents you from importing the following fields:

• [RT] DPM File Id
• Evidence Job ID

Note: If you try to import these fields, Nuix Discover displays an error message.

Manage Documents > Imports > Flat files: Create source and attachment relationships for any Document ID option

When performing an import using a flat file, you can now create a source and attachment relationship for any of the Document ID options on the Document ID page in the Import window:

• Existing Document ID

Note: Previously, the Source and attachment relationship list, shown in the following figure, was available only if you selected Existing Document ID under the Document ID options.

• Get Next - Levels Based
• Get Next – Sequential

If you select the Get Next - Levels Based or Get Next - Sequential option under Document ID, and select Parent Doc ID, Attachment Doc IDs, or Family Range in the Source and Attachment relationship list, a new Source and Attachment Document ID list appears, as shown in the following figure.

Note: The options in this list are based on the column names of the load file. This setting determines which field to use as the initial document ID when determining source and attachment relationships.

Note: The Source and Attachment Document ID list does not appear if you select None or LFP in the Source and Attachment relationship list. It also does not appear if you select the Existing Document ID option under Document ID.

After you run the import job, the settings you applied on this page appear on the Imports > Properties page.

Note: The Connect API Explorer already supports creating source and attachment relationships when you assign sequential Document ID values.

Manage Documents > Imports: Users can map fields to binders and issues

When importing flat files or MDB files into Nuix Discover, users can now map fields to binders or issues. In the Import window, on the Field Map page, users can click the Case field column and select Binder or Issue, as shown in the following figure.

• To map fields to binders and issues when importing an MDB load file, on the Import > Fields page, select Custom map imported fields to case fields.
• Fields must be the PICK type to be mapped to binders.
• Fields must be the TEXT type to be mapped to issues.
• If a user selects the Binder or Issue and one does not already exist, the application creates it.
• Binders created through Imports are always shared binders. They are not security binders or mobile binders.
• Permissions are not assigned for new binders or top-level issues.
• When updating existing documents, the application treats binders and issues the same as one-to-many fields.

Manage Documents > Ingestions: Documents with “un-executed code” messages no longer coded as Corrupted

The application will no longer code documents with Corrupted in the [Meta] Processing Exceptions field if they generate only the following messages during import:

• PDF Portfolio contains un-executed code that may generate text.
• PDF contains un-executed JavaScript code that may generate text.

These messages appear in the [RT] Ingestion Exception Detail field.

Note: If the import process results in one or both of these messages along with any other error messages, the application will code the affected document as Corrupted.

Manage Documents > Ingestions: Improved error handling in Ingestions

If an Ingestions job encounters only empty files, the Standardizing Data stage fails with the following message: “Error occurred: Nothing to process. Warning: The join order has been enforced because a local join hint is used.” The overall status of the job is Completed with Warnings.

If the application completes an ingestions job with unprocessed files, and the unprocessed files are resubmitted but contain no data, the application finishes the resubmission job as described above, and the job’s Properties page displays the statistics from the initial job.

Manage Documents > Productions: Redaction label font size option

When creating a production, you can now set a font size for the redaction label. The Font size setting is available on the Manage Documents > Productions > Redactions page, as shown in the following figure.

Note: Previously, the font size you set for endorsements controlled the font size for footers, headers, and the redaction label. Now, you can set a different font size for the redaction label than for footers and headers.

• The default font size is 18 and can be any font size between 6 and 72. A value is required.
• The application applies the font size setting to all redaction labels.

Manage Documents > Renumbering: Capture all jobs in the Renumbering ID field

The Renumbering ID field now captures the Job ID of all Renumbering jobs. In previous versions, only the latest job was retained.

Manage Documents > Renumbering: Documents with a page count of 0 or null are excluded from the renumbering job

If you run a renumbering job, if documents in a job have records with a page count of 0 or null, they are excluded from the job.

A new status named Has no page count is now available on the Exclusions page in the Renumbering window, under Documents that must be excluded, as shown in the following figure. If the application detects documents that do not have a page count, a number appears in parentheses next to the Has no page count line and the document is excluded from the renumbering job.

Manage Documents > Renumbering: Users can modify settings for the “Document ID plus page number” endorsement option

In previous versions, on the Endorsement page in the Renumbering window, when the user selected Document ID plus page number for one or more of the header or footer values, the application previously added the number to the Document ID in this format: -00001 (a hyphen with a five-digit padded page number).

With this release, users can modify the character that appears before the page number (the hyphen) by entering a character in the Character before page number box, as shown in the following figure. Users can also modify the number of padding digits by entering a new number in the Page number padding box. For example, if the character is “_” (underscore) and the padding is 4, the page number part of the endorsement would be “_0001”.

Portal Management > User Administration: Organization selection required if organization security is enabled

As a portal administrator, when you add a new user, if organization security is enabled for the portal that you manage, you must select an organization or suborganization.

Portal Management > Cases and Servers: Bulk edit cases

System administrators can now change the following properties for multiple cases in one action:

• IP Address Rule
• Database Server
• Analysis Server
• Image Repository
• Index file Repository
• File transfer Repository
• Archive Repository

Note: This feature is available only for cases with a status of valid or inactive.

Use the following procedure to change the settings for multiple cases.

1. On the Portal Management > Cases and Servers page, select one or more cases.
2. On the toolbar, on the More menu, select Bulk edit, as shown in the following figure.



The Bulk edit window appears, as shown in the following figure, and displays the IP Address Rule page.

Note: The settings on most of the pages in the Bulk edit window follow the same pattern, with the exception of the File transfer Repository page. The default option for all pages in the Bulk edit window is No change.

3. To change the setting on the IP Address Rule page, do the following:
• Select Replace with, and then select a new value from the list.

Note: The IP Address Rule settings are the values that are allowed for all of the organizations that are linked to the selected cases.

• To save your changes and exit the window, click Save.

Note: When you click Save, the application creates a case edit job.



4. To change the setting on the Database Server page, do the following:
• In the navigation pane, click Database Server.
• On the Database Server page, select Replace with, and then select a new value from the list.
• To save your changes and exit the window, click Save.

Note: When you click Save, the application creates a case edit job.

5. To change the setting on the Analysis Server page, do the following:
• In the navigation pane, click Analysis Server.
• On the Analysis Server page, select Replace with, and then select a new value from the list.
• To save your changes and exit the window, click Save.

Note: When you click Save, the application creates a case edit job.

6. To change the setting on the Image Repository page, do the following:
• In the navigation pane, click Image Repository.
• On the Image Repository page, select Replace with, and then select a new value from the list.
• To save your changes and exit the window, click Save.

Note: When you click Save, the application creates a case edit job.

7. To change the setting on the Index file Repository page, do the following:
• In the navigation pane, click Index file Repository.
• On the Index file Repository page, select Replace with, and then select a new value from the list.
• To save your changes and exit the window, click Save.

Note: When you click Save, the application creates a case edit job.

8. To change the setting on the File transfer Repository page, as shown in the following figure, do the following:
• To override the existing setting, select Override with, and then select a value from the list. Or, to add a new value, select Add new value, and then select a new value from the list.

Note: You can select multiple values when you override the settings or add a new value.

• To save your changes and exit the window, click Save.

Note: When you click Save, the application creates a case edit job.



9. To change the setting on the Archive Repository page, do the following:
• In the navigation pane, click Archive Repository.
• On the Archive Repository page, select Replace with, and then select a new value from the list.
• To save your changes and exit the window, click Save.

Note: When you click Save, the application creates a case edit job.

Portal Management > Cases and Servers: New case option: Disable downloading external resources during text extraction

The following new case option, shown in the following figure, is available on the Portal Management > Cases and Servers > [Case] > Case Options page:

Disable downloading external resources during text extraction

Select this option to block external web calls during text extraction when HTML links are encountered, for example, when using the Predictive Coding feature.

Note: This option is cleared by default.

Connect API Explorer: Use importJobAddDocuments mutation to populate All Custodians, All Evidence IDs, or All File Paths

When using the importJobAddDocuments mutation, if the fields array for a document is imported with a name value of All Custodians, All Evidence IDs, or All File Paths, and the action field is set to InsertUpdate or Append, any values not already coded for the document are added to the document.

Note: Users cannot delete the All Custodians, All Evidence IDs, or All File Paths values from a document using the importJobAddDocuments mutation.

The following is an example of how to add the All Custodians value to the name field for a document using the importJobAddDocuments mutation.

Sample document details mutation:

mutation SampleDocumentDetails{
  importJobAddDocuments(caseId: 5,
  input: {
    rdxJobId: 52080,
    documents: {
      documentId: “ACTEST_00000001”,
      fields: {
        name: “All Custodians”,
        action: Append,
        values: “Sample Custodian”
      }
    }
  }){
    documentCount
  }
}

Sample mutation results:

{
  “data”: {
    “importJobAddDocuments”: {
      “documentCount”: 1
    }
  }
}

Ingestions: Upgrade to Nuix Engine 9.0 and OpenJDK 11

Nuix Discover now supports Nuix Engine 9.0 and OpenJDK 11.

Supported upgrade paths

You can upgrade the following versions of Ringtail Legal, Ringtail, and Nuix Discover 10.5 to Nuix Discover 10.6:

• Ringtail 8.0.1, 8.1, 8.2, 8.3, 8.3.1, 8.3.2, 8.4, 8.4.2, 8.5, 8.6
• Ringtail Legal 1.0.58

For versions of Ringtail Legal earlier than 1.0.57, you must first upgrade to Ringtail Legal 1.0.58, and then upgrade to Nuix Discover 10.x.

Note: When upgrading to Ringtail 8.6 or later from an earlier version, you must request an updated license.

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

Support for Microsoft Internet Explorer 11 ending August 17, 2021

• On August 17, 2021, Microsoft will end support for Microsoft Internet Explorer (IE) 11 for O365.
• As of this date, Nuix Discover will no longer support Internet Explorer.
• This will, for example, affect Microsoft Office Online Server, which is used in the Office Online viewer in the View pane in Nuix Discover.
• Please plan to move to one of the following supported browsers before this date: Google Chrome or (Chromium-based) Microsoft Edge. Both of these browsers will continue to support the Office Online viewer feature.

Nuix Discover support lifecycle for Microsoft Windows Server and Microsoft SQL Server

The Nuix Discover support lifecycle for Microsoft products is communicated at the beginning of each year.

Note: For additional information about the Microsoft Lifecycle Policy, go to https://support.microsoft.com/en-us/lifecycle/search.

The general support policy for Microsoft Windows Server and Microsoft SQL Server for Nuix Discover quarterly on-premises releases is as follows:

• Nuix Discover will support at least two versions of Microsoft Windows Server and Microsoft SQL Server for each release.
• Within one year of a newly released version of Microsoft Windows Server or Microsoft SQL Server, those versions will be supported by Nuix Discover.
• Once Microsoft ends mainstream support for a version of Microsoft Windows Server or Microsoft SQL Server, those versions will no longer be supported by Nuix Discover.
• A 12-month notice of support retirement will be communicated with each quarterly on-premises release.

Note: For detailed information about client computer requirements, see the Nuix Discover 10.7 Client Computer Requirements guide. For detailed system and hardware requirements, see the Nuix Discover 10.7 Hardware and System Requirements guide.

Nuix Discover support lifecycle for biweekly and quarterly releases

Note the following support lifecycle for biweekly and quarterly releases.

• Biweekly releases
• Nuix supports the last four biweekly releases.
• Example: 10.7.005, 10.7.004, 10.7.003, 10.7.002
• Quarterly releases
• Nuix supports the last four quarterly releases to on-premises clients.
• Example: 10.7, 10.6, 10.5, 10.4

Note: Service packs for quarterly releases are offered for up to the latest four releases and for one year from the initial release date of the quarterly release.

Service parks for biweekly releases are offered for the four most recent biweekly releases.

For earlier releases that are no longer eligible for service packs, the Nuix Support Team will provide best-effort support.

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.

How to contact Nuix Support

If you need assistance, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support. If you do not have an account for the Nuix Support Portal, you can request one on the site.