Nuix Discover 10.9 Quarterly Release Notes

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.
    • New Search page showing Page Label field

      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.

Renumbering option on the Tools menu

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.

Search page showing context changes capability

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.

Search page indicating the background color change

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.

Search page indicating the Threading button

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.
  • Search page showing the orange warning icon

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.

      Chat documents window showing promoted chats

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.

Search Term Familes page showing the Term label column

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.

Search Term Families page showing the selection in the Term label column

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
  • Indexing Options page showing the Apply all rules option selected

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.

Field Map page indicating the case mapping

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
  • Indexing Options page showing the information message

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.

Content: File Type Rank page showing the banner message

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.

Hosted Details page showing the Non-billable column

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.

Hosted Details page showing the Non-billable clomun filters

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

Nuix Discover 10.8 Quarterly Release Notes

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.

Chat conversation

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.
  • Settings for Excel page

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.

Field Map page

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.
  2. Schedule page

    The window closes.

  3. 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.

Document ID page

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.
  4. Note: If you select the No change option, the non-billable status is not changed for any cases.

    Billable Status page
  5. In the list, select Billable or Non-billable.
  6. 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.

Cases page

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.

Errors page

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. Portal Options page
  3. 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.

Usage page

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.

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 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.

Nuix Discover 10.7 Quarterly Release Notes

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.

Browse pane showing Assignments section

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.
  3. 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.
  3. Note: Document is the default selection.

    New Search page showing Results within this entity 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.

    New Search page showing ID Type selection
  4. Under Source, do one of the following:
  5. 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.
    New Search page showing Source entry
  6. Click Next.
  7. The results appear on the Results page, as shown in the following figure.

    Results page showing search results

    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.

  8. 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
Import page showing existing Document ID

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.

Import page showing source attachment ID

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.

Import Field Map page showing Document Title list
  • 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.

Redactions page showing Font size
  • 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.

Renumbering Exclusions page

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”.

Renumbering Endorsement page

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.
  3. Cases page showing Bulk edit selection

    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.

  4. 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.

    Bulk edit IP Address Rule page
  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. 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.

    Bulk edit File transfer Respository page
  10. 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.

Properties page

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.

Nuix Discover 10.6 Quarterly Release Notes

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.

OCR: Updated OCR engine

Nuix Discover now uses ABBYY FineReader Engine for Optical Character Recognition (OCR) processing. This update affects the OCR processing option on the Tools menu on the Documents page, the Production Print feature, and the Exports feature.

The requirements and options available for OCRing image files in each of these areas have not changed. Only the OCR engine has changed.

The following differences are due to how ABBYY processes files:

  • ABBYY cannot access secured PDF files.
    • If a user submits a secured PDF for OCR using the Tools menu on the Documents page, an error appears. In this instance, the Document OCR Status field contains the word Error and the Document OCR Error Details field contains the following message: Exception: ERR_IMAGE_PDF_OPERATION_NOT_PERMITTED.
    • If a user produces a secured PDF as an image but no endorsements (redactions, headers, footers) appear on the image and the option to embed text in PDFs is selected, then a message appears on the Production > History page indicating that an error occurred during processing. Users can click a link on the page to access the rendition documents that generated the error. The Document OCR Status field for those rendition documents contains the word Error and the Document OCR Error Details field contains the following message: Exception: ERR_IMAGE_PDF_OPERATION_NOT_PERMITTED.
    • Note: If endorsements are applied to the image, ABBYY attempts to make the file searchable.

    • If a user exports a secured PDF file, ABBYY is unable to embed text in non-searchable pages within the file if the following conditions exist:
      • The option selected for image format is Convert to Searchable PDF or Embed Text in Existing PDFs, and
      • No endorsements are applied on the image.
    • If non-searchable pages are present in the PDF, a message appears on the Export > Warnings page indicating which documents contain searchable files that were not exported.
  • ABBYY recognizes text within files using languages selected by users. Users must select at least one language. While selecting all languages that may be present in the document set could provide more accurate results, we recommend that users select no more than 10. Selecting more languages increases processing time and may result in lower quality results.
  • If a user submits a document for OCR using the Tools menu on the Documents page and any page in the document fails in the process, the application does not create a .txt file. Additionally, if the option to embed text in a PDF is selected, the application does not return an updated PDF file. The same is also true if a user chooses to embed text in a PDF using the Production Print or Export features.
  • Note: In previous versions, the application was able to work around these issues using Nuance, but there are no workarounds with ABBYY at this time. However, we have found that ABBYY does not encounter errors on pages that Nuance was unable to successfully OCR. For example, Nuance failed to OCR any pages that were missing content. ABBYY does not encounter this failure.

Manage Documents > Exports > Update Image settings for exports

When converting images to PDF or from PDF to single-page TIFF, administrators now have the option to select the image size during export. When converting from PDF to single-page TIFF, administrators also have the ability to convert color PDFs to JPG files, as opposed to black and white TIFF files. You can access both options on the Image settings page in the Export window, as shown in the following figure.

Exports > Update Image Settings window
  • To access the new Paper size option, in the Image settings window, click the Settings icon. You can select either Letter or A4. The default selection is based on default settings for Automated Imaging, but can be changed for each export.
  • Note: Only files that are converted to another file type based on what you selected in the strong list will be affected by this setting.

  • To convert color PDFs to JPG files, in the Image format list, select Convert PDFs to TIFF, and then select Auto-detect color and render to JPG. The default selection for this option is based on the default settings for Automated Imaging, but can be changed for each export.
  • You can then enter the appropriate values in the Image resolution (DPI) and JPG quality (%) boxes. You can change the default values in these fields for each export.

Note: Footers, headers, redactions, and highlights are endorsed on the original image. If that image is converted at export (an image to PDF or a PDF to TIFF or JPG), the resulting files will have Letter or A4 dimensions. However, because the footers and headers were applied on the original image, they may not be positioned in the footer or header of the exported image file.

Manage Documents > Imaging: Support for Microsoft Publisher and Microsoft Project files

The Imaging feature now supports the .pub (Microsoft Publisher) and .mpp (Microsoft Project) file types. Once imaged, you can view these files in the View pane (in the Image viewer and in the Office Online viewer).

Note: Only files created using Microsoft Publisher 2000 or later are supported.

Manage Documents > Imports: Option to automatically ignore unmapped fields in imported flat files

When creating a new Imports job using a flat file, users can choose to ignore imported fields that they do not want to map or match to existing import fields. This functionality allows organizations to map only the fields they need and ignore the rest.

Import > Field Map page

To access this functionality, go to the Manage Documents > Imports page and click Add. In the Import window, on the Field Map page, the following message appears: Update all Action values of New to Ignore if no Case field is chosen. Click the strong button to ignore fields that have no value in the Case field column.

Import > Field Map page showing Ignore action

Manage Documents > Ingestions: NIST list updated - December 2020

The Ingestions feature now uses an updated version of this list, released in DECEMBER 2020. 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 > Ingestions: Cellebrite XML processing updates

Ingestions chat processing is now available for XML exports from Cellebrite Physical Analyzer, up to version 7.39. Exports to XML for later versions may be supported but have not been verified.

When a user exports from Physical Analyzer, additional files are commonly created and contain information that is duplicative of the information in the XML file. These additional files include files with names such as “chat-1.txt.” Additional files appear on the Manage Documents > Ingestions > [ingestion job] > Unprocessed Files page.

Note: If a user selects these files to reprocess, the application will return an error for the job in the Standardizing Data stage. We recommend that you do not attempt to reprocess these additional files.

Portal Management > Cases and Servers: Case creation date and time

The creation date and time for a case now appear in a new column on the Cases and Servers > Cases page, as shown in the following figure. This column is still available on the Cases and Servers > Deleted Cases page.

Cases and Servers > Cases page

Text extraction: Email headers skipped during text extraction

For the Predictive Coding and Production features, Nuix Discover is now configured (by default) to skip email headers for .msg files during text extraction.

Indexing: Email headers skipped during indexing

Nuix Discover is now configured (by default) to skip email headers for .msg files during indexing.

Note: To apply this change, you must reindex your case.

This change was available as of 10.6.004.

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.6 Client Computer Requirements guide. For detailed system and hardware requirements, see the Nuix Discover 10.6 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.6.004, 10.6.003, 10.6.002, 10.6.001
  • Quarterly releases
    • Nuix supports the last four quarterly releases to on-premises clients.
      • Example: 10.5, 10.4, 10.3, 10.2

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.

Nuix Discover 10.5 Quarterly Release Notes

Password requirement indicators on the login page

When you change your password in Nuix Discover, the application now displays password strength requirements (as configured by your administrator) and alerts you if passwords do not match. An example is shown in the following figure.

Password requirement indicators

Note: This new functionality applies to Ringtail authentication.

An administrator sets the password requirements on the Portal Management > User Administration > Account Settings page.

New search operator: not w\0

Nuix Discover now supports the not w\0 search operator.

For example, to find all documents that include Word01 or Word02 or Word03 but exclude documents that include Word04, you can run the following search:

Word?? not w\0 Word 04

The application finds all words in the index that meet the criteria for Word??, and excludes words after the not w\0 proximity operator (in this case, Word 04).

Translate documents into Russian

The Translate feature now supports Russian as a target language for both the Google and Microsoft translation services. Russian is also included as a choice for the Translation Languages system field. You can include Russian translations in productions.

Introducing the People Identity feature

The People Identity feature, also referred to as names normalization, is available on the Case Setup > People Identity page.

Note: A case administrator can make this feature available to group leaders but not to group members. For information about how administrators and group leaders can use this feature, see Case Setup: Introducing the People Identity feature. For information about how administrators can grant group leaders access to this feature, see Security > Administration: Enable the People Identity feature for group leaders.

This feature allows administrators and group leaders (with permissions) to link an individual person’s various “people names,” such as email addresses and user names, to an identity.

For example, if John Doe is associated with the following people names in Nuix Discover, an administrator can consolidate these email addresses and names into a single identity on the Case Setup > People Identity page.

  • john.j.doe@gmail.com
  • john.doe@gmail.com
  • jdoe@aol.com

Tip: Among other benefits, this feature is especially helpful when creating a privilege log because the normalized identity name can be used instead of the non-normalized people names.

After your administrator creates identities, you can work with the identities in the following ways.

  • Search page: Search for documents using identities on the Search page.
    • If an administrator has created identities, you can search for documents based on their connection to those identities using the following fields on the Search page:
      • Identity
      • Identity - BCC
      • Identity - CC
      • Identity - From
      • Identity - To
  • List pane: Add identity fields to the List pane column templates.
    • You can add the following identity columns to the List pane when documents are in the search results:
      • Identity
      • Identity - BCC
      • Identity - CC
      • Identity - From
      • Identity - To
      • Tip: Adding these columns and using the Download feature in the List pane allows you to quickly generate a privilege log or other report showing the normalized names associated with documents.

  • Communication Network pane: Use identities to view normalized names in the Communication Network pane.
    • In the Communication Network pane, in addition to viewing communications for non-normalized person names, you can now also view information based on the normalized Identity names. To view the communications for an Identity, for example, for William S. Bradford, on the toolbar in the Communication Network pane, select Identity from the list, as shown in the following figure.
    • Communication Network pane showing identity selection

Note: To use identities on the Search page and in the List pane, the user’s group must have permissions set to Allow for People\Organizations on the Security > Objects > Document Fields page. To access the Communication Network pane, the user’s group must have permissions set to Allow for the Communication network feature on the Security > Features page.

Tools menu: UI extensions - Custom tools

Your portal or system administrator can now add custom tools, for example, a calculator, to the Tools menu using the user interface extensions (UI extensions) feature.

Use the following procedure to access these custom tools.

  1. On the Documents page, on the Tools menu, in the navigation pane, click the UI extensions button, as shown in the following figure.
  2. Documents page Tools menu
  3. Select a UI extension tool.
  4. The tool appears in a standalone window. You can minimize, maximize, resize, and close the window. You can also reposition the window within your application browser window.

    Note: You must close the window before you can open a different UI extension tool.

Case Setup > Issues: Issue administration enhancements

The Issue administration feature has been enhanced in this release and includes the following updates:

Note: Administrators can grant group leaders access to issue management on the Security > Administration page by setting the Case Setup - Issues - Properties and Case Setup - Issues - Security functions to Allow.

Add a root issue with child issues at the same time

Use the following procedure to add a root issue and child issues at the same time.

Note: Previously, this was a two-step process.

  1. On the Case Setup > Issues page, on the toolbar, click Add.
  2. In the Add issues dialog box, shown in the following figure, provide a Name for the root issue.
  3. Add issues dialog box providing a Name
  4. In the Child issue name(s) box, provide the names of the child issue or issues.
  5. Note: Create a new line for each issue.

  6. Click Save.
  7. The root issue appears on the Issues page, as shown in the following figure. In the Name column, click the name of the root issue.
  8. Issues page showing root issue
  9. The Child Issues page appears. To add additional issues to the child issues that you created, click the Add issue button, as shown in the following figure.
  10. Child Issues page showing Add issue button

Clone a root issue and include child issues

You can now clone an existing root issue, including all of its child issues.

Note: When you clone an issue, the application clones only the issue structure, but not the document membership, that is, documents that were coded to the issues that you cloned.

Use the following procedure to clone an existing root issue.

  1. On the Case Setup > Issues page, hover over the row for an issue, and then click the Clone Issue button, as shown in the following figure.
  2. Case Setup > Issues page showing Clone Issues button
  3. In the Clone Issue dialog box, as shown in the following figure, you can edit the name of the cloned issue.
  4. Clone Issue dialog box
  5. Click OK.
  6. The cloned issue appears on the Issues page.

Import issues

You can now import issues using a .csv file.

Use the following procedure to import issues.

  1. On the Case Setup > Issues page, on the toolbar, click Import issues.
  2. In the Import issues dialog box, as shown in the following figure, do one of the following:
  3. Import issues dialog box
    • If you have a .csv file with issues, click Browse to upload your .csv file.
    • If you do not have a prepared .csv file, click the Download template link to download and populate a .csv file, and then click Browse to upload the file.
    • Note: In the .csv file, the root and child issues must be separated by a comma.

      The following figure, created in a text editor, provides an example of the format for the .csv file.

      Example format for .csv file in file manager

      The following figure provides an example of the format for the .csv file when opened in a Microsoft Excel document. The root issue name is in column A, the child issue names are is in column B, and the subissue names are in column C.

      Example format of .csv file in Excel
  4. After you upload your .csv file, click OK.
  5. Note: If the application encountered errors when importing the .csv file, a notification appears, with a link to the errors. Fix the errors, and upload the .csv file again.

Export issues

You can now export issues in a .csv file format.

Use the following procedure to export issues.

  1. On the Case Setup > Issues page, select the check box next to an issue.
  2. On the toolbar, click Export issues.
  3. In the Export issues dialog box, click OK.
  4. The application downloads the .csv file to your computer.

    If you open the .csv file in Microsoft Excel, the information in the .csv file will look similar to what is shown in the following figure.

    Example of .csv file in Excel

    If you open the .csv file in a text editor, the information in the .csv file will look similar to what is shown in the following figure.

    Example of .csv file in text editor

Move child issues to a different root issue

You can now move child issues from one root issue to another root issue. You cannot currently move child issues within the same root issue.

Note: When you move issues, the application maintains the document membership, that is, documents that are coded to issues.

Use the following procedure to move child issues.

  1. On the Case Setup > Issues page, click the link for a root issue.
  2. On the Child Issues page, select the check boxes next to one or more issues. To select all child issues, select the top check box.
  3. On the toolbar, click Move, as shown in the following figure.
  4. Child Issues page showing Move button
  5. In the Move Issues dialog box, shown in the following figure, under Root issues, click the link for a root issue.
  6. Move Issues dialog box
  7. Click OK.
  8. The application moves the selected child issue or issues from the current root issue to the destination root issue.

    Note: If a child issue with the same name already exists in the destination root issue, the application notifies you and the issue is not moved. Change the name of the child issue and repeat the previous steps.

Case Setup: Introducing the People Identity feature

The People Identity feature, also referred to as names normalization, is available on the Case Setup > People Identity page.

Note: Case administrators have access to this feature by default. To grant group leaders to access to this feature, you must enable it on the Case Setup > Administration page. For more information, see the Security > Administration: Enable the People Identity feature for group leaders section.

This feature allows administrators and group leaders (with permissions) to link an individual person’s various people names, such as email addresses and user names, to an identity.

For example, if John Doe is associated with the following people names in Nuix Discover, an administrator (or group member with access to this feature) can consolidate these email addresses and names into a single identity.

  • john.j.doe@gmail.com
  • john.doe@gmail.com
  • jdoe@aol.com

Tip: Among other benefits, this feature is especially helpful when creating a privilege log, because the normalized identity name can be used instead of the non-normalized people names.

Using the People Identity feature, you can:

  • Run a Normalize job to create identities and link non-normalized people names
  • Note: You can use the Normalize feature on the Case Setup > People Identity page on new, non-normalized people names in a case.

  • Assign (or reassign) people to an identity
  • Note: You can use the Assign identity feature to change the connections between people and identities.

  • Edit the identity name and description
  • Delete identities
  • View the identities and people for a specific document set
  • Download an identity report

Normalize people names

Use the following procedure to normalize names.

  1. Go to the Case Setup > People Identity page.
  2. If there are non-normalized names, a banner appears at the top of the page telling you that new people have been added and to click Normalize to normalize the people names to an identity.

    The following figure shows the names before they are normalized.

  3. Do one of the following:
    • To normalize the non-normalized people names, proceed to step 3.
    • (Optional) In the banner, to view the names of the people who have not yet been normalized, click View non-normalized names.
    • The application displays the non-normalized names. You can then select which names to normalize.

      People Identity page
  4. On the toolbar, click the Normalize button.
  5. In the Normalize dialog box, the following message appears, as shown in the following figure: The normalize job will link non-normalized people to an identity. People that are already linked to an identity will not be affected. To confirm, click OK.
  6. Normalize dialog box

    Note: The job operates only on non-normalized people names. People that were linked to an identity before running the job are not affected.

    The application runs a Normalization RPF job to analyze the people name data and logically group the people under a unique identity. The banner at the top of the People Identity page lets you know that the normalization job is running and displays the following message, as shown in the following figure: Normalization job is running. Refresh the page to see updated results.

    People Identity page showing normalization jobs
  7. Refresh the page to see the updated results. When the application has finished normalizing, the banner at the top of the page lets you know that the normalization job is complete and that all people are linked to an identity, as shown in the following figure.
  8. Note: In the tree view in the Name column, the identities are the parent rows (shown in bold font) and the people names are the child rows (in non-bold font).

    People Identity page showing Name column

Working with the table on the People Identity page, you can do the following:

  • In the Document set list, you can return results for all documents in the case or for a subset of documents, for example, a binder or a population. For more information, see View the identities and people for a document set.
  • Filter by the Name column to return specific people and their linked identities.
  • Note: When filtering by the Name column, the text you enter will match on people names (in child rows), and the filtered results will include the identities (parent rows) for those people that match your filter as well as all other people that are linked to those identities.

  • Sort the columns in ascending or descending order.
  • Note: No matter how you sort the columns, if there are non-normalized people names, they will always appear under the Non-normalized section at the bottom of the last page.

  • Click the plus and minus sign to collapse and expand the people names beneath each identity.
  • In the Occurrences in documents table, shown in the following figure, you can click a number link in the Total, From, To, CC, or BCC columns to view the documents that are associated with a person or identity. For more information, see View the identities and people for a document set.
  • Note: The counts in the Total column and identity rows reflect the number of occurrences that the identity or person name appears in documents. The counts do not represent the actual number of documents. For example, if Jane Smith sends an email and copies (CCs) herself, her name will appear in the same document two times (From and CC), so the Total column will show a count of 2 but the link will only return one document on the Documents page.

    Documents page showing Total column counts
  • To add a description for an identity, in the Description column, click in the row for an identity, provide a description in the description window, and then click outside of the window. You can also edit the identity description. For more information, see Edit the identity name and description.

Assign an identity

The Assign identity feature allows you to change the identity that is assigned to people. You can reassign people to an existing identity or create a new one.

Use the following procedure to assign an identity.

  1. Select the check box next to a person, and then click Assign identity.
  2. Note: To assign an identity to multiple people at one time, select more than one person, and then click Assign identity.

    The Assign identity dialog box appears, as shown in the following figure.

  3. Under Assign identity, select one of the following options:
    • Select an existing identity: Select an existing identity from the list.
    • Add new identity name: Select this option and enter a name in the box.
    • Assign identity dialog box showing Name selection
  4. (Optional) When you assign people to a new identity, you can delete the source identity after you make the assignment, if there are no remaining people linked to that identity. If the source identity has fields coded, the coding will also be deleted. To delete the source identity after you make the assignment, select the following check box, which is cleared by default: Delete source identity after assignment if there are no remaining people linked. (If the source identity had fields coded, the coding will also be deleted.)
  5. Click OK.
  6. The person (or people) are then listed under the identity.

Edit the identity name and description

You can edit the identity name or the identity description.

Note: The system Data Model now includes a new entity named Identity, shown in the following figure. The Identity entity was created to support the Names Normalization feature. The Identity entity has a one-to-many connection to the Person entity.

Entities page showing modification capabilities

To make the Identity name and Identity description editable for a user on the Case Setup > People Identity page, an administrator must grant Write access to these fields for the user’s group.

Use the following procedure to make the identity name or identity description fields editable.

  1. Go to the Case Setup > Data Models > System > Entities > Identity > Fields page.
  2. On the Fields page, click the link for the Identity Description or strong, as shown in the following figure.
  3. Field page showing how to modify
  4. In the navigation pane, click Security.
  5. Set the security to Write for a user group, as shown in the following figure.
  6. Security page showing the Write selection

Tip: On the Case Setup > Data Models > System > Entities > Identity > Fields page, click the Add button to add new fields to use for coding identities. Set the appropriate group permissions for your new fields on the field’s Security page. You can use your new fields in Column Templates or Conditional Templates for the Identity entity. You must enable the Conditional Template.

Use the following procedure to edit the identity name or the identity description.

  1. Click on the name or description for an identity. For the name, an editable field appears, as shown in the following figure.
  2. Fields page showing editable fields
  3. Type the new identity name or description.
  4. To save your changes, click outside the field.

Delete identities

You can only delete an identity that does not have any people assigned to it.

Use the following procedure to delete an identity.

  1. Hover over the row of the identity you want to delete and click the Delete identity button, as shown in the following figure.
  2. Delete identity

    The Delete identity dialog box appears.

  3. The information that appears in this dialog box depends on whether an identity has user-created fields with coded values.
    • When you delete an identity that has no people assigned to it, you are asked to confirm the deletion of the identity in the Delete identity dialog box, as shown in the following figure. If you are sure you want to delete the identity, click OK.
    • Delete identity dialog box

      Note: You cannot delete an identity that has people assigned to it or delete the individual people.

    • If you try to delete an identity that has user-created fields with coded values, the Delete identity dialog box displays a warning and lists the fields that are coded, as shown in the following figure. To delete the identity, click OK.
    • Delete identity dialog box showing message for codes values

View the identities and people for a document set

Select a Document set to view the identities and people that are associated with those documents.

Use the following procedure to view the identities and people for a specific document set.

  1. In the Document set list, select the type of document set you want to use, and then select the document set in the field that appears to the right.
  2. The page will refresh when the document set is changed, and the application will filter the displayed identities to only those that have people connected to documents in the selected set.

Note: All people appear for identities that have at least one person connected to documents in the selected set, even if some people in those identities are connected to 0 documents. The counts in the columns reflect the number of occurrences within the selected set. Your selected document set will be selected by default the next time you return to the People Identity page.

The Normalize job always operates on all documents in the case, regardless of which document set is selected on the page.

Download an identity report

You can download an identity report to a .csv file.

Use the following procedure to download an identity report.

  1. Click the Download report button. Nuix Discover saves the identity information to a .csv file in your Downloads folder.
  2. Note: The Download report feature respects the document set that is selected. The report file name has a time stamp with the local time so that each time you download a new report with a new time stamp, the report is saved and does not overwrite a previous report.

  3. To view the report, open the .csv file in Microsoft Excel.

Security > Administration: Enable the People Identity feature for group leaders

If you want group leaders to use the People Identity feature, which is also referred to as the Names Normalization feature, you must enable it for them.

Use the following procedure to enable the People Identity feature for group leaders.

  1. Go to the Security > Administration page.
  2. In the Leaders column, click the Allow button next to Case Setup - People Identity, as shown in the following figure.
  3. Administration page showing Leaders column
  4. Click Save.

Manage Documents > Imaging: Support for .ics and .xps file types

The Imaging feature now supports the .ics and .xps file types.

  • An .ics file is a calendar file saved in a universal calendar format that is used by several email and calendar programs, including Microsoft Outlook.
  • An .xps file is a document that contains fixed page layout information written in the XPS page description language. This file type defines the layout, appearance, and printing information for a document. XPS files are similar to PDF files, but are saved in Microsoft’s proprietary XPS format.

Once imaged, you can view these files in the View pane (in the Image viewer and in the Office Online viewer).

Manage Documents > Imports: New default delimiter on the Field Map page

When creating a new Imports job using a flat file, on the Field Map page, the default Delimiter value is now “; (59)” when one of the following is selected in the Case field column:

  • People - To
  • People - CC
  • People - BCC

Manage Documents > Ingestions: Group multi-segment AD1 files

When running an ingestions job, multi-segment AD1 files are now grouped in the same processing task.

An AD1 file is a Forensic Toolkit FTK imager Image file.

Manage Documents > Ingestions: NIST list updated - September 2020

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

Case Options: New case option to set the maximum unique word count for an index for content searching

On the Portal Management > Cases and Servers > [Case] > Case Options page, shown in the following figure, you can now use the following option to set the maximum unique word count that can be retrieved from an index for content searching: Search max unique word count.

Case Options page showing maximum unique word count
  • The default value is 256,000.
  • The minimum value is 16.
  • The maximum value is 4,096,000.

Case Options: New case option when translating with a Microsoft custom translation model

Portal administrators can now configure a custom translation model to be used for Microsoft translations for a specific case and for a specific language pair.

Note: You must work with Nuix to configure this feature in your SaaS environment. To request access to this feature, submit a ticket on the Nuix Support Portal, located at https://nuix.service-now.com/support.

A custom translation model allows you to create a customized dictionary of domain-specific source language and target language terms for a specific language pair. Microsoft refers to this feature as the Microsoft Custom Translator. Custom models will need to be created in Microsoft’s Custom Translator portal in Azure.

To use a custom translation model for a case, in the Translate with Microsoft custom model box on the Portal Management > Case and Servers > [Case] > Case Options page, shown in the following figure, enter the Category ID, which is the unique identifier for the custom model.

Case Options page showing how to use a custom translation model

Custom UI extensions for the Tools menu

The user interface extensions (UI extensions) feature allows application administrators and service providers to extend the functionality of the application by embedding custom third-party applications directly into the application interface. A third-party application that loads within the application is called a UI extension.

In addition to adding a UI extension to the Portal Home page, the Case Home page, or as a workspace pane on the Documents page, system administrators and portal administrators can now add a custom UI extension to the Tools menu on the Documents page using the Workspace tools UI extension.

Note: System administrators can add UI extensions in a portal for any organization or user, and portal administrators can install extensions for the organizations and users that they manage.

Sample UI extension applications:

  • An administrator might add a UI extension to the Tools menu to allow users easy access to external websites, for example, to an online calculator, as described in this document.
  • Note: Administrators are blocked from adding some websites, for example, CNN, as UI extensions.

  • Administrators could also configure a UI extension on the Tools menu to submit a selection of documents in the List pane for reporting, processing, or another task.
  • Another possible application could be a custom tool that combines multiple steps into one process. For example, you could build a custom tool that would allow you to take Predictive Coding score ranges and tag them with different review priority levels. Users could then search for documents by the review priority and tag those documents with the correct priority level.

For detailed information about UI extensions, see the following topics in the Nuix Discover online help.

  • UI Extension SDK: The UI Extension SDK provides an API that UI extensions can use to communicate with the application. The UI Extension SDK also includes steps to build and configure an extension, reference documentation, and an example extension. For access to the UI Extension SDK, contact Discover.Sales@Nuix.com.
  • Administer UI extensions: This topic describes how to add a UI extension to the Case Home page, the Portal Home page, and as a workspace pane on the Documents page.

The workflow to add a UI extension to the Tools menu on the Documents page consists of the following main steps, described in more detail in the following sections:

  1. Manually add a UI extension to the Tools menu
  2. Enable a UI extension for an organization and cases
  3. Set group security for a UI extension
  4. Test the UI extension on the Tools menu

Manually add a UI extension to the Tools menu

Use the following procedure to manually add a UI extension to the Tools menu.

Note: For information about how to install a UI extension using a manifest file, see the Install a UI extension using a manifest file in the Nuix Discover online help.

  1. On the Portal Home page, under Portal Management, click UI Extensions.
  2. On the UI Extensions page, on the toolbar, click Add.
  3. The Add UI extension window appears, as shown in the following figure.

    Add UI extensions > Settings page top half
  4. On the Settings page, in the Settings editor area, leave the Basic option selected.
  5. Note: If you are using a manifest file, select Advanced. The advanced procedure is not described in this document. For more information about how to add a UI extension using a manifest file, see Administer UI extensions in the Nuix Discover online help.

  6. Type a Name for the UI extension.
  7. In the Location list, select Workspace tools.
  8. Under Default window size, you can set the following:
    • Width: The minimum value for the width is 200 pixels and the maximum value is 1280 pixels.
    • Height: The minimum value for the height is 150 pixels and the maximum value is 768 pixels.
    • Require document selection: If the tool involves working with documents, select this option to require document selection before using the tool.
    • Display the OK and Cancel buttons: This check box is selected by default. Clear the check box if you do not need to include OK and Cancel buttons in the window, for example, when adding a calculator tool.
  9. Type an optional Description of the extension. The description appears on the UI Extensions page.
  10. Scroll down to display additional settings, as shown in the following figure.
  11. Add UI extensions > Settings page bottom half
  12. In the URL box, enter the URL of the web application that you are adding as an extension. The URL must include http or https.
  13. Note: Administrators are blocked from adding some websites, for example, CNN, as UI extensions.

  14. In the Authentication secret box, click the Generate a random authentication secret button.
  15. Click Next.
  16. On the Review page, review the settings for the extension, and then click Save.

Enable a UI extension for an organization and cases

System administrators can enable UI extensions for the organizations in a portal.

Note: For portal administrators, when organization security is enabled, the list of available items depends on membership in a provider or client organization.

Use the following procedure to enable a UI extension for organizations.

  1. To access the UI extensions that are installed in the application, on the Portal Home page, under Portal Management, click UI Extensions.
  2. The UI Extensions page appears.

  3. On the UI Extensions page, shown in the following figure, click the name of an extension.
  4. UI Extensions page
  5. In the navigation pane, click Organizations.
  6. Depending on which organizations you want to enable the extension for, do the following:
    • To enable the extension for a single organization, hover over the row for the organization, and then click Allow.
    • To enable the extension for all organizations, click the Allow button in the heading row.
  7. After a UI extension is enabled for an organization, system administrators and portal administrators can enable the extension for the cases that are assigned to the organization. In the navigation pane, click Cases.
  8. Depending on which cases you want to enable the extension for, do the following:
    • To enable the extension for a single case, hover over the row for the case, and then click Allow.
    • To enable the extension for all cases, click the Allow button in the heading row.

Set group security for a UI extension

To allow groups in a case to access a UI extension on the Tools menu, administrators must grant access to the following security option on the Security > Features page in the case: UI Extension – [UI Extension Name] (for example, UI Extension – Calculator).

Test the UI extension on the Tools menu

Use the following procedure to test the UI extension.

Note: Administrators are blocked from adding some websites, for example, CNN, as UI extensions.

  1. Log in to a case.
  2. On the Documents page, on the Tools menu, in the navigation pane, click the UI extensions button, as shown in the following figure.
  3. Tools menu showing the UI extensions button
  4. Select a UI extensions tool.
  5. Ensure that the tool appears as expected in the standalone window.

New portal option to address potential performance issues when streaming media files

Web servers become highly consumed by the FFmpeg process running at 100% when streaming media files, which causes performance issues in the environment. To address this issue, a new setting named View pane media thread count is now available on the Portal Management > Settings > Portal Options page to allow system administrators to limit the number of allowed threads.

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.5 Client Computer Requirements guide. For detailed system and hardware requirements, see the Nuix Discover 10.5 Hardware and System Requirements guide.

Nuix Discover 10.4 Quarterly Release Notes

Browse: Introducing the Hierarchies feature

This release includes a new feature that allows you to view Hierarchies in the Browse pane, for example, to view the folder hierarchy of a file path for a custodian.

An example is shown in the following figure.

Note: Your administrator must configure and grant you access to hierarchies.

Hierarchies example under Browse pane

Tip: You can also search for a Hierarchy on the Search page.

Conditional Coding: Add a binder

In the Conditional Coding pane, group leaders with permissions to work with binders can now add a binder and apply security to that binder.

Use the following procedure to add a shared binder.

  1. In the Conditional Coding pane, in the list on the toolbar, select the Binders template.
  2. On the toolbar, click the Add binder button, as shown in the following figure.
  3. Add binder button
  4. In the Add binders window, shown in the following figure, on the Properties page, provide a name and an optional description.
  5. Add binder Properties page
  6. Under Type, leave the Shared binder type option selected.
  7. Optionally, under Use as, set the binder to be used as a Security override or Mobile binder.
  8. Click Next.
  9. On the Security page, set the user group security for the shared binder.
  10. Click Save.
  11. The binder appears in the Conditional Coding pane.

Use the following procedure to add a private binder.

  1. In the Conditional Coding pane, in the list on the toolbar, select Binders.
  2. On the toolbar, click the Add binder button.
  3. In the Add binder dialog box, on the Properties page, provide a name and an optional description.
  4. Under Type, select Private.
  5. The Owner list appears, as shown in the following figure.

    Add binders Properties page Owners list
  6. In the Owner list, select an owner.
  7. Click Save.
  8. The binder appears as a private binder in the Conditional Coding pane.

Note: If you are a group leader with permissions and need to delete a binder, you can do that on the Case Setup > Binders page, but not in the Conditional Coding pane.

List: Download a report to an .xlsx format and add a report title

In the List pane, you can now download a report to an .xslx format and give the report a title, as shown in the following figure. Previously, you could download the report only to a .csv format.

Download dialog box

Enhancements to Workspace panes

This release includes the following enhancements to all workspace panes, as shown in the following figure:

List pane enhancements

Change a pane

To change a pane, on the pane menu, select a different pane from the list, as shown in the following figure.

Note: Changing a pane changes your current workspace configuration.

Change pane selection

If you select a pane that is already included in your current workspace configuration, the current pane is exchanged with the pane you selected.

For example, if your workspace configuration includes a Browse pane, a List pane, and a Conditional Coding pane, if you change the List pane to a Conditional Coding pane, the List pane appears where the Conditional Coding pane used to be, as shown in the following figures.

Before

Change pane selection before

After

Change pane selection after

Maximize a pane

All workspace panes now include a new option to maximize the pane, as shown in the following figure.

Maximize panes option

When you select the Maximize option, the application maximizes the pane and hides all of the other panes in the workspace configuration.

To restore the hidden panes, click the Restore all hidden panes button on the toolbar of the pane, as shown in the following figure.

Restore all hidden panes button

Close a pane

All workspace panes now include a new option to close the pane, as shown in the following figure.

Note: Closing a pane changes your current workspace configuration.

Close pane option

When you select the Close option, the application removes the pane from the current workspace as well as from the pre-set workspace configurations.

To add the pane that you closed back to a workspace, on the workspaces menu, shown in the following figure, edit the workspace.

Add pane back into workspace

Tools: Introducing the redesigned Tools menu

This release includes a redesigned Tools menu that provides an enhanced user experience when working with various tools. The menu was redesigned based on user feedback. The tools are organized into logical groupings. The names of the tools have not changed.

All tools: Allows you to access the entire list of tools, as shown in the following figure. The tools in each section mirror the logical groupings.

All tools

Frequently used tools

Frequently used tools such as Report and Batch Print are now at the top of the menu, as shown in the following figure.

Frequently used tools

Find tools quickly

The search box at the top of the menu, shown in the following figure, allows you to find tools without having to scroll through the list.

Find tools

Logical groupings

The tools are organized into the following logical groups that you can access by clicking the buttons in the navigation pane on the menu:

  • Output
  • General
  • Results
  • Processing

Output: The tools in this grouping include Report, Batch print, Export, and Archive files, as shown in the following figure.

Logical groupings > Output

General: The tools in this grouping include History, Load search file, Workflow, Quick code, Add document, Coding history report, Document count, and Theme, as shown in the following figure.

Logical groupings > General

Results: The tools in this grouping include Base docs\Renditions, Find masters family, Find family duplicates, Find individual duplicates, Remove family duplicates, and Remove individual duplicates, as shown in the following figure.

Logical groupings > Results

Processing: The tools in this grouping include Imaging, Reverse previous imaging, OCR processing, Extract text, Transcribe audio, Indexing and enrichment, Thread analysis, Convert page annotations, and Translate, as shown in the following figure.

Logical groupings > Processing

Tools > Imaging: Auto-detect color and render to JPG

When submitting documents for imaging, you can now select an option to automatically detect color and render to JPG. The Auto-detect color and render to JPG check box is located in the Imaging window on the Properties page, as shown in the following figure.

Note: This option is available only if the TIFF option is selected from the Image type list.

The default value for the option is based on the Imaging settings found in Manage Documents > Imaging - Automated > Settings.

Imaging > Properties page Automated > Settings

Tools > Imaging: Image viewer support for Adobe Photoshop file formats (.psd and .psb)

In the Imaging window, you can now submit .psd and .psb files, which are Adobe Photoshop file formats, for imaging to a TIFF, JPEG, or PDF format, as shown in the following figure.

Once the files are imaged, you can view the imaged files in the Image viewer in the View pane.

Imaging > Properties page Viewing images

Tools: Access to Transcribe audio and Translate options

Users can now use the Transcribe audio and Translate options on the Tools menu, even if they do not have access to private binders.

Tools > Coding History: Coding history report on the Tools menu

The Tools menu on the Documents page now includes a Coding history report option that allows you to download a .csv report with the history for a field for all documents selected in the List pane.

Note: To see this option, your administrator must grant you access to the Coding - Coding History feature on the Security > Features page, and audit history must be configured for the case.

Use the following procedure to generate a coding history report.

  1. In the List pane, select one or more documents.
  2. On the Tools menu, select the Coding history report option.
  3. In the Download coding history report dialog box, shown in the following figure, from the Field list, select a field, and then click OK.
  4. Note: The available fields depend on the permissions granted by your administrator.

    Download coding history report dialog box

    A processing window appears, as shown in the following figure.

    Note: Do not close this window or exit the case until the report downloads.

    Download Processing dialog box
  5. After the .csv report downloads, open or save the file.

Coding History > Search: New operator to search for previously coded values

A new operator named previous value ever was is now available for advanced searches on the Search page, as shown in the following figure.

Search page showing example search

Note: The previous value ever was operator is available to users who are in a group with permissions to access the Coding History pane. And audit history must be configured for the case.

The following field types support coding history searches using the previous value ever was operator:

Note: Memo field types are not supported.

  • Pick list
  • Date
  • Number
  • Yes\no
  • Text
  • Binder - Shared
  • Issue
  • Production
  • Population
  • Sample
  • Highlight
  • Redaction
  • People - correspondence type
  • Organizations - correspondence type

When using this operator, you can search for previously coded values, which are the values captured by the Coding History feature and found in the Previous value column in the Coding History pane, as shown in the following figure.

Previous value column in Coding History pane

Use the following procedure to search for previously coded values.

  1. Navigate to the Search page.
  2. In the Select a field box, select the field for your search criteria.
  3. In the Select an operator box, select previous value ever was.
  4. In the Select a value box, select or enter the value.
  5. Note: Not all values for your selected field may be available in the Select a value list. Values are not available for previous value ever was searches until they have been stored in coding history (for at least one audit record).
     
    When searching for a text field value using the previous value ever was operator, the text field value must be an exact match.

  6. Optionally, to include Coded by or coded on date parameters in your search criteria, click the Add additional criteria button.
  7. Note: Coded by and coded on date parameters will be evaluated against the user and date corresponding to the original coding action for the value.

  8. To run the search, click the Search button.

Analysis > Search Terms: Term query column added

The Analysis > Search Terms page now includes a new column named Term query, as shown in the following figure. This column contains the term query value or values for a Search Term Family.

You can use the information in the Term query column to effectively determine how to modify the search to increase or decrease the number of hits.

Analysis > Search Terms page

Analysis > Predictive Coding > Add custom Predictive Coding Templates

The Predictive Coding Templates page has been added to the Analysis capabilities in Nuix Discover and is available to all administrators. This page allows administrators to select the Standard or Standard + people template when setting up predictive coding or Continuous Active Learning (CAL) models, or to create their own templates.

Note: The Standard and Standard + people templates are available to all cases and cannot be modified.

Create a new Predictive Coding Template

To create a new template, go to the Case Home > Analysis > Predictive Coding Templates page and click Add. Add a name and description for the template, and then click Save. The Fields page opens for that template. To add fields to the template, select a field in the Add field list and click the + (plus sign) button, shown in the following figure.

Analysis > Predictive Coding > Fields page Add fields

The following information applies to fields in a predictive coding template.

  • The values of date fields included in a template appear as text strings.
  • The weight for each field is 1 by default, but you can change the value to anything between 1 and 10. Weight reflects the amount of influence a field has on the model in relation to other fields in the template. For example, if you want People information to be more heavily considered in the model than other fields, adjust the weight value on the People fields to be higher than the other field weight values.
  • Analysis > Predicitive Coding > Fields page People information

The following information applies to all custom predictive coding templates.

  • Extracted text from documents is included in every template, although it is not listed as an item in the template. The training field for the model that the template is selected for is also included.
  • Once a template is being used by a CAL or predictive coding model, it cannot be edited. Open the template’s Properties page to view the names of the models that are using the template.
  • Analysis > Predictive Coding > Properties page

Clone a Predictive Coding Template

All custom templates can be cloned, regardless of whether they are in use. To clone a template, open the Fields page for the template and click Clone template. Update the template name as needed and click Save. The Fields page for the new template opens. Add fields, delete fields, or change any of the field weights on that page.

Delete a Predictive Coding Template

You can delete any custom predictive coding template that is not in use by a predictive coding or CAL model. To delete a template, open the Fields page for the template and click Delete template.

Use Predictive Coding Templates with CAL

Administrators now have the option to select a predictive coding template when configuring training for a model. To select a template, go to the Case Home > Analysis > Populations and Samples page and select a population. Then, open the Predictive Coding page for the population and click Configure training. On the Settings page, select a template in the Predictive coding template list.

Predictive Coding > Settings page

Note: You can change the predictive model template throughout the lifecycle of the training model. However, at the present time, the application only provides data about the current template selected for training and does not record the history of different templates that have been selected.

Use Predictive Coding Templates with the Predictive Coding standard workflow

To select a predictive coding template to use when adding a predictive model, go to the Case Home > Analysis > Predictive Models page and click Add. In the Add Predictive Model dialog box, select a predictive coding template in the Predictive coding template list.

Predictive Models > Add Predictive Models page

Select how date data is treated for Predictive Coding templates

We have added an option to Predictive Coding Templates that allows administrators to select how date type field data should be treated in the model.

To access the option, go to Analysis > Predictive Coding Templates and select a template. On the Fields page, click in the Date Value column, and then select a value for how date information should be treated in the template.

Predictive Coding Templates > Fields page

The options are as follows:

  • Text: Date information is treated as a text string.
  • Day, month, and year: Date information is modeled without time. This option is the default.
  • Month: Date information is treated as a number with January = 1, February = 2, and so on.
  • Day: Date information is treated as a number.
  • Day of the week: Date information is treated as a number with Sunday = 1, Monday = 2, and so on.
  • Year: Date information is treated as a number.

Note: The application treats any date fields selected in templates created before this change as Text. If the template is used in any models, the date value cannot be changed. The choice of which Date Value option to use depends on the case data and what aspect of the date information has an impact on the model. For example, documents with dates clustered around the middle of January 2005 may be meaningful. Select the Day, month, and year value to model date information in that way. In a different example, which day of the week a date falls on (Monday, Tuesday, and so on) has some relevance. Use the Day of the week value to model date information in that way.

Case Setup: Introducing the Hierarchies feature

This release includes a new feature on the Case Setup > Hierarchies page that you can use to set up hierarchies, for example, to browse the folder hierarchy of a file path for a custodian.

Once you have set up hierarchies and granted access to user groups, users can view the hierarchies in the Browse pane.

Note: Administrators can grant group leaders access to this feature by setting the Case Setup - Hierarchies to Allow for Leaders on the Security > Administration page.

Use the following procedure to add a hierarchy.

  1. On the Case Setup > Hierarchies page, on the toolbar, click Add.
  2. In the Add hierarchy window, shown in the following figure, on the Properties page, do the following:
    • Provide a Name.
    • Select a Field, for example, All File Paths.
    • Select a Delimiter.
    • Click Next.
    Add hierarchy > Properties page
  3. On the Security page, shown in the following figure, set the security for groups, and then click Save.
  4. Add hierarchy > Security page

    The hierarchy appears on the Hierarchies page, as shown in the following figure.

After you create a hierarchy, you must run an indexing and enrichment job to populate and update the hierarchy.

Note: As documents are added to the case and submitted or resubmitted for indexing and enrichment, the hierarchies are updated as part of those jobs.

Use the following procedure to run an indexing and enrichment job for a hierarchy.

  1. On the Case Setup > Hierarchies page, select the check box next to a hierarchy, as shown in the following figure.
  2. On the toolbar, click Run.
  3. Case Setup > Hierarchies page

Use the following procedure to delete a hierarchy.

  1. On the Case Setup > Hierarchies page, select the check box next to a hierarchy, as shown in the previous figure.
  2. On the toolbar, click Delete.

Case Setup > Binders: New workflow to add a binder

On the Case Setup > Binders page, the workflow to add a binder has been streamlined. When you add a binder, you can now set the properties and the security in a wizard-like fashion. Previously, you had to add a new binder, and then access the new binder to set the security.

Note: If you need to edit an existing binder or a newly created binder, you must do that on the Case Setup > Binders > Properties and Security pages for a binder.

Add a shared binder

Use the following procedure to add a shared binder and set the security for the binder.

  1. On the Case Setup > Binders page, on the toolbar, click Add.
  2. In the Add binder window, shown in the following figure, on the Properties page, provide a name and an optional description.
  3. Add binders > Properties page
  4. Under Type, leave the Shared binder type option selected.
  5. Optionally, under Use as, set the binder to be used as a Security override or Mobile binder.
  6. Click Next.
  7. On the Security page, set the security for the binder, and then click Save, as shown in the following figure.
  8. Add binders > Security page

    The new binder appears on the Case Setup > Binders page.

Add a private binder

Use the following procedure to add a private binder.

  1. On the Case Setup > Binders page, on the toolbar, click Add.
  2. In the Add binder window, on the Properties page, shown in the following figure, do the following:
    • Provide a Name and an optional Description.
    • Under Type, select Private.
    • The Owner list appears.

    • In the Owner list, select an owner.
  3. Click Save.
  4. Adding private binder

Security > Administration: Allow group leaders to add binders in the Conditional Coding pane

To allow group leaders to add binders in the Conditional Coding pane, you must set the Case Setup - Binders - Properties and Case Setup - Binders - Security functions to Allow for Leaders on the Security > Administration page.

Security > Features: Set security for the Documents Added section on the Case Home page

You can set security for the Documents Added section on the Case Home page. You can choose to display or hide the Documents Added section by enabling or disabling the Case Home - Documents added feature for groups on the Security > Features page, as shown in the following figure.

Note: This feature is set to Deny by default for all newly added groups. When a group is cloned, access to the Documents Added feature is carried over from the group it was cloned from.

Security > Features page

When this feature is set to Deny for a group, the users in that group do not see the Documents Added section on the Case Home page, and the Results History section appears in that location, as shown in the following figure.

Case Home page Results History section

When this feature is set to Allow for a group, the users in that group see the Documents Added section on the Case Home page, as shown in the following figure.

Documents Added section of Case Home page

Manage Documents > Exports: Ability to apply headers

Administrators now have the option to apply headers to base images in Custom and MDB Classic export types. In previous releases, only footer settings were available.

You can access header options on the Headers\footers page in the Export window, as shown in the following figure. The options available for footer values are also available for header values. You can select any combination of headers and footers.

Headers\footers page in the Export window

Note: The width, height, and font size are the same for both headers and footers. As with footers, the Header height setting allows you to add space to the top of the image when endorsing headers such that the header text does not overlap with image text.

Manage Documents > Imaging - Automated: Update default brightness setting to 15

In previous versions, when a file contained text with a background that was similar in color, converting the file to a black and white image could result in text and background that were the same color. We have updated the brightness setting to increase the likelihood that the text and background will be distinguishable in the resulting images.

In the Manage Documents > Imaging - Automated > Settings window, on the PDF page, the default brightness setting for new cases is now 15, as shown in the following figure. For existing cases, if the setting was previously 85, the value has been changed to 15. If the setting was previously anything other than 85, the value has not been changed.

Settings > PDF page

Manage Documents > Imports: Delimiter column removed from Field Map for Ringtail MDB load files

Ringtail MDB load files do not support using a delimiter to separate multiple field values.

Starting with this release, when you add an import job on the Manage Documents > Imports page, if you select the Ringtail - MDB job type on the Import Details page in the Import window, the Delimiter column no longer appears on the Field Map page in the Import window. The Delimiter column still appears for a Flat file job.

Note: If you clone a previous Ringtail - MDB import job and the Delimiter value was set, the value is not applied to the new import job.

Manage Documents > Productions: Apply headers

Administrators now have the option to apply headers to production images. In previous releases, only footer settings were available.

You can access header options on the Endorsements page for a production. Click in any of the boxes for Left, Middle, or Right header to launch the variable builder.

Endorsements page

You can select any combination of headers and footers. Note that the width, height, and font size are the same for both headers and footers. As with footers, the Header height setting allows you to add space to the top of the image when endorsing headers such that the header text does not overlap with image text.

Manage Documents > Productions: New Quality Control checks

The following new quality control checks have been added to the Quality Control page for productions.

  • An Annotations exist that are not selected to be applied quality control check has been added to the Quality Control page for productions, as shown in the following figure.
    • This check is enabled when at least one production rule other than Custom placeholder is selected on the Production rules page.
    • This quality control check identifies documents that have annotations applied to them that are not selected to be applied in the production.
    • If the application identifies any affected documents, a message that indicates the number of documents appears in the Result column on the Quality Control page for the production. Click the message to view the affected documents on the Documents page.

    Quality Control page viewing affected documents
  • A Documents not scanned for content quality control check has been added to the Quality Control page for productions, as shown in the following figure.
    • This checks any documents that are in a production rule and are designated to be produced as native files or content files.
    • Previously, this step was always run before locking a production, but it was not clear which documents triggered the warning. Adding this check to the Quality Control page will now provide those details.
    • If documents were not scanned for content, a message appears in the Result column on this page and lets you know which documents were not scanned for content, and indicates that you should run an Indexing and enrichment job.
    Quality Control page message in Result column

Manage Documents > Productions: New productions numbering options

The Attributes page of the Productions feature now includes new options for setting the numbering convention for production documents and files, as shown in the following figure.

Attributes page

The following options are available under Numbering on the Attributes page of a production:

  • Standard: This option offers a new, simplified way to set the Production Document Label and Production Page Label. You can enter information directly into the Prefix, Start number, and Padding boxes. Under Number by, select either Page or Document. If you choose to number by document, you can enter a value for page numbering padding and choose a delimiter to use between the document and page number, if required.
  • The following list provides examples of page and document numbering.

    • Doc 1 - page 1
      • Number by page: ABC-00000001
      • Number by document: ABC-00000001-00001
    • Doc 1 - page 2
      • Number by page: ABC-00000002
      • Number by document: ABC-00000001-00002
    • Doc 2 - page 1
      • Number by page: ABC-00000003
      • Number by document: ABC-00000002-00001
    • Doc 2 - page 2
      • Number by page: ABC-00000004
      • Number by document: ABC-00000002-00002
    • Doc 2 - page 3
      • Number by page: ABC-00000005
      • Number by document: ABC-00000002-00003
    • Doc 3 - page 1
      • Number by page: ABC-00000006
      • Number by document: ABC-00000003-00001
  • Custom: This option is the same as in previous versions. It allows administrators to enhance customization by using the variable builder to define values.
  • For productions that were locked or were created but not locked prior to this update, the selections you made for Production Document Label and Production Page Label appear in the Custom numbering section of the Attributes page.

Note: The Production Document Label determines the Rendition Document ID as well as the names of any native and content files. The Production Page Label determines the name of image files. The Production Page Label is also referred to as the Bates number. To set the Bates number as a footer, you must select the Production Page Label option, regardless of how you set up numbering on the Attributes page. Load file template field references to begin and end Bates and any other numbering values will not change.

Updates to the Renumbering feature

The following updates have been made to the Renumbering feature, which is available on the Tools menu:

  • When endorsing headers, more space is now provided between the endorsement and the edge of the page. This reduces the potential for the endorsement to be cut off when printing documents to paper.
  • The following updates have been made to the Document ID page in the Renumbering window, as shown in the following figure:
    • Suffix delimiter: This character is used before the page number during endorsement. The default character is a hyphen.
    • Note: The Suffix delimiter that you set on this page appears on the Manage Documents > Renumbering > Properties page in the Settings > Document ID section.

    • Suffix padding: This value is used when generating a suffix during endorsement. The default value is 4. Valid values are 1 through 9.
    • Note: The Suffix padding that you set on this page appears on the Manage Documents > Renumbering > Properties page in the Settings > Document ID section.

    • Override validation: If you select this option, the application assigns Document ID values starting with the selected value, even if there is an existing Document ID with a higher number.
    • Note: This option is not selected by default. Selecting this option could result in a job failure if a Document ID already exists. Selecting this option could also cause the application to assign page numbers that already exist on other documents. If you select this option, the application does not validate whether there is a Document ID in the expected range for the settings.

      Renumbering > Document ID page
  • On the Endorsement page in the Renumbering window, if you select the Document ID plus page number endorsement option, as shown in the following figure, the Start numbering on page 2 check box appears. If you select this check box, the first page of a document includes only the Document ID, but not the page number. The page numbering starts on the second page of the document.
  • Note: If you select the Document ID plus page number endorsement option on this page and select the Start numbering on page 2 check box, the setting appears on the Manage Documents > Renumbering > Properties page, in the Settings > Endorsements section.

    Renumbering > Endorsements page

Introducing the case archiving feature

Case archiving allows you to archive an entire case. Case archiving is available to system and portal administrators. You may want to archive a case if you no longer need the database to be readily available in Nuix Discover, but you want the option of restoring it in the future should the need arise.

When you archive a case, it is stored in a folder on the archive repository that is assigned to the case. The folder will include backup files of all three of the case databases, zip archives containing all files from the repositories assigned to the case, and a backup of the coding history index (if the case has audit enabled for coding history). After you archive a case, you can download the case files, recommission the case, or permanently delete the case.

Note: Portal and system administrators can do everything described in this section.

Archive a case

You can archive an entire case using the Decommission option, which is available on the More menu on the Cases page.

Use the following procedure to decommission and archive a case.

  1. On the Cases page, select the case you wish to archive.
  2. On the More menu, select Decommission, as shown in the following figure.
  3. More menu Decommission selection

    The Decommission case window appears, as shown in the following figure.

  4. The Decommission case dialog box has been changed to a wizard-style window with two pages: Options and Summary. The Options page now includes a choice for Archive (selected by default) or Permanently delete, which was previously the only option available when decommissioning a case. Select Archive, and then click Next.
  5. Decommission case > Options page
  6. The Summary page, shown in the following figure, displays the destination folder where the archived case will be stored, the total size of the case to be archived (as captured by the latest case metrics job), and a listing of the database and analysis servers, Elasticsearch index name, and the repositories that are assigned to the case. To archive the case, click OK.
  7. Decommission case > Summary page

    Note: If files were archived while the case was live, the folders containing those file archives will remain adjacent to the new folder that is created for the case archive. The previously archived files will not be “re-archived” to the case archive destination folder.

    If the case does not have an archive repository currently assigned, the Destination field shown in the following figure will display a list of the available archive repositories. Select an archive repository to assign as the destination for the archived case.

    Decommission case > Summary page Destination selection

    Note: When organizations security is enabled for the portal, the archive repository that is assigned to the case must also be assigned to the case’s organization to allow for the case to be archived.

  8. After you click OK, a Case Decommission job will run in RPF and will archive the case. The worker processing window will open and display the progress of the job stages, as shown in the following figure.
  9. Note: You do not need to keep the worker processing window open while the job is running. You can also monitor the job progress in the Progress column for the case row on the Cases and Servers > Cases page, or by viewing the job on the Processing > Jobs page.

    Processing > Jobs page

    Note: When the job begins, the case will be taken offline and users will no longer be able to access the case. Any scheduled RPF jobs for the case will be removed.

  10. If the job fails at any point, the case will appear with a Failed status on the Cases and Servers > Cases page. You can use the Resubmit option to attempt to resume the job. This will restart the job on the stage where it left off. To resubmit the case for decommission, select the case, and on the More menu, click Resubmit, as shown in the following figure.
  11. Resubmit decommission

After a case is successfully archived, it will appear on the Cases page with an Archived status, as shown in the following figure.

Cases page with an Archived status

About archived case files

When you archive a case, Nuix Discover saves a variety of case files. An example of the types of files that are stored for an archived case is shown in the following figure.

The types of files for your archived case include:

  • .bak files for all three of the case SQL databases.
  • Zip archives containing all files from the repositories assigned to the case.
  • Note: Zip file names include the top-level folder name from the repository. An empty .zip file will be created to represent a folder that does not contain any files in the case subfolder. Files are batched into .zip archives that are approximately 2 GB in size. Depending on the total size of files contained in a repository folder, this could result in multiple .zip archives for a top-level folder. In that case, each .zip archive will be named uniquely with a numeric suffix.

  • A .zip archive containing the coding history Elasticsearch index.
  • .csv files that contain a file inventory of each top-level folder from each repository. These inventory files are used for the validation stages of the decommission and recommission jobs.
  • .csv files containing a file inventory

When you archive a case, you also have three new options on the More menu.

The following options are available for an archived case on the More menu on the Cases page, as shown in the following figure:

  • Download files: This will download a copy of all files for the archived case.
  • Recommission case: This will restore the case and all files back to their original locations.
  • Delete: This will permanently delete the archived case with no backup.
  • More menu features

Download case files from an archived case

You can download case files from an archived case and save a copy of those files locally using the Download files option on the More menu on the Cases page.

Use the following procedure to download case files from an archived case.

  1. On the Cases page, select the archived case.
  2. On the More menu, select Download files, as shown in the following figure.
  3. More menu > Download files selection

    The Download files dialog box appears, as shown in the following figure.

  4. In the Download files dialog box, you will see the total size of the files for the archived case that will be downloaded. Click OK.
  5. Download files dialog box

    The worker processing window appears, as shown in the following figure.

  6. The worker processing window displays the status for the files being downloaded. Keep this window open, as all files will be downloaded through this window.
  7. Note: Depending on your browser settings, you may be prompted to allow for multiple files to be downloaded.

    Download jobs progress dialog box

Delete an archived case

After you decommission and archive a case, you can delete it permanently using the Delete option on the More menu on the Cases page.

Use the following procedure to delete an archived case.

  1. On the Cases page, select the archived case.
  2. On the More menu, select Delete, as shown in the following figure.
  3. More menu Delete selection

    The Delete archived case dialog box appears, as shown in the following figure.

  4. In the Delete archived case dialog box, select the Delete this case and all associated files check box to enable the OK button, and then click OK to permanently delete the archived case with no backup.
  5. Delete archived case dialog box
  6. The Decommissioned Case Deletion job will run in RPF and will permanently delete the archived case. The worker processing window opens and displays the progress of the job stages, as shown in the following figure.
  7. Note: You do not have to keep the worker processing window open while the job is running. You can also monitor the job progress in the Progress column for the case row on the Cases and Servers > Cases page, or by viewing the job on the Processing > Jobs page.

    Processing > Jobs page
  8. If the job fails at any point, the case will appear with a Failed status on the Cases and Servers > Cases page. You can use the Resubmit option to attempt to resume the job. This will restart the job on the stage where it left off. To resubmit a case to be deleted, select the case, and from the More menu, click Resubmit.

After an archived case is successfully deleted, it will be logged to the Cases and Servers > Deleted Cases page.

Recommission a case

You can recommission an archived case by using the Recommission case option on the More menu on the Cases page.

Use the following procedure to recommission an archived case.

  1. On the Cases page, select the archived case.
  2. On the More menu, select Recommission case, as shown in the following figure.
  3. More menu Recommission case selection

    The Recommission case dialog box appears, as shown in the following figure.

  4. The Recommission case dialog box displays the same repositories that were assigned to the case at the time it was archived. To recommission the case, click OK.
  5. Recommission case dialog box confirmation

    Note: The original servers and repositories that were assigned to the case at the time it was archived are selected by default. The selected Image, Index file, and File transfer repositories will be the destinations for restoring the files. The selected Archive repository is where the recommission job will look for the archived case files to be restored.

    Note: If an original repository is no longer available in the portal, a warning icon will appear next to that item, as shown in the following figure, and the field will display a list of the available repositories. Select a new repository to assign as the repository type to restore the files to.

    Recommission case dialog box warning
  6. A Case Recommission job will run in RPF and will restore the case. The worker processing window will open and display the progress of the job stages, as shown in the following figure. You do not have to keep the worker processing window open while the job is running.
  7. Note: You can also monitor the job progress in the Progress column for the case row on the Cases and Servers > Cases page, or by viewing the job on the Processing > Jobs page.

    Processing > Jobs page
  8. If the job fails at any point, the case will appear with a Failed status on the Cases and Servers > Cases page. You can use the Resubmit option to attempt to resume the job. This will restart the job on the stage where it left off. To resubmit a case to be recommissioned, select the case, and on the More menu, click Resubmit.

After a case is successfully recommissioned, it will appear on the Cases page with a Valid status, as shown in the following figure.

Cases page with a Valid status

Note: The recommission job will attempt to reassign the same users to the case who were assigned at the time the case was archived, assuming those users are still available in the portal.

Report on decommissioned cases

You can see archived cases on the Reports > Hosted Details page by using the Status column filter to show or hide cases with an Archived status, as shown in the following figure.

Reports > Hosted Details page

Note: Case metrics are refreshed at the end of the case decommission job so that after a case is successfully archived the total size of the archived case will be represented in the Archive data (GB) column on the Hosted Details page.

Cases and Servers: Database and Analysis servers prepopulated for Organizations when adding or cloning a case

When you add a new case, the Database and Analysis servers for that Organization are prepopulated on the Servers page in the Add case window, as shown in the following figure.

Add case > Servers page

When you clone a case, the Database and Analysis servers for that Organization are prepopulated on the Servers page in the Clone case window, as shown in the following figure.

Servers page showing Database and Analysis servers prepopulated

Cases and Servers > Clone Case: Audit for coding history is enabled by default for new cases

If the coding history audit feature is enabled for a portal, when you clone a case and leave the Clear data option unselected, as shown in the following figure, auditing is now automatically enabled.

The benefit of this is that you do not have to request for the coding history audit feature to be enabled by a system administrator after you create a case.

Case Details page showing cloned case details

After you clone a case, a new elastic index is created for the new case, and audit is enabled for coding history.

Case and Servers > Case Options: New case options for the Predictive Coding feature

The following case options for Predictive Coding have been added to the Portal Management > Case and Servers > [Case] > Case Options page.

Tip: Hover over an infotip to view additional information about an option.

  • Predict Large Document Truncation Length: Amount of characters to keep at the beginning of a long text after truncation.
    • Default value: 100000000
  • Predict Max Document Size: Maximum size (in MB) of a document allowed before its contents are truncated.
    • Default value: 500
  • Predict Tokenization Batch Max Size: Maximum size in bytes of a batch allowed when there is more than one document.
    • Default value: 300

Cases and Servers: Clone a case from one Organization to another Organization

When you clone a case, you can now select a different Organization than the Organization that is currently associated with the case that you are cloning, as shown in the following figure.

Case Details page selection of different organization

Settings: Portal Options: New setting to limit the size of an audio file in the View pane

A new option named View pane maximum audio file size is now available on the Portal Management > Settings > Portal Options page, as shown in the following figure. Use this option to set the maximum file size in bytes when streaming audio files in the View pane. This new option, which can be set to a maximum value of 31457280 bytes, addresses IIS performance issues for .wav files.

Portal Management > Settings > Portal Options page

Settings > Log Options: Change to storing logs in the database

On the Portal Management > Settings > Log Options page, shown in the following figure, if you select the Store logs in database option, but do not provide any information in the Telemetry archive configuration box, the Telemetry Archive job runs once per day and truncates the database table for logs that are older than seven days.

Portal Management > Settings > Log Options page

User Administration > Account Settings: Increase the password history maximum setting to 24

On the Portal Home > User Administration > Account Settings page, in the Password history box, administrators can enter the number of times users must create a unique password before it can be reused. In previous versions, administrators could select 1-20 unique password entries. Now, administrators can select 1-24.

Cases and Servers: Enable Linux\Docker Ingestions option relocated to the portal level

The Enable Linux\Docker Ingestions option has been removed from Case Options and relocated to Portal Options. On the Portal Home > Settings > Portal Options page, if you select the Enable Linux\Docker Ingestions check box, all cases in the portal will use this setting.

Note: Cases that were configured in previous versions will respect the prior setting. To change the case setting for an existing case, you must use a SQL query.

Organizations: Note about changing case metrics settings

When you change the case metrics settings for an organization in the Case metrics settings dialog box on the Portal Management > Organizations page, a banner that indicates that the daily metrics are being saved for organizations will now appear at the top of the page while the scheduled jobs are being saved for cases in the organizations, as shown in the following figure. The banner will be removed after all jobs are saved.

Portal Management > Organizations page banner indicating the daily metrics

Important: You can continue working while the jobs are being saved, but do not log out of Nuix Discover until you see that the banner is removed.

The time that it takes for the jobs to finish saving depends on the size of your environment.

Connect API Explorer: OneGraph GraphiQL Explorer API query builder

The Connect API Explorer now contains the OneGraph GraphiQL Explorer plug-in. This plug-in is a query builder that assists users, both new and advanced, in quickly and easily generating queries and mutations with a graphical representation of the data fields and objects and helps avoid the frustration of incorrect syntax.

The Connect API Explorer window now contains four panes, as shown in the following figure, and described in the following table.

Connect API Explorer window showing the available panes
  • Pane #1 Explorer pane:
    • New query builder for automated assistance in constructing queries and mutations.

    Note: To close the Explorer pane, click the X button. To reopen this pane, click the Show explorer button in the Editor pane.

  • Pane #2 Editor pane:
    • Area for constructing, formatting, and running queries and mutations.
  • Pane #3 Results pane:
    • Contains query and mutation results.
  • Pane #4 Documentation Explorer pane:
    • Documentation details for all query and mutation endpoints and their associated arguments and fields.

Each time you enter the Connect API Explorer, the Explorer pane will begin with a default query under the Me argument related to data associated with you, the user.

Use the following procedure to manipulate any query or mutation.

Note: This example creates a basic query filtering on all active cases and sorts them by case name in ascending order.

  1. To create a new query or mutation, in the Add New field, at the bottom of the Explorer pane, select Query or Mutation from the list, and then click the + sign, as shown in the following figure.
  2. Explorer pane Add New button

    The new blank query or mutation will appear in the Explorer and Editor panes with a default name.

  3. To copy an existing query or mutation, to the right of the Name field, hover over and click the Copy button, as shown in the following figure.
  4. Explorer pane Copy button

    A duplicate copy will appear under the existing queries and mutations in the Explorer and Editor panes.

    Note: You can manipulate multiple queries and mutations simultaneously.

  5. Enter a unique Name.
  6. The change appears in the Explorer and Editor panes.

    Note: It is best to give your query or mutation a unique name to help identify their function.

  7. In the Explorer pane, expand the cases list by clicking the expand arrow, as shown in the following figure.
  8. Explorer pane expanded objects list

    The cases argument is added to the Editor pane with the proper syntax.

    Note: Filter fields appear in purple and are used for filtering the returned data by a specified value you enter. Fields that appear in blue are used for returning any data value within that field.

    Important: If you close an expanded list in the Explorer pane, and already have several fields and filters selected, closing the list will delete the selections from the query or mutation. However, those selections are cached, and by expanding the list again, the selected fields and filter data will reappear.

  9. Select the check boxes for the id and name fields shown in blue text, shown in the following figure in step 7.
  10. The fields appear in the Editor pane in the proper location and surrounded by the correct syntax.

    Note: If you manually enter these fields in the Editor pane, the check boxes are automatically selected in the Explorer pane.

  11. Select the check box for the active field shown in purple text, shown in the following figure in step 7, and then select true.
  12. Note: When filtering with multiple values, such as multiple IDs, the builder does not support arrays. You must enter the multiple filtering values manually in the Editor pane.

  13. Expand the sort field shown in purple text, and then do the following.
    • Select the check box for the dir field, and then select Asc.
    • Select the check box for the field* field, and then select name.
    • Important: The asterisk (*) following a field name indicates a required field. If selected, this field must contain a data value to filter on.

    The query now contains all of the selected fields and filter options, as shown in the following figure.

    Explorer and Editor panes showing example query
  14. To delete the query or mutation and start over, hover over the name in the Explorer pane, and then click the X button, as shown in the following figure.
  15. Explorer pane Delete button

    The query or mutation is deleted from both the Explorer and Editor panes.

  16. To run a query or mutation, in the Editor pane, click the Execute query button.
  17. Note: If you have multiple queries and mutations, a list will appear where you can select one for execution. However, all queries and mutations must be valid to run that selection successfully.

    The results will appear in the Results pane.

Connect API Explorer: Identify archived cases using the decommissionStatus field

In the Connect API Explorer, the caseDecommissionStatusEnumType filter now includes the status Archived as a value by using the decommissionStatus field.

Sample query:

query {
  cases (decommissionStatus: Archived) {
    name
    caseDecommissionedBy
    caseDecommissionedDate
    decommissionStatus
  }
}

Sample query results:

{
  “data”: {
    “cases”: [
      {
        “name”: “Acme”,
        “caseDecommissionedBy”: “Doe, John”,
        “caseDecommissionedDate”: “2020-06-15T18:35:55.743Z”,
        “decommissionStatus”: “Archived”
      }
    ]
  }
}

Connect API Explorer: Search coding history values using the PreviousValueEverWas operator

The operator PreviousValueEverWas is now available in the API for searching on values in coding history.

Sample mutation:

mutation {
  searchRun (caseId: 2, input: {
    include: MatchingItems,
    renditions: false,
    singleQuery: {
      field: “Document ID”,
      operator: PreviousValueEverWas,
      value: “A”
    }
  }) {
    id
    label
    count
    dateRun
    entityId
    items {
      id
      itemId
    }
  }
}

Sample mutation results:

{
  “data”: {
    “searchRun”: {
      “id”: 742,
      “label”: “--/“Document ID/” previous value ever was /“A/””,
      “count”: 0,
      “dateRun”: “2020-06-19T14:18:53.027Z”,
      “entityId”: 1,
      “items”: []
    }
  }
}

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.

As of the Nuix Discover 10.4 quarterly release to on-premises clients, the following Microsoft server products are supported:

  • Microsoft Windows Server Operating System
    • Microsoft Windows Server 2012 R2
    • Note: (End-of-support notice) Microsoft Windows Server 2012 R2 will no longer be supported as of the 10.5.011 release in January of 2020.

    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2019
  • Microsoft SQL Server
    • Microsoft SQL Server 2016 SP2
    • Microsoft SQL Server 2017 CU21
    • Microsoft SQL Server 2019 CU6

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

Login Service version 2.3.15 now includes an installer

This installer is intended for deployment on Windows servers. New versions of Nuix Discover will continue to be compatible with Login Service version 2.2.21, so you can upgrade at your convenience. The Login Service can be installed using the Nuix Discover Deployer version 2.5.94 and higher.

Ingestions: NIST list updated - June 2020

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

Ingestions: Upgrade to the Nuix Engine 8.6.3

Ingestions now uses the Nuix Workstation 8.6.3 processing engine.

Nuix Discover 10.3 Quarterly Release Notes

Default start page for a group

Your administrator can now define the Nuix Discover page that appears for your group after you log in to the application. For example, if your administrator sets the start page for your group to be the Documents page, that page appears after you log in, and Workspace A appears.

Case Home page menu: Search page option

The Case Home menu now includes a Search option, as shown in the following figure. Click Search to access the Search page.

Note: You can still access this page using the Search button on the toolbar on the Case Home or Documents pages.

Case Site Map - Search page

Translate: Propagate translated text to duplicate documents

When you submit a document for translation, the translated text is propagated across all duplicates of the document, so that you do not have to translate each duplicate document individually.

Note: The application does not translate documents with branded redactions.

Also, the following applies to the translated duplicate documents:

  • The application codes the Translation Language system field with the same target language as the translated document.
  • The application codes the Translation Status system field with the same value as the translated document.

Introducing the Memo Editor pane

Nuix Discover now has a new Memo Editor pane, as shown in the following figure. This new pane is available for both documents and entities. It contains the existing Memo Editor formatting capabilities, as well as a new and quicker way of creating and removing links, and a new feature for downloading memos in Hypertext Markup Language (HTML) format.

Memo Editor pane

Note: The Memo Editor pane does not replace the existing editor capability within memo fields.

The following list provides an overview of the features available in the Memo Editor pane:

  • Memo field selection: To switch between the active memo fields, click the drop-down list on the toolbar and select a field. You can select the Comments, Timelines Description, [Meta] Chat HTML, and Document Description fields, as well as many others.
  • Note: From the memo fields drop-down list, the Memo Editor pane allows you to access only the one-to-one memo fields.

  • Hyperlinks: Creating hyperlinks to documents, binders, transcripts, or other data takes fewer mouse clicks using the Memo Editor pane. Hyperlinking is also available for both documents and entities. In previous releases, you could not hyperlink to entities.
    • When you enter text to create a link and either double-click or highlight the text, an inline menu appears that contains the Document link, Object link, Transcript link, Web link, and Remove link options, as shown in the following figure.
    • Inline menu

      After selecting a link option, a dialog box appears that allows you to search for and to select the link data.

      Note: The inline menu for linking replaces the Link toolbar button in the existing memo capability.

    • To view link contents, each link contains a tooltip that appears when you point to an existing link, as shown in the following figure.
    • Memo Editor pane linking tooltip
    • Linked content opens when you hold down the Ctrl key on the keyboard and click the mouse.
    • To remove a link, double-click the link and select Remove link.
    • Note: You cannot edit the text in existing links. You must first remove the link, then correct spelling errors or other mistakes made in the link text.

  • Auto-search linking: The Mentions feature allows you to do a quick search for document links.
    • When you type the hash (#) sign, followed by six or more characters of a Document ID, an inline list appears with matching search results, as shown in the following figure.
    • Inline selection list

      Select an item from this list to automatically create a link to the selected document and insert the link into the memo.

      Tip: You cannot create a link back to an active document.

  • Downloading: The Download button allows you to export memos to HTML, as shown in the following figure.
  • Memo download details

    The top portion of the HTML file shows general information such as the case, user, date downloaded, and other information. Memo text follows.

    • If the memo contains links, you can view the link contents in the same manner as in the Memo Editor pane. However, because transcript links are embedded data and do not have an associated URL, they do not open from the downloaded HTML file. They open only from the Memo Editor pane.

Note: If you have not previously logged in to Nuix Discover, the login page appears before opening the linked document.

Renumbering: Change the Document IDs and leveling of documents

You can now use the Renumbering feature in Nuix Discover to change the Document ID format of documents. Once you have specified a Document ID format, the application does the following:

  • Images the selected documents and converts them to a PDF format.
  • Applies the specified numbering rules.
  • Relevels the documents to match the new Document IDs.
  • Applies endorsements to the PDF image.
  • Replaces the PDF image with the endorsed version.

You can view the endorsed PDF images in the Image viewer in Nuix Discover.

Renumber documents

You can renumber imported documents using the Renumbering option on the Tools menu, shown in the following figure.

Caution:: Do not run multiple simultaneous renumbering jobs with the same Document ID prefix in a case.

Select one or more documents to enable this tool.

Document selection to enable renumbering tool

On the Exclusions page, shown in the following figure, you can determine the following information:

  • Types of files to include and exclude in your renumbering.
  • If the native file should still appear in the Image viewer in Nuix Discover.
  • How the application will handle documents that fail to image to PDF.
Renumbering Exclusions page

On the Slipsheets page, shown in the following figure, you can select which files to insert slipsheets for, and use the variable builder to determine what text appears on the slipsheets.

Renumbering Slipsheets page

On the Document ID page, shown in the following figure, you can determine the following information:

Renumbering Document ID page
  • The format for how the files will be renumbered. You can select a format that includes a prefix, box, folder, page, and delimiter, or you can select a format that includes only a prefix and padding.
    • The following options are available in the Format list:
      • Prefix, Box, Folder, Page - increment by page
      • Prefix, Box, Folder, Page - increment by document
      • Prefix with consecutive numbering
  • If document families must stay together in a folder after renumbering.
  • If levels should be updated to correspond to the new numbering. This option is available only if you select the Prefix, Box, Folder, or Page format.
  • Override validation: If you select this option, the application assigns Document ID values starting with the selected value, even if there is an existing Document ID with a higher number.
  • Note: This option is not selected by default. Selecting this option could result in a job failure if a Document ID already exists. Selecting this option could also cause the application to assign page numbers that already exist on other documents. If you select this option, the application does not validate whether there is a Document ID in the expected range for the settings.

On the Endorsement page, shown in the following figure, you can determine what information goes in the header and footer of renamed documents.

Renumbering Endorsement page Header and Fotter contents

If you select the Document ID plus page number endorsement option, as shown in the following figure, the Start numbering on page 2 check box appears. If you select this check box, the first page of a document includes only the Document ID, but not the page number. The page numbering starts on the second page of the document.

Renumbering Endorsement page Document ID page number

Security > Groups: Set the default start page for a group

You can now set a default start page for a group. One of the benefits of this new feature is that you can, for example, route users directly to the Documents page so that they can start reviewing documents. Workspace A appears by default on the Documents page.

Use the following procedure to set the start page for an existing group.

  1. On the Security > Groups page, in the Name column, click the link for a group.
  2. On the Properties page, in the Start page list, shown in the following figure, select one of the following start pages: Documents, Search, Transcripts, Production Pages, Security, Case Setup, Manage Document, Review Setup, Analysis.
  3. Note: The Case Home page is the default start page.

    Case Home - Properties page
  4. Click Save.
  5. The next time a member of the group logs in to the application, the designated start page appears. For example, if you set the Documents page as the start page, the Documents page appears by default.

Use the following procedure to change the start page for an existing group.

  1. On the Security > Groups page, on the toolbar, click Add.
  2. In the Create group dialog box, shown in the following figure, do the following:
    • In the Name box, provide a name.
    • In the Start page list, select a page.
    • Create group dialog box
  3. Click Save.

Security > Features: Memo Editor pane configuration

To make the Memo Editor pane available to users, on the Case Home > Security > Features page, an administrator must set the Document – Memo editor feature to Allow for a group. By default, this feature is set to Deny.

Security > Features: Renumbering: Enable the renumbering feature

On the Security > Features page, administrators can enable the renumbering feature using the Processing - Renumbering option.

Case Setup > System Fields > Renumbering: Enable renumbering system fields

On the Case Setup > System Fields page, administrators can make renumbering-related system fields available to users. If the renumbering system fields are enabled, users can search for the fields and display the fields as columns in the List pane.

The following renumbering system fields are available:

  • Renumbering Status
  • Renumbering Previous Document ID
  • Renumbering ID

Manage Documents > Exports: Option to include blank text files

For custom export types (base or renditions), a new option is available in the Export window to include a blank .txt file for all documents in the export that are missing a .txt file, as shown in the following figure. For base documents, the option is available on the File types page in the Settings window (available when you click the Settings button, or gear).

Option for base document export

Export - Settings Options dialog box

For rendition documents, the option is available on the File types page, as shown in the following figure.

Option for document export.

Export (Renditions) dialog box

If you select this option, along with the option to export content files, the application exports a blank .txt file for documents without an existing .txt file or associated extracted text. For base documents, the application names the .txt file according to the document ID. For rendition documents, the application names the .txt file according to the production document label for renditions. The blank .txt files are referenced in any load files that have a field for the text file name.

Note: When exporting base documents, if the application excludes any .txt files from an export because of annotations, a blank .txt file is not exported for those documents. The option to omit text files if a document is annotated is on the Annotations page in the Settings window (available when you click the Settings button, or gear).

To help administrators easily identify documents for which blank .txt files were exported, the following message appears on the Warnings page of the export job: “A blank content file (.txt) was exported because no content\.txt file was found for a document.”

Manage Documents > Imaging: Add time zone setting for email file conversion

Administrators can now select a time zone for rendering native email files into images. The Time zone option is available in the Manage Documents > Imaging-Automated > Settings window on the Email and Website page. Administrators can select Use ingestions default or a specific time zone. If the administrator selects Use ingestions default, the application uses the time zone set in the default settings for Ingestions.

Manage Documents > Imports: Prevent the creation of a new field with the same name as a system field

In the Import settings window, on the Field Map page, if a user creates a new field with the same name as an existing system field but of a different type, the application does not allow the user to continue. The field is outlined in red, and the following message appears: “New field cannot match an existing system field's name.”

Manage Documents > Ingestions: Upgrade to the Nuix Engine 8.4.5

Ingestions now uses the Nuix Workstation 8.4.5 processing engine. The engine upgrade resolves the out-of-memory failures when processing some forensic images.

Manage Documents > Renumbering: View renumbering job properties

On the Manage Documents > Renumbering page, administrators can view the properties and progress of renumbering jobs. Click a renumbering job in the list to view the properties or errors for the job.

Note: Administrators can allow Group Members and Group Leaders to access the Manage Documents > Renumbering page. On the Security > Administration page, in the Leaders or Members columns, set the Manage Documents – Renumbering Management function to Allow, and then click Save.

Portal Management > Processing > Index Status: Only document entities are included in the index status counts

On the Portal Management > Processing > Index Status page, shown in the following figure, only document entity items are included in the indexing counts in the Documents columns (Total, Indexed, Waiting, Excluded, Failed). Non-document entity items are not captured.

Portal Management - Processing - Index Status page

Portal Management > Reports: New Max data (GB) column in Hosted Details report

The Hosted Details report includes a new column named Max data (GB), shown in the following figure.

This column displays the maximum active hosted data size for a case within a specified date range and captures the following data: sum value of base documents, production renditions, databases, the Elasticsearch index, the content index, and Predict data. This column also includes a calendar icon. Hover over the calendar icon to display the date of the maximum value.

Hosted Details page including the Max data (GB)

If you download a report, it will now include the following two columns and values:

  • Max data (GB): The maximum active hosted data size for a case.
  • Max data (date): The date the maximum active hosted data size was captured.

Portal Management > Settings: Text extraction: Update batching logic in text extraction job

In previous versions, the application processed text extraction jobs in batches using the number of files per batch that was specified in the Extract text job batch size case setting. (To access this setting, go the Portal Management > Cases and Servers > Cases page and click on the name of a case.)

To efficiently accommodate larger files, portal administrators can now set batch thresholds by file size using the Extract text job max batch file size portal setting, shown in the following figure.

To access this setting, go to the Portal Management > Settings > Portal Options page. The application determines the text extraction job batch size using whichever is smaller in file size: the number of files specified in the case setting or the maximum file size per batch specified in the portal setting.

Portal Options page shows the Extract text job max batch file size

Portal Management > Settings > Log Options: Multiple S3 bucket entries supported for the Telemetry archive configuration

The Telemetry archive configuration field on the Portal Management > Settings > Log Options page now has a new “S3Buckets&lrquo; setting that supports multiple entries for the key, secret, region, and bucket values.

When telemetry is configured to store the logs in the database, and the configuration string includes multiple S3 buckets, the telemetry data is pushed to all S3 buckets.

The following example shows how to format the JSON configuration string with multiple S3 buckets.

{
“Checkpoint”: 0,
“CheckpointRPF”: 0,
“S3Buckets”: [
{ “Key”: “******”, “Secret”: “******”, “Region”: “us-east-1”, “Bucket”: “s3-bucket-1” }
,
{ “Key”: “******”, “Secret”: “******”, “Region”: “us-east-1”, “Bucket”: “s3-bucket-2” }
],
“CleanupMaxDays”: 3,
“ScheduleId”: 22,
“IntervalInMinutes”: 30,
“NRecentRecordsToReturn”: 10000
}

Portal Management > Cases and Servers: Delete case record from the portal database for deleted cases

After a case is deleted, as a system administrator, you can delete the case record for the deleted case from the portal database. You can also then create a new case using the same case name.

Use the following procedure to delete the case record for a deleted case.

  1. On the Portal Management > Cases and Servers > Deleted Cases page, select the check box next to a case.
  2. On the toolbar, click Delete record.
  3. In the Delete record dialog box, shown in the following figure, select the Delete case record and all metrics check box.
  4. Note: Once you select this check box and click OK in the following step, the case record and all metrics are permanently deleted from the portal database.

    Delete record dialog box
  5. Click OK.
  6. After you delete the record, the deleted case no longer appears on the Deleted Cases page or the Portal Management > Reports page.

Portal Management > Organizations: Default template case for cloning

System administrators can now select a default case to clone at the organization level.

The following new setting is now available on the Properties page for an organization, as shown in the following figure: Default template case for cloning.

Properties page

Portal Management > Organizations: Schedule daily case metrics jobs

System administrators can now schedule daily case metrics jobs for organizations and all cases in those organizations.

Note: This feature is not available to portal administrators.

Use the following procedure to schedule a daily case metrics job for an organization.

  1. On the Portal Management > Organizations page, on the toolbar, click the Case metrics button.
  2. The Case metrics settings dialog box appears.

  3. In the Case metrics settings dialog box, shown in the following figure, in the Time list, select a time.
  4. Note: The time appears in the user’s local time.

  5. Select one or more organizations.
  6. Note: To select all organizations, select the blue checkmark, shown in the following figure.

  7. Click Save.
  8. Case metrics settings dialog box

    The jobs are scheduled to run daily, at the time you selected. The newly scheduled jobs are added to all existing cases for the selected organization or organizations. For cases that are added to an organization after the job has been scheduled, the settings for the organization apply.

    Note: These settings do not override previously scheduled jobs.

Use the following procedure to cancel a daily case metrics job.

  1. Open the Case metrics settings dialog box.
  2. Clear the check box for the selected organization or organizations.
  3. Click Save.

After you schedule a daily case metrics job, in the table on the Portal Management > Organizations page, an icon in the second column indicates if a daily case metrics job is scheduled for an organization, as shown in the following figure.

Note: This column is visible only to system administrators.

Organizations page

Once the daily case metrics job is complete, the values in the following columns are updated on the Portal Management > Reports > Hosted Details page:

  • Base documents (GB)
  • Production renditions (GB)
  • Databases (GB)
  • Elasticsearch index (GB)
  • Content index (GB)
  • Predict (GB)

The values in the following columns are not updated as part of a daily case metrics job. Rather, the values in these columns reflect the values from the last Gather case metrics job that was run:

  • Orphan (GB)
  • File transfer data (GB)
  • Archive data (GB)
  • Missing (GB)

To update the values for these columns, you must run a full Gather case metrics job on the Portal Management > Processing > Jobs page.

Connect API Explorer: maxActiveHostedSize and dateOfMaxActiveHostedSize case statistics

There are two new case statistics available through the Connect API Explorer that will return the maximum value of the aggregateActiveHostedSize and the date of that value within a specified date range.

Note: The aggregateActiveHostedSize statistic is the sum of sizeOfBaseDocumentsHostedDetails, sizeOfRenditionsHostedDetails, aggregateDatabases, sizeOfElasticSearchIndex, dtIndexSize, and sizeOfFolderData_Predict.

  • maxActiveHostedSize: Returns the maximum value of aggregateActiveHostedSize within a specified date range. This value calculates from the first minute of the startDate (12:00:00am) to the last minute of the endDate (11:59:59pm) in Coordinated Universal Time (UTC).
    • When only providing the endDate for the date range, the returned value is the highest value of the aggregateActiveHostedSize calculating from the beginning of the case to the last minute of the specified endDate.
    • When there is no startDate or endDate provided, the returned value is the highest of the aggregateActiveHostedSize over the entire life of the case, from the beginning of the case through the current day.
  • dateOfMaxActiveHostedSize: Returns the date of the maxActiveHostedSize within a specified date range.
    • When only providing the endDate for the date range, the returned value is the date of the maxActiveHostedSize calculating from the beginning of the case to the last minute of the specified endDate.
    • When there is no startDate or endDate provided, the returned value is the date of the maxActiveHostedSize over the entire life of the case, from the beginning of the case through the current day.
Sample query:
query {
  cases {
    name
    statistics(startDate: “2020-04-01”, endDate: “2020-04-30”) {
      maxActiveHostedSize
      dateOfMaxActiveHostedSize
    }
  }
}

Import API: Delete files from the S3 bucket upon completion of an import job

If the import job setting is to copy files from S3, once the files are copied, the application deletes the files from the S3 bucket. The application deletes the files for only those import jobs that completed successfully. The application does not delete files in failed import jobs.

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.

As of the Nuix Discover 10.3 quarterly release to on-premises clients, the following Microsoft server products are supported:

  • Microsoft Windows Server Operating System
    • Microsoft Windows Server 2012 R2
      • End-of-support notice: Microsoft Windows Server 2012 R2 will no longer be supported as of the 10.6.000 release in December of 2020.
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2019
  • Microsoft SQL Server
    • Microsoft SQL Server 2016 Standard SP2
    • Microsoft SQL Server 2017 Standard CU5 and higher
    • Microsoft SQL Server 2019 CU5

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

Upgrade to Nuix Engine 8.4.5

Ingestions now uses the Nuix 8.4.5 engine. The engine upgrade resolves the out-of-memory failures when processing some forensic images.

Login Service version 2.3.15 now includes an installer

  • This installer is intended for deployment on Microsoft Windows Servers.
  • New versions of Nuix Discover will continue to be compatible with Login Service version 2.2.21.
  • The Login Service can be installed using the Nuix Discover Deployer version 2.5.94 and higher.
  • The Login Service is an optional feature.

Nuix Discover 10.2 Quarterly Release Notes

Translate: New and updated source languages

The Translate feature now includes additional source language options, for example, Irish and Punjabi, when translating with Microsoft.

Some of the source language options for Google were renamed. For example, Portuguese was renamed to Portuguese (Portugal, Brazil).

These new or updated source language options are available in the Translate workspace pane and the Tools>Translate dialog box.

Coding History for fields updated by import jobs

The Coding History feature now captures audit records for field values that are updated by import jobs for existing document records.

The Coding History pane will include the following information:

  • The updated field value.
  • The user who created the import job as well as the date and time of the import job.
  • The previously coded value that was changed.
  • The user who applied the coding as well as the date and time of the previous coding.

Note: Your administrator must grant you read access to these fields so that they appear in the Coding History pane.

Imports: Run indexing and enrichment using an import job

The Imports feature now allows you to request an indexing and enrichment job after an import job completes. On the Case Home>Manage Documents>Imports page, the Import Details page contains an option to Run indexing and enrichment, as shown in the following figure.

Import Details page

Selecting this option will run an indexing and enrichment job immediately after an import job completes. After adding a new import job, you can verify the selection of this option by clicking on the Import ID for that job and looking under the Import Details section of the Properties page, as shown in the following figure. The Run Indexing and Enrichment property indicates Yes if selected, or No if not selected.

Import Details Properties page

Imports: Delete data from S3 bucket after completing import jobs

If files in an import job are copied from S3, the application deletes the files that were in the S3 bucket once the import job has successfully completed.

Ingestions: Nuix Engine upgrade to version 8.4.3

The Ingestions feature in Nuix Discover for Windows and Linux now uses the Nuix Engine version 8.4.3.

This upgrade includes the following improvements:

  • Handling of OneNote files is improved. More content and attachments are extracted from OneNote data.
  • Support added for HEIC/HEIF file formats.
  • CAD drawing attachments are no longer treated as immaterial.
  • General improvements made to processing EnCase L01 files.
  • Differences in MD5 hash values between emails collected from Office 365 and emails from other sources due to sender address differences no longer occur.

Nuix Engine 8.4.3 requires an upgrade of the Nuix Management Server (NMS). To retrieve a copy of the NMS version 8.4 for installation, paste the following link into a browser: https://download.nuix.com/releases/server. Then, log in to the Nuix Customer Portal.

To access all Nuix Workstation 8.4 documentation, paste the following link into a browser: http://download.nuix.com/nuix_workstation_suite. Then, log in to the Nuix Customer Portal.

Ingestions: New system fields for ingestions

We have added the following three system fields to the Ingestions feature:

  • [Meta] Message Class: The message class MAPI property for email files. By default, this field is checked on the Customize Fields page in the Advanced Settings window for ingestions.
  • [Meta] PDF Properties: Extracted properties specific to PDF files. Most files will have multiple properties. Each value in this field has the name of the property followed by the value for that property. By default, this field is checked on the Customize Fields page in the Advanced Settings window for ingestions.
  • [Meta] Transport Message Headers: The message header for email files. By default, this field is unchecked on the Customize Fields page in the Advanced Settings window for ingestions.

Ingestions: Add error message information for corrupt documents

When the application encounters an ingestions error because of a corrupt document, information about that error appears in the [RT] Ingestion Detail field.

Load File Templates: Add new fields to the Variable builder for Load file templates

The following two new expressions are available as options for load file template field values: Attach Count and Attach Filenames. These options are available for both general and production load file templates.

  • The Attach Count expression returns the number of immediate attachments associated with a parent document. If there are no immediate attachments, no value is returned in the field.
  • The Attach Filenames expression lists the file names for immediate attachments associated with a parent document. The file name values are from the [Meta] File Name field. If there are no immediate attachments, no value is returned in the field.

Portal Management>User Administration: Download report with case details

When you click the Download report button to download a report of users on the Portal Management>User Administration>Users page, a new option named Users with case detail is now available in the Download dialog box, as shown in the following figure.

Download dialog box

After you click OK in the Download dialog box, a processing window appears, as shown in the following figure. Leave this window open until the report generation is complete.

Download processing window

Portal Management>Organizations: Set default file repositories

System administrators can now set default file repositories for an organization on the organization’s Properties page, as shown in the following figure.

Organization's Properties page

Note: The lists do not populate by default. The options in the lists include the file repositories that appear on the File Repositories page for an organization.

The options in this list include:

  • Image: Image or Index repositories
  • Index file: Image or Index repositories
  • File transfer: Image or Index repositories
  • Archive: Archive repositories
  • External: External repositories

The following three new columns now appear on the File Repositories page for an organization, as shown in the following figure.

File Repositories page
  • Default repository for:
    • If a file repository is the default repository, the values for indexes or images appear in this column.
    • Note: If a file repository is not linked to an organization, the default repository value does not appear on the Properties page for the organization.

  • Archive: If the file repository is the default file repository, a dot appears in the Archive column.
  • External: If the file repository is an external file repository, a dot appears in the External column.

Portal Management>Organizations: Set default servers

System administrators can now set default servers for an organization on the Properties page, as shown in the following figure.

Note: The lists do not populate by default. The options in these lists include the servers that appear on the Servers page for an organization.

Servers page
  • Database server: Database servers that you have permission to access.
  • Analysis server: Analysis servers that you have permission to access.

A new Default column appears on the Servers page for an organization, as shown in the following figure.

If a server is a default server, a dot appears in the Default column.

Note: If no servers are linked to the organization, this information does not appear on the Properties page for an organization.

Servers page showing new Default column

Portal Management>Processing>Supervisors: Logs page for RPF supervisors

A new Logs page is available in the navigation pane on the supervisor Properties page, as shown in the following figure.

To access this page, from the Portal Home page, go to Portal Management>Processing>Supervisors and select a supervisor in the list. The Logs page displays log information about the supervisor, which can help you identify error messages that may not otherwise appear in the interface.

You can also download a log for a supervisor. The log includes error and info messages.

To download a log to a .csv format, on the Logs page for a Supervisor, click the Download logs button.

Logs page

Connect API Explorer>Import API: Transfer files from S3 in createImportJob mutation

The createImportJob mutation now contains parameters to transfer files from S3.

  • Name: fileTransferLocation
  • Valid values: AmazonS3 or Windows
  • Required: No
  • Default: Windows

Note: The default is Windows. When selecting Windows, the files copy from the file repository designated for Images under the import/<case name> folder. When selecting AmazonS3, this mutation returns information needed to access the S3 bucket.

These Options parameters will allow you to request transfer of the following S3 return values within the fileTransferLocationInformation parameter:

  • accessKey
  • secretAccessKey
  • token
  • repositoryType
  • regionEndpoint
  • bucketName
  • rootPrefix
  • expiration

Note: When the fileTransferLocation is AmazonS3, the mutation copies the files from the Amazon S3 bucket and folder created for the job rather than from the import folder on the agent.

The following is an example of how to use these parameters.

Sample mutation:

mutation {
  createImportJob (
    caseId:26,
    options:
    {
      level:“Imports”,
      docsPerLevel:1000,
      updateGroupCoding:True,
      fileTransferLocation:AmazonS3
    }
  )
  {
    rdxJobId
    fileTransferLocationInfo
    {
        accessKey
        secretAccessKey
        token
        repositoryType
        regionEndpoint
        bucketName
        rootPrefix
        expiration
    }    
  }
}

Sample returned data:

{
  “data”: {
    “createImportJob”: {
      “rdxJobId”: 1040,
      “temporaryFileTransferLocationConnectInfo”: {
        “accessKey”: “AEK_AccessKeyId”,
        “secretAccessKey”: “AEK_SecretAccessKey”,
        “token”: “AEK_SessionToken”,
        “repositoryType”: “AmazonS3”,
        “regionEndpoint”: “AEK_Region”,
        “bucketName”: “AEK_Bucket”,
        “rootPrefix”: “AEK_JobPrefix”,
        “expiration”: “2019-11-27T07:04:29.601994Z”
      }
    }
  }
}

Connect API Explorer>Import API: Assign sequential document IDs in an import job

The createImportJob mutation now contains parameters for assigning sequential document ID values for documents in the job.

  • Name: documentIdFormat
  • Valid values: Sequential or Existing
  • Required: No
  • Default: Existing

Note: Use a value of Sequential to have the application reassign document ID values for the documents within this import. Assignment of document IDs uses the provided prefix beginning with the next available document ID number matching that prefix and incrementing by 1 for each document.

  • Name: documentIdPrefix
  • Type: String
  • Required: No

Note: This is static text that appears at the beginning of each document ID only when using Sequential for the documentIdFormat option. If you do not provide this option, the application will use the document ID prefix setting from the Ingestions default settings.

When the documentIdFormat option is Sequential, the job generates a new document ID for all documents within the job. The generated ID will consist of a prefix from documentIdPrefix and a number value padded to nine digits beginning with the next available number in the case with the same prefix.

Document source and attachment relationships generate using the references in parentId based on the provided document ID values. If using sequential renumbering, document source and attachment relationships will generate only based on the parentId references within this job. Documents will not attach to prior existing documents.

If the document contains only one page, the page label will match the document ID. For documents containing multiple pages, the page labels update as DocID-00001, DocID-00002, DocID-00003, consecutively to the last page.

For files that are in pages, the page file name will match the existing page label such as DocID-00001.tif, DocID-00002.tif, and so on. For files not in pages, the file is named after the document ID, like DocID.xls.

The following is an example of how to use these parameters.

Sample mutation:

mutation {
  createImportJob (
    caseId:26,
    options:
    {
      level:“Imports”,
      docsPerLevel:1000,
      updateGroupCoding:True,
      documentIdFormat:Sequential,
      documentIdPrefix:“Doc_”
    }
  )
  {
    rdxJobId
  }
}

Connect API Explorer: Query assignment data for report generation

The Connect API Explorer allows you to gather assignment data to generate reports that can show process workflows, phases, and user assignments.

The following lists the available fields for an assignment object query:

  • id
  • status: Object that extracts the following values:
    • Unassigned
    • Active
    • Suspended
    • Cleared
    • Deleted
    • Revoked
  • workflow: Object to extract the following field data:
    • description
    • id
    • name
    • phases
  • phases: Object to extract the following field data:
    • documentsPerAssignment
    • id
    • locked
    • name
    • parentId
    • parentPhaseName
    • quickCode
    • validationCriteriaName
  • lot: Object to extract the following field data:
    • id
    • name
  • name
  • user
  • assignedDate
  • clearedDate
  • createdDate
  • clear
  • total

Sample query:

query {
  cases (id: 5) {
    reviewSetup {
      workflows (id: 7) {
        phases (id: 10) {
          id
        }
      }
      assignments (id: 8) {
        id
      }
    }
  }
}

Connect API Explorer: Clone cases using caseClone mutation

The caseClone mutation allows you to quickly create new cases without having to use the Nuix Discover UI. The following describes the mutation acceptance criteria.

Required fields:

  • caseName
  • organizationId: Used to identify an organization’s default template used for cloning.

Optional fields:

  • sourceCaseId: Data based on a user’s organization. If the sourceCaseId is missing and there is a selected default template, the mutation uses the organization’s default template case. If the sourceCaseId is missing and there is no default template selected, the application returns the following message: A sourceCaseId must be included in this mutation when an organization does not have a default template case.
  • Description
  • scheduleMetricsJob = true (default): If true, schedule is set to Monthly on day 31 at 11:00 PM.

The following lists the non-configurable fields that inherit the organization’s default or have a hard-coded default:

  • active = true (default)
  • clearData = true (default)
  • databaseServerId
  • imageRepositoryId
  • indexRepositoryId
  • fileTransferRepositoryId
  • analysisServerId
  • archiveRepositoryId
  • externalRepositoryId

The following lists examples of some of the available result fields for use in the caseClone mutation:

  • processingStatus: Object that extracts the following case processing status:
    • Failure
    • Pending
    • Queued
    • Succeeded
    • SucceededWithWarnings
  • processingType: Object that extracts the following case processing type:
    • Clone
    • Connect
    • Create
    • Decommission
    • DeleteDecommissionCase
    • Edit
    • Recommission

Note: This mutation does not support the process of setting the case metrics schedule to (daily (time)), (Weekly (week day, time)), (monthly(day, time)).

Sample mutation query with defaults:

mutation clone {
  caseClone (input: {
    organizationId: 1,
    sourceCaseId: 2,
    caseName: “My new clone”
  }) {
    case {
      id
    }
  }
}

Sample mutation query with options:

mutation clone {
  caseClone (input: {
    organizationId: 1,
    sourceCaseId: 2,
    caseName: “My new clone”
    description: “This is my cloned case”,
    scheduleMetricsJob: true
  }) {
    case {
      id
    }
  }
}

Connect API Explorer: userUpdate mutation for administration tasks

The Connect API Explorer userUpdate mutation allows administrators to perform updates to multiple user accounts simultaneously. When building this mutation, you must include the userId field to identify the user accounts.

Optional fields:

  • firstName
  • lastName
  • email
  • companyId
  • identityProviderId
  • portalCategory
  • disabled
  • requirePasswordChange: Previously named forceReset
  • licenses
  • password
  • addToActiveDirectory
  • forceResetChallengeQuestions

Important: When passing a field value that is blank, the mutation will remove the field. For example, the mutation will remove the disabled field if you enter disabled: “”. When entering new values for either the firstName or lastName, the mutation updates the entire name.

Sample mutation:

mutation {
  userUpdate(input: [
    {userId: 200, firstName: “Fred”, lastName: “Doo”},
    {userId: 1, firstName: “Velma”},
    {userId: 1, lastName: “Doo”}
  ]) {
    users {
      id
      fullName
    }
  }
}

Connect API Explorer: New userAdd mutation

The new mutation userAdd allows the addition of new user accounts using the API. The following lists the accepted input data for this mutation:

  • firstName: Required data
  • lastName: Required data
  • username: Required data
  • password: Required data
  • email
  • licenses: Default is Yes
  • forceReset: Default is Yes
  • portalCategory: Required and follows the same rules as in the user interface (UI) of what the user passing in the mutation can assign.
  • organizationID: Follows the same rules as in the UI of what the user passing in the mutation can assign.
  • companyID
  • addtoActiveDirectory: Required and default is Yes.

The following is an example of how to use this mutation.

Sample Mutation:

mutation newuser {
  userAdd(input: {firstName: “new”, lastName: “user”, userName: “newuser”, password: “Qwerty12345”, email: “newuser@user.com”, forceReset: false, portalCategory: PortalAdministrator, licenses: 1, addToActiveDirectory: true}) {
    users {
      id
      organizations {
        name
        id
        accountNumber
      }
      identityProvider
      userName
      fullName
      companyName
    }
  }
}

Connect API Explorer: New userDelete mutation

The new mutation userDelete allows the deletion of user accounts using the API so that you can integrate your user management application with Nuix Discover. The following lists the accepted input data for this mutation:

  • If all users exist, executing the userDelete mutation with single or multiple userid values will delete all specified users.
  • If some users do not exist, executing the userDelete mutation with single or multiple userid values will delete the specified valid users. In return, the user id values as null.
  • If no users exist, executing the userDelete mutation with single or multiple userid values will return the user id values as null.

Fields:

  • userID: An integer that identifies the user in the portal.

The following is an example of how to use this mutation.

Sample Mutation:

mutation userDelete {
  userDelete(input: {userId: [231]}) {
    users {
      id
    }
  }
}

Connect API Explorer: Cross organization cloning using caseClone mutation

The mutation caseClone now allows the cloning of organizations without using the UI Extensions. The following is the acceptance criteria when using this process:

Required Fields:

  • caseName: Required data.
  • organizationId: Required data.
  • sourceCaseId: Optional data with defaults based on user’s organization.
    • When not included, the mutation will use the organization’s default case template.
    • When not included and there is no default case template, the mutation uses the portal default case template.
    • When not included and there is no default case template or a portal case template, the application returns the following message: A sourceCaseId must be included in this mutation when the portal and organization do not have a default template case.
  • description: Optional data.
  • scheduleMetricsJob = true (default): Optional data. If true, schedule is set to Monthly on day 31 at 11:00 PM.
    • The mutation does not support setting the case metrics schedule as (daily (time)), (Weekly (week day, time)), (monthly(day, time)).

The following are non-configurable fields and inherit the organization defaults or have a hard-coded default:

  • active = true (default)
  • clearData = true (default)
  • databaseServerId
  • imageRepositoryId
  • indexRepositoryId
  • fileTransferRepositoryId
  • analysisServerId
  • archiveRepositoryId
  • externalRepositoryId

The following is an example of how to use these defaults and options.

Sample mutation with defaults:

mutation clone {
  caseClone(input: {
    sourceCaseId: 1,
    caseName: “My new cloned case”
  }) {
    case {
      id
    }
  }
}

Sample mutation with options:

mutation clone {
  caseClone(input: {
    organizationId: 11,
    sourceCaseId: 12,
    caseName: “My new cloned case”,
    description: “This case is described”,
    scheduleMetricsJob: true
  }) {
    case {
      id
    }
  }
}

Sample mutation query with defaults:

mutation clone {
  caseClone (input: {
    organizationId: 1,
    sourceCaseId: 2,
    caseName: “My new clone”
  }) {
    case {
      id
    }
  }
}

Sample mutation query with options:

mutation clone {
  caseClone (input: {
    organizationId: 1,
    sourceCaseId: 2,
    caseName: “My new clone”
    description: “This is my cloned case”,
    scheduleMetricsJob: true
  }) {
    case {
      id
    }
  }
}

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 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.

As of the Nuix Discover 10.2 quarterly release to on-premises clients, the following Microsoft products are supported:

  • Microsoft Windows Server Operating System
    • Microsoft Windows Server 2012 R2
    • Microsoft Windows Server 2016
    • Microsoft Windows Server 2019
  • Microsoft SQL Server
    • Microsoft SQL Server 2016 Standard SP2
    • Microsoft SQL Server 2017 Standard w/CU5 (14.0.3023.8 or higher)

End-of-support notice

Microsoft Windows Server 2012 R2 will no longer be supported as of the 10.6 quarterly on-premises release.

User audit migration service is integrated into Nuix Discover

As of the 10.2 quarterly release, the standalone user audit migration service is removed. The service is now integrated into the Nuix Discover code.

Note: Additional information will be provided in the 10.2 system documentation.

As part of the integration, the following portal setting was removed: User audit migration service URL.

The User audit log service URL setting is still available to system administrators. When this setting has a value, the Portal Management>Cases and Servers>Coding History page is visible.

Nuix Discover 10.1 Quarterly Release Notes

Audio: Resubmit multiple previously transcribed documents

You can now resubmit audio documents to generate new transcriptions using the Transcribe audio option on the Tools menu. Doing so can be useful if you selected the wrong language model when you transcribed audio documents, or if errors occurred during the transcription job.

Before you resubmit previously transcribed documents, note the following:

  • After you resubmit the audio documents, the application removes any corrections that were made in the previous transcriptions.
  • You cannot resubmit documents that have annotations. Delete the annotations first.

Use the following procedure to resubmit previously transcribed audio documents.

  1. On the Tools menu, select Transcribe audio.
  2. In the Transcribe audio dialog box, shown in the following figure, do the following:
  3. Transcribe audio page
    • Under Language model, select the language. You can select one of the following audio language models:
      • Arabic (Modern Standard)
      • Brazilian Portuguese
      • Chinese (Mandarin)
      • English (UK)
      • English (US)
      • French
      • German
      • Japanese
      • Korean
      • Spanish
    • Under Optional inclusions, select the check boxes for the documents that you would like to resubmit.
  4. Click OK.

Tools > OCR processing: Languages listed in alphabetical order in the OCR processing dialog box

In the OCR processing dialog box, available languages for OCR processing now appear in alphabetical order.

Manage Documents > Exports: Updates to the MDB Classic export type

The following two updates have been made to the MDB Classic export type in the Export window:

  • Administrators can export a production or a set of rendition documents. In previous releases, administrators could export only binders or base documents with this export type.
    • When creating an export from the Manage Documents page, administrators can select the MDB Classic export type.
    • When selecting rendition documents from search results for export using the Tools > Export menu option, administrators can select the MDB Classic export type from the Export type list.
  • Administrators can choose to populate the pages table of an MDB export file, even if no files are selected for export.
    • If an administrator selects the option to export an MDB load file in the Export window but does not select any files to export, the pages table of the exported MDB file will be empty by default. However, administrators can now populate the pages table of the MDB file anyway. On the Load files page, in the Settings window (available when you click the Settings button, or gear), select the Populate the pages table of the MDB even if no files are selected for export check box.
    • Export (Renditions) page

Manage Documents > Exports: Enhancements and changes to the Exports feature

You now receive the same export results regardless of the way that you choose to submit the export job. You can submit export jobs on the Manage Documents > Exports page or by using the Tools > Export feature on the Documents page.

Only administrators can export documents from the Manage Documents > Exports page. In addition, the user interface used in the Tools > Export feature is now also used on the Manage Documents > Exports page and includes the same options for administrators.

Major enhancements and changes

  • When exporting on the Manage Documents > Exports page, you can now export more than one load file at a time.
  • For base documents, you can select options to convert image files to PDF or TIFF.
  • For any load file field references to files, for page or document load files, the application now populates load file fields based on the files exported along with load files. This process is different than how the Manage Documents > Exports feature worked previously for page load files. For example, in the legacy code, if you exported an MDB load file on its own, but no other files, the pages table would reflect main_pages for the documents in the export. In the updated code, if you export an MDB with no files, no updates occur to the pages table.

Other enhancements and changes

  • Exported files will exist in a folder named according to the Export name and ID under the export folder. However, as shown in the following figure, you can select a repository from the File repository list and, under Output folder path, you can also export to an existing folder instead. To select a file repository or an existing folder, on the Define export page, click the Settings (gear) button to open the Settings window, as shown in the following figure.
  • Export - Define export page
  • When exporting using the Manage Documents > Exports feature, on the Source page, you can choose to export a Binder of documents or a Production. Depending on whether you select Binder or Production on the Source page, the options on subsequent pages will differ. This process is similar to how the options change in the Exports > Tools window depending on whether you select base or rendition documents.
  • Note: This page is not enabled when using the Tools > Export feature on the Documents page because that export is based on documents selected in a search result.

    Export - Source page
  • A new Image settings page replaces the PDF settings page.
    • For image files, users can select the option to convert images to non-searchable PDFs or to convert PDFs to TIFF. These options were previously available for production exports from the Manage Documents > Exports page and are now options for base document exports as well. If the document set already consists of PDFs, you can select the following option from the Image format list: Embed OCR text in existing PDFs. Selecting this option will not create searchable PDFs from non-PDF files.
    • Note: The Embed OCR text in existing PDFs option is available only if the Enable PDF annotations option is set for the case.

      Export - Image settings page
  • The MDB Classic export type is now available to administrators on the Define export page, as shown in the following figure.
  • Export - Define export page
    • The MDB Classic export type makes file selection and MDB page table updates more consistent with expected results. This process is similar to using IEM in the past.
    • On the File types page, instead of selecting the options to export endorsable images, native, and content (.txt) files, you can now choose to export Imaged pages or Content files, as shown in the following figure. If you select Imaged pages, the application exports all of the files that you can see in the Image viewer in the View pane. If you select Content files, the application exports all of the files that you can see in the Native viewer in the View pane.
    • Export - Select file types to export, as needed page
    • Just like for the Custom export type, on the Annotations page in the Export window, users can choose to endorse footers and annotations.
    • The options for omitting other files when a file is annotated are slightly different than the omit file options for Custom export types. For the MDB Classic export type, the default options are as follows:
      • Omit other page files if document images are annotated: When this option is selected, only the annotated files are exported. The application will exclude any other page files from the export.
      • Omit content files if document is annotated: When this option is selected, the application excludes all content files from the export.
      • Export - Annotations page
    • For the MDB Classic export type, you can select only MDB load files for export with the files. By default, if exporting files, the pages table of the MDB will mirror the main_pages table in the application, that is, what appears in the Image viewer in the View pane.
    • A new option, shown in the following figure, is available for the MDB Classic export type. If needed, click the Settings (gear) button to select the following option:
      • Associate all exported files for a document in the pages table. If you select this option, all files exported will be represented in the pages table of the MDB, even if they did not exist in the main_pages table.
      • Export page - MDB selection

Export Feature Summary

  • The Export feature on the Manage Documents page is available only to administrators and is always available to administrators.
    • The export set is based on a selected Binder or Production.
    • No group security is enabled for the items listed for selection. All Binders, Productions, Fields, and Annotations are listed as options.
  • The Export feature, which is an option available on the Tools menu on the Documents page, is available only if the user’s group is set to Allow on the Security > Features page for the Processing – Exports feature. The following additional information applies:
    • The export set is based on selected documents in search results.
    • Group security is enabled for the items listed for selection. Users will see fields or annotations that are allowed only for the group they are logged in as.
    • Non-administrators have access to only one export type, which is Native files only, no load file included.

The following list provides an overview of the use cases, security, available file type options, and handling of base documents and renditions for the different export types (Custom, Native files only, no load file included, and MDB Classic), as well as an overview of the updates to the MDB pages table for the different export types.

  • Use cases for the different export types:
    • Custom: Select this option if you want all available file options.
    • Native files only, no load file included: Select this option if you only want to export native files for a set of documents and nothing else.
    • MDB Classic: Select this option if you are loading the export to another Nuix Discover case and want the file organization or views to be the same in the target case.
  • Security for the different export types:
    • Custom: Administrators only.
    • Native files only, no load file included: Available to administrators and to non-administrators who have access to the export feature.
    • MDB Classic: Administrators only.
  • Available file type options for the different export types:
    • Custom:
      • Endorsable image files: Any files in the Image viewer that are .tif, .tiff, .jpeg, .jpg, .bmp, .png, or .pdf (if PDF annotations are enabled in the case).
      • Native files: Highest-ranking non-txt file or file with an extension matching the field value (if specified).
      • Content files (.txt): Existing .txt file on fileshare or extracted text (for base documents).
    • Native files only, no load file included:
      • No selection available.
      • The application will export only one native file per document.
      • The native is the highest-ranking non-txt file or file with an extension matching the field value (if specified in case options).
    • MDB Classic:
      • Imaged pages: Any files in the Image viewer.
      • Content files: Any files in the Native viewer.
  • Options for base documents for the different export types:
    • Custom:
      • Image format: Select to embed OCR text in existing PDFs, convert images to PDF, or convert PDFs to TIFF.
      • Footers
      • Annotations
      • Load file: One MDB or any number of non-MDB load files.
    • Native files only, no load file included:
      • Exported file structure: As currently foldered in the case or Flattened.
    • MDB Classic:
      • Image format: Select to embed OCR text in existing PDFs.
      • Footers
      • Annotations
      • Load file: One MDB.
  • Options for rendition documents for the different export types:
    • Custom:
      • Image format: Select to embed text in existing PDFs, convert images to PDF, or convert PDFs to TIFF.
      • Load file: One MDB or any number of non-MDB load files.
    • Native files only, no load file included:
      • Exported file structure: As foldered in the case or Flattened.
    • MDB Classic:
      • Image format: Select to embed OCR text in existing PDFs.
      • Load file: One MDB.
  • MDB pages table updates for the different export types:
    • Custom:
      • At least one file per document will be associated with a document in the pages table as long as it was selected for export.
      • If endorsable images are exported, those will be associated with the document in the pages table.
      • If only a native file is exported for a document, it will be associated with the document in the pages table.
      • If only a content file is exported, the .txt file will be associated with the document in the pages table.
      • If you select the option to Update the pages table to mirror files in the image viewer, and if you select both endorsable images and natives for export, and both of those file types exist in the Image viewer for a document, then those files will all be associated with the document in the pages table.
      • If you do not select any files for export, the pages table will be empty.
    • Native files only, no load file included: Not applicable.
    • MDB Classic:
      • The pages table will mirror files available in the Image viewer if you select Imaged pages to be exported.
      • If you do not select Imaged pages to be exported, no files will be referenced in the pages table.
      • If you select Content files to be exported as well as the option to Associate all exported files for a document in the pages table, then the content files exported will be referenced in the pages table.

Additional basic information about how exports work

  • The application copies the exported files to the case default file transfer file repository and a unique subfolder under the export folder. Administrators can change the file repository and select an existing subfolder to copy the files to.
    • The application names the subfolder under the export folder based on the export name and the export ID. The application names the load files according to the export name only, and not the export ID.
  • Exported file structure:
    • When exporting files with an MDB load file, files are exported in the same file structure as they exist in the case.
    • When exporting files with a non-MDB load file, files are separated into images, native, and text folders. However, if exporting a production from the Manage Documents page, the application respects the export path details in the production settings. Note that any system load file templates reference the default folder names of image, native, and text files.

Manage Documents > Ingestions: NIST list updated - September 2019

Ingestions now uses an updated version of this list, released in September 2019. For more information, go to https://www.nist.gov/itl/ssd/software-quality-group/national-software-reference-library-nsrl.

Manage Documents > Ingestions: Show level settings in Add ingestion dialog box

In the Add ingestion dialog box, a read-only display of the default level settings for the case now appears under the Family deduplication setting.

For example, select the default settings for levels, as shown in the following figure.

Default settings - Levels page

These levels appear in the Add ingestion dialog box under the Levels heading, as shown in the following figure.

Add ingestion page

Portal Management > Processing > Jobs: Size of Elasticsearch index captured during Gather case metrics job

If a case uses an Elasticsearch index, the Gather case metrics job now captures the size of the Elasticsearch index. The Elasticsearch index is used to capture the coding audit history.

Portal Management > Processing > Jobs: Gather case metrics job captures total file size of base documents for non-document entity items

When you run a Gather case metrics job, in addition to capturing the file size of image, native, and content files associated with base documents, the application now also captures the total file size of the image, native, and content files associated with non-document entity items. This information appears in the Base documents (GB) column on the Portal Management > Reports > Hosted Details page.

Portal Management > Reports: Change the time zone

You can now change the time zone for the data that appears on the Portal Management > Reports > Usage and Hosted Details pages from local time to Coordinated Universal Time (UTC). Using UTC time allows the reports to display data consistently with reports that are generated through the API when querying for specific dates or date ranges. By default, the data appears in local time.

Use the following procedure to change the time zone from local time to UTC.

  1. On the Portal Management > Reports > Usage or Hosted Details page, on the toolbar, click the Time zone button.
  2. In the Time zone dialog box, shown in the following figure, select UTC time.
  3. Time zone dialog box
  4. Click OK.
  5. The data displayed is then based on UTC time.

Portal Management > Reports: Subtotal column added to Hosted Details report

The Portal Management > Reports > Hosted Details page now includes a Subtotal (GB) column.

Note: The label for the Total size (GB) changed to Total (GB).

In the Subtotal (GB) column, you can view a subtotal of the active data, which includes the data in the following columns:

  • Base documents (GB)
  • Production renditions (GB)
  • Databases (GB)
  • Content index (GB)
  • Predict (GB)
  • Orphan (GB)

Portal Management > Reports: Elasticsearch index size available in the Hosted Details report

If a case uses an Elasticsearch index, you can view the size of the Elasticsearch index for a case on the Reports > Hosted Details page. The name of the new column is Elasticsearch index (GB). The Elasticsearch index is used to capture the coding audit history.

Portal Management > Settings > Log Options: Download a telemetry log file

The Portal Management > Settings > Log Options page includes a new button on the toolbar named Download log that you can use to download a telemetry log file. The application downloads the telemetry log data to a .log text file.

To keep the file size manageable, you can configure the number of records to maintain in the JSON string in the Telemetry archive configuration setting on the Portal Management > Settings > Log Options page. For example, as shown in the following figure, NRecentRecordsToReturn is set to 10000.

Log Options page Telemetry archive configuration data

Connect API Explorer: Access and download API documentation

There are two new buttons available on the Connect API Explorer page, as shown in the following figure.

API documentation buttons

The Open docs button accesses additional API documentation that contains more in-depth guidance on creating and handling queries and mutations. When you click the Open docs button, the Connect API Documentation tab appears containing the API documentation, as shown in the following figure. On the left are active links that access individual topics. Click these links to scroll the page up or down to the selected topic.

Connect API Documentation sample page

Note: The top-right corner of the Connect API Documentation tab shows your specific URL location of the documentation and the current version of the document.

To download the documentation, click Download docs. Doing so downloads the documentation as a Hypertext Markup Language (HTML) page for viewing in any browser window.

Connect API Explorer: API token enhancements

Newly created API authorization tokens no longer require separate API keys and never expire. On the User Administration > API Access page, the API key label now shows the following message: The API key is not required for new authorization tokens.

The API authorization changes are backward compatible to accept existing authorization tokens, which will expire after three years.

To get a new key for an existing user, on the User Administration > API Access page, clear the Authorize this user to use the Connect API check box. Then select this option again to reactivate their authorization.

Connect API Explorer: New case statistic in the API {cases{statistics}} query

The Nuix Discover Connect API contains a new sizeOfElasticSearchIndex field that returns the total size of the Elasticsearch index for cases. The Elasticsearch index stores the audit history records for coding changes that are viewable within the Coding History pane.

The following example uses the new sizeOfElasticSearchIndex field in the cases {statistics} object.

{
  cases {
    name
    statistics {
      sizeOfElasticSearchIndex
    }
  }
}

The sizeOfElasticSearchIndex field is also part of the aggregateTotalHostedSize statistic that returns the sum of sizeofBaseDocumentsHostedDetails, sizeofRenditionsHostedDetails, aggregateDatabases, sizeOfElasticsearchIndex, dtIndexSize, sizeOfNonDocumentData, and sizeOfOrphanFiles.

Connect API Explorer: GraphQL and GraphQL Parser version upgrade

Connect API Explorer now contains the latest upgraded version of GraphQL (v2.4.0) and GraphQL Parser (v4.1.2). These upgrades require a few minor changes to your existing API queries and codes that are declaring Date variables.

In any existing API queries, the Date variable needs to change from Date to DateTime. The following figure is an example of an existing query declaring a Date variable before the upgrade.

Connect API Explorer Date variable example

This next figure shows the needed change for the upgraded version of GraphQL.

Connect API Explorer DateTime variable example

Support for Microsoft Windows Server 2019

As of this release, Nuix Discover supports Microsoft Windows Server 2019.

Changes to the installation process

Recent enhancements to the installation process introduced the following changes.

Web installer requires IIS to be enabled in advance

For new server installations, the web installer now requires Internet Information Services (IIS) to be enabled on the server in advance. This installation was formerly handled by the installer.

The command that needs to be run in advance is Install-WindowsFeature Web-Server. For additional information, see https://docs.microsoft.com/en-us/powershell/module/servermanager/install-windowsfeature?view=winserver2012r2-ps.

Note: This requirement also exists for the coordinator server.

Two new web server prerequisites

The following two new web server prerequisites are required. These prerequisites are installed automatically by the web installer.

  • Application Request Routing 3.0
  • URL Rewrite Module 2.1

Installers no longer include the Microsoft .NET Framework 4.8

The following installers no longer include the Microsoft .NET Framework 4.8 prerequisite.

Note: If the Microsoft Framework .NET 4.8+ is not installed before running these installers, the installation does not complete successfully. Before running any of the following installers, you must install the Microsoft Framework .NET 4.8+, which you can download from https://dotnet.microsoft.com/download/dotnet-framework/net48.

  • Web
  • SQL Component
  • RPF Coordinator
  • RPF Supervisor
  • Hit Highlight
  • Content Search
  • Portal API

Upcoming changes to Transport Layer Security version for Google Chrome

In Chrome 81, which will be released in March 2020, Google will block connections to sites using Transport Layer Security (TLS) 1.0 and 1.1. The recommendation from Google is to enable TLS 1.2. For additional information, go to the following URL: https://blog.chromium.org/2019/10/chrome-ui-for-deprecating-legacy-tls.html

Nuix Discover 10.0 Quarterly Release Notes

Nuix Ringtail is now Nuix Discover

In August of 2019, we officially changed the name of our eDiscovery application from Nuix Ringtail to Nuix Discover. This new name better describes the unique and powerful capabilities of our award-winning software and better aligns it with the rest of the Nuix product family, most notably Nuix Workstation and Nuix Investigate. Nuix Discover is a central part of the Nuix Total Data Intelligence platform and vision, which promises to improve collaboration, innovation, and knowledge management for organizations around the globe.

Nuix Discover logo

As a result of renaming Ringtail to Nuix Discover, the following changes were made in the user interface.

  • After you log in, the navigation bar at the top of all pages displays the Nuix Discover logo and name.
  • Navigation Bar Nuix Discover logo
  • The What’s new in Ringtail section on the Portal Home page is now named What’s new.
  • Portal Home page What's new
  • The What’s new in Ringtail section on the Case Home page is now named What’s new and displays the Nuix Discover logo.
  • Case Home page What's new
  • On the user name menu, under User settings, the Reset to Ringtail default menu option is now named Reset to case default.
  • User settings Reset to case default
  • The Ringtail Connect API Explorer is now named Connect API Explorer.
  • Portal Management Connect API Exporler option

Audio pane: Select a language model to use for transcription

You can now specify the language model to use for transcription. For example, if you know that the audio in a file uses British English instead of American English, you can select English (UK) as the source language before you transcribe the audio file.

To specify the language model for an individual file, select a file, and then click the Transcribe audio button in the Audio pane. In the Transcribe audio dialog box, select an option from the Language model list, and then click OK.

Transcribe audio dialog box

To specify the language model for multiple files, select the files. On the Tools menu, select Transcribe audio. In the Transcribe audio dialog box, select an option from the Language model list, and then click OK.

Transcribe audio Language model selection

You can select one of the following audio language models:

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

Audio pane: Resubmit transcribed audio file

If you accidentally selected the wrong language model when you transcribed an audio file, you can click the Transcribe audio button in the Audio pane to resubmit the transcription using a different language model, as shown in the following figure.

Note: This functionality is not yet available for multiple files using the Tools > Transcribe audio option.

Transcribe audio dialog box Successful transcription message

Note: You cannot re-transcribe a file that has annotations. Delete the annotations first.

Track the history for documents viewed and downloaded

In the Document view history dialog box, you can see how many times on a given day that a user viewed or downloaded a document in the View pane or downloaded a document in the Code pane.

To open the Document view history dialog box, in the View pane, select the Document view history option from the View pane menu. Alternatively, if you pinned this option to the View pane toolbar, click the Document view history button.

View pane Document view history selection

In the Document view history dialog box, each document viewing event appears on a new row. If a user downloaded a document, a dot appears in the Downloaded column.

The downloaded report also includes this information.

Document view history Downloaded column

Coding History: Case administrators can see all records regardless of group membership and security

Case administrators can see all history records, including records for deleted objects, in the template views in the Coding History pane, regardless of their group membership and the group security settings for objects such as binders, fields, or productions.

Analysis > Mines: Grant group leaders administrative rights to mines

Administrators can now grant administrative rights to mines to group leaders. Previously, only administrators could manage mines.

To grant group leaders administrative access to mines, on the Security > Administration page, in the Leaders column, set the Analysis – Mines function to Allow, and then click Save.

Security Administration page

Once group leaders have been granted access to manage mines, they can perform the following tasks:

  • Add, delete, rebuild, edit properties, and manage security for mines.
  • Access the Security > Objects page for mines to set the permissions for groups.

Case Setup > Fields > Items: Prompt when renaming or deleting pick list items that are coded to documents

On the Case Setup > Fields > Items page, if you try to delete a pick list item that is coded to a document, the Delete selected items dialog box appears with a warning message. You are prompted to confirm the action before you can proceed.

Delete selected items dialog box

If you try to rename a pick list item, if documents are coded to the item, a warning message appears in the Modify field value dialog box. After you click OK, inline editing is enabled.

Modify field value dialog box

If you try to rename a pick list item, if no documents are coded to the item, inline editing is enabled.

Case Setup > System Fields: New system field for Audio Language Model

A new system field named Audio Language Model is available on the Case Setup > System Fields page.

Note: The application disables this field for groups by default, and you cannot grant groups write access to this field.

The application populates this field after a user submits an audio transcription from the Audio pane or the Tools > Transcribe audio menu. The field value is the name of the language selected in the Language Model list for the audio transcription.

Audio Language Model Items page

Manage Documents > Ingestions: Support up to 10 levels

Administrators can now select up to ten levels on the Levels page in the Default settings window for Ingestions.

For each level, you can select one of the following options:

  • Constant: Enter a static value into the box.
  • Select a field: A list appears that allows you to select a field. You can select any one-to-one field that is selected on the Customize Fields page in the Advanced settings window.
  • None
  • Existing levels: Select a level that already exists for the case.

Manage Documents > Ingestions: NIST list updated - June 2019

In the Default Settings window for Ingestions, users can choose to exclude files that appear in the Reference Data Set (RDS) provided by the National Software Reference Library (NSRL), which is maintained by the National Institute of Standards and Technology (NIST). This is commonly referred to as the “NIST list.”” Ingestions now uses the most recent version of this list, released in June 2019. You can view the list at the following link: https://www.nist.gov/itl/ssd/software-quality-group/nsrl-download/current-rds-hash-sets.

Manage Documents > Ingestions: Add advanced setting for email files

The Email Files page is now available in the Advanced Settings window of the Ingestions feature. On this page, users can select the type of file that is available in the viewer for imported email files.

To select the correct file type, choose an option in the Files to include for email data list. The default type for new and existing cases is MHT. If you select this option, emails are rendered in the same way as before this new setting was introduced. You can also select MSG/EML with attachments. This option includes embedded attachments as part of the email document. Processes such as indexing, imaging, and export include any embedded attachments when acting on the email document.

You can view this setting for an existing imaging job on the Properties page. The Email files value appears at the bottom of the page.

Note: We expect to add an option for MSG/EML without attachments in the future. We also expect to add an option to use the MHT rendering for searching and review while preserving an MSG/EML copy for export and production.

Manage Documents > Ingestions: Settings added to the Properties page

The following information has been added to the Properties page for Ingestions.

  • Source encoding: The source encoding value selected in the Advanced settings window for ingestions.
  • Password bank: If the administrator did not select a password bank for ingestions in the Advanced settings window, the value displayed in this row is No. If the administrator selected a password bank, the value is Yes.
  • Chat settings: The following information is available in this section:
    • Idle time: Threads are broken into separate documents if the difference in sent times between two messages is equal to or greater than this number.
    • Minimum messages: Threads containing fewer messages than this number are not broken out into separate documents.
    • Maximum messages: Threads containing more messages than this number are broken out into separate documents.

Manage Documents > Ingestions: Chat: For documents in split threads, display the message counts for the thread in parentheses

In previous versions, when using Ingestions on chat thread documents, the count of messages at the top of the HTML for chat data was misleading for documents that were part of split threads.

In this version, the count of messages for each participant appears in parentheses after the total count of messages in the thread.

For example, if there are 17 messages from participant A in the thread, and 5 messages from participant A in a document that is part of the thread, the MSG column for participant A would contain a value of 17 (5). If a document is not from a split thread, the count in parentheses does not appear.

Manage Documents > Ingestions: Improved handling of missing files in the ingest_temp folder during file transfer

In previous versions, the application could not complete the transfer of files during the ingestions process if any files were missing from the ingest_temp folder. This would often occur when files were quarantined by virus scanning software. In those instances, the application could not complete the ingestions job without manual intervention. With this release, if files cannot be copied because they do not exist in the ingest_temp location, the application does the following:

  • Creates a slipsheet for any missing file with the text “File not available to copy.” Copies the slipsheet to the proper location in the images folder and references the slipsheet in the main_pages table.
  • Codes the document with a value of “File Copy Failed” in the [Meta] Processing Exceptions field.
  • Codes the document with a value of “File not available in temporary folder” in the [RT] Ingestions Exception Detail field.
  • Updates the [Meta] File Extension - Loaded field with a value of “pdf.”
  • Codes the [Meta] File Extension - Original field with the extension of the original file.

Manage Documents > Load File Templates: Field name suffixes removed in the Variable Builder

In the Variable Builder for load file templates, the names of the field types (DATE, MEMO, NUMB, PICK, TEXT, YES/NO) no longer appear in the Name column.

Variable Builder Quick Picks tab

Portal Management > Cases and Servers: Only system administrators can disconnect a case

On the Portal Management > Cases and Servers page, the Disconnect case button on the toolbar appears only for system administrators. Previously, portal administrators also had access to this feature.

Cases and Servers page Discount case button

Portal Management > Reports: Enhancements to the Portal Summary Report

The following enhancements and changes are available in the Portal Summary Report on the Portal Management > Reports > Summary page:

  • Recent user activity list:
    • The list now shows activity for the last 30 days. The list used to show activity for the last 7 days.
    • For failed logins, the login date and time appear in red font.
    • The Sessions column has been renamed to Cases and shows the number of cases that the user logged in to in the last 30 days. If the user did not log in to any cases, the value is zero (0).
    • Tip: Hover over a row in this column to display a tooltip that shows the case name and the last accessed date for all cases in the organization that the user accessed in the last 30 days. See the following figure for an example.

      Recent user activity Sessions column

Portal Management > Reports > Summary: New Settings feature to include or exclude data for deleted cases

A new Settings button is available on the toolbar on the Portal Management > Reports > Summary page.

Click the Settings button to open the Settings dialog box. By default, data for deleted cases is excluded from the reports. To display data for deleted cases, select the Include option.

Settings dialog box to Include or Exclude

If the Exclude option is selected, the data for deleted cases does not appear in the following sections on the Reports > Summary page:

  • The Cases bar chart (Total column)
  • The Recent user activity table
  • The Hosted data table and chart
  • Note: Below the chart in the Hosted data section, a message also indicates if the data for deleted cases is included or excluded.

    Reports Summary page

Portal Management > Settings: Enable telemetry logging from the portal database

You can write telemetry logging data to the portal database. This logging data includes all usage metrics and application errors for a portal.

The following settings are available on the Portal Management > Settings > Log Options page, as shown in the following figure.

Settings Log Options page
  • Enable telemetry logging: Select this check box to enable logging for the portal.
  • Log detail level: Select an option to adjust the level of detail captured in the log: Error, Info, Debug, or Trace.
  • Log file location: If you provide a location, the telemetry data is stored in physical files on the web servers.
  • Max log files: Provide a value to indicate the number of archive (.archive.log) files to keep on the web servers.
  • Store logs in database: Select this check box to store log data in the portal database. If selected, an RPF job pushes the data to S3 and cleans up the database table per the configuration setting indicated in the Telemetry archive configuration setting.
  • Note: If this option is selected, and the Telemetry archive configuration setting is not configured, then no log entries will be deleted from the database table.

  • Telemetry archive configuration: The information in this setting controls the frequency of when the RPF job runs to upload log entries from the database table to S3 and clean up the portal database. This setting is a JSON string with the following fields:
  • {
      “Checkpoint”: “0”,
      “Key”: “AWS key”,
      “Secret”: “AWS secret key”,
      “Region”: “AWS region”,
      “Bucket”: “AWS S3 bucket name”,
      “CleanupMaxDays”: 30,
      “ScheduleId”: null,
      “IntervalInMinutes”: 60
    }
    • Checkpoint: Default to 0. This holds the value of the last successful upload to S3.
    • Key: AWS key
    • Secret: AWS secret key
    • Region: AWS region
    • Bucket: AWS S3 bucket
    • CleanupMaxDays: Cleans up database records that are older than this value.
    • ScheduleId: Defaults to null. This will be set by the RPF job and should not be modified manually.
    • IntervalInMinutes: Defaults to 60. This sets the frequency, in minutes, for the RPF scheduled job.
  • The Log Options page also includes the following additional changes:
    • The following two syslog options were removed:
      • Ringtail syslog server name
      • Ringtail syslog server port
    • Some options were renamed as follows:
      • Log enabled > Enable telemetry logging
      • Log level > Log level detail
      • Log location > Log file location
      • Max Archive Files > Max log files
      • Database log enabled > Store logs in database

Import API

There are three new mutations in the Connect API for importing documents into a case: createImportJob, addDocumentsForImportJob, and submitImportJob.

Create an import job

You can create an import job in a case using the createImportJob mutation. This mutation returns the rdxJobID, which is used in the next mutation to add documents to the import job. This mutation also allows you to configure some job-level settings.

Sample mutation:

mutation {
  createImportJob (
    caseId:26,
    options:{
      name:“My Import Job”,
      description:“Import job description”,
      level:“Imports/Custodian A/0001”,
      docsPerLevel:1000
      updateGroupCoding:true
    }
  )
  {
    rdxJobId
  }
}

Sample response:

{
  “data”: {
    “createImportJob”: {
      “rdxJobId”: 319
    }
  }
}

Configurable options:

  • name: String is the name of the import job. If you do not provide a value for this option, the job name is “Import from API.”
  • description: String is the description of the import job. If you do not provide a value for this option, the job description is “Import from API.”
  • level: String determines the root level to put documents in. If you do not provide a value for this option, the level is “API/{ImportID}/0001.” Level values assigned to documents in the addDocumentsForImportJob mutation override this setting.
  • docsPerLevel: Int determines the maximum number of documents per level. If you do not provide a value for this option, the value is 1000.
  • updateGroupCoding: Boolean updates the group coding fields (All Custodians, for example) for new documents in this import and any existing or future family duplicate documents. If you do not provide a value for this option, the value is “false.”

Add documents to an import job

You can use the addDocumentsForImportJob mutation to add documents to an import job that was created using the createImportJob mutation. Each addDocumentsForImportJob mutation allows you to add up to 5000 documents. To add additional documents to the job, run multiple mutations with different documents.

Note: When defining the path value for pages and contentfiles, the path is relative to the “import” folder in the Image file repository defined for the case.

For example, if the path is defined as follows:

path:“Imports\\Media0001\\Images\\0001\\DOC-00000001.tif”

then the file should be located at:

{Image file repository}\import\{case name}\Imports\Media0001\Images\0001\DOC-00000001.tif.

Sample mutation:

mutation {
  addDocumentsForImportJob (
    caseId:26,
    rdxJobId:319,
    documents:[
      {
        documentId:“DOC-00000001”,
        hash:“qwer1234asdf5678zxcv1234qwer5678”,
        familyhash:“poui1234asdf5678zxcv1234qwer5678”,
        level:“Imports/Custom/0001”,
        parentId:“”,
        sourceattachmentaction:Delete,
        pageaction:InsertUpdate
        mainfields:[
          {
            name:DocumentDate,value:“2019-01-03”,action:Update
          },
          {
            name:DocumentType,value:“Microsoft Outlook Message”,action:Update
          },
          {
            name:DocumentTitle,value:“Re: Your message”,action:Update
          },
          {
            name:DocumentDescription,value:“”,action:Delete
          },
          {
            name:EstimatedDate,value:“False”,action:Update       
          }
        ],
        fields:[
          {
            name:“Custodian”,onetomany:false,type:PickList,action:InsertUpdate,values:“Custodian A”
          },
          {
            name:“[Meta] Processing Exceptions”,type:PickList,action:InsertUpdate,values:[“Corrupted”,“Empty File”]
          },
          {
            name:“[Meta] File Name”,onetomany:false,type:Text,action:InsertUpdate,values:“Re: Your message.msg”
          },
          {
            name:“[Meta] File Path”,onetomany:false,type:Memo,action:InsertUpdate,values:“C:\\Downloads\\Email”
          },
          {
            name:“[Meta] File Size”,onetomany:false,type:Number,action:Delete,values:“1592”
          },
          {
            name:“[Meta] Date Sent”,onetomany:false,type:DateTime,action:InsertUpdate,values:“2019-01-03”
          },
        ],
        correspondence:[
          {
            type:“From”,people:“acustodian@example.com”,orgs:“example.com”,action:InsertUpdate
          },
          {
            type:“To”,people:“bsmith@example.com”,action:Append
          },
          {
            type:“CC”,people:[“kjohnson@example.com”,“ewilliams@example.com”],action:InsertUpdate
          }
        ],
        pages:[
          {
            pagenumber:1,pagelabel:“DOC-00000001”,path:“Imports\\Media0001\\Images\\0001\\DOC-00000001.tif”
          },
          {
            pagenumber:2,pagelabel:“DOC-00000002”,path:“Imports\\Media0001\\Images\\0001\\DOC-00000002.tif”
          }
        ]
        ,
        contentfiles:[
          {
            path:“Imports\\Media0001\\Natives\\0001\\DOC-00000001.mht”
          }
        ]
      },
      {
        documentId:“DOC-00000003”,
        hash:“6425hyjkasdf5678zxcv1234qwer5678”,
        familyhash:“poui1234asdf5678zxcv1234qwer5678”,
        level:“Imports/Custom/0001”,
        parentId:“DOC-00000001”,
        sourceattachmentaction:InsertUpdate,
        pageaction:InsertUpdate
        mainfields:[
          {
            name:DocumentDate,value:“2019-01-02”,action:Update
          },
          {
            name:DocumentType,value:“Microsoft Word”,action:Update
          },
          {
            name:DocumentTitle,value:“WordDoc.docx”,action:Update
          },
          {
            name:DocumentDescription,value:“Sample description”,action:Update
          },
          {
            name:EstimatedDate,value:“False”,action:Update       
          }
        ],
        fields:[
          {
            name:“Custodian”,onetomany:false,type:PickList,action:InsertUpdate,values:“Custodian A”
          },
          {
            name:“[Meta] File Name”,onetomany:false,type:Text,action:InsertUpdate,values:“WordDoc.docx”
          },
          {
            name:“[Meta] File Path”,onetomany:false,type:Memo,action:InsertUpdate,values:“C:\\Downloads\\Email\\Re: Your message.msg”
          },
          {
            name:“[Meta] File Size”,onetomany:false,type:Number,action:InsertUpdate,values:“74326”
          },
          {
            name:“[Meta] Date Modified”,onetomany:false,type:DateTime,action:InsertUpdate,values:“2019-01-02”
          },
        ],
        pages:[
          {
            pagenumber:1,pagelabel:“DOC-00000003”,path:“Imports\\Media0001\\Natives\\0001\\DOC-00000003.docx”
          }
        ]
      }
    ]
  )
  {
    documentCount
  }
}

Sample response:

{
  “data”: {
    “addDocumentsForImportJob”: {
      “documentCount”: 2
    }
  }
}

Configurable options:

  • documentId: String! imports the Document ID of the document.
  • hash: String imports the individual MD5 hash value of the document. This value is added to the [RT] MD5 Hash field in the case.
  • familyhash: String imports the family MD5 hash value of the document. This value is added to the [RT] Family MD5 Hash field in the case.
  • level: String, when set, overrides any level data set in the job options. Levels are not updated for existing documents.
  • parentId: String is the parent document ID for the document that establishes a source/attachment relationship. The source/attachment relationship is either updated or deleted depending on the value set for sourceattachmentaction.
  • sourceattachmentaction: SAAction determines which of the following actions to take for the parentId field:
    • Delete removes coding from the document for the field.
    • InsertUpdate inserts or updates the value(s) of the field.
  • pageaction: Action determines which of the following actions to take on the pages:
    • Append appends the value(s) to the field. This applies only to one-to-many fields
    • Delete removes coding from the document for the field.
    • InsertUpdate inserts or updates the value(s) of the field
  • mainfields: [DocumentFieldParams] imports the following data into core document fields in the case.
    • name: DocumentField! is the name of the document field. The names correspond to the core document fields in the case: DocumentDate, DocumentDescription, DocumentTitle, DocumentType, EstimatedDate.
    • value: String determines which of the following values is populated in the document field.
      • DocumentDate is the Document Date of the document. Format is YYYY-MM-DD.
      • DocumentDescription is the Document Description of the document.
      • DocumentTitle is the Document Title of the document.
      • DocumentType is the Document Type of the document.
      • EstimatedDate is the Estimated Date of the document. A Boolean value.
    • action: CoreAction! determines which of the following actions to take on the incoming field data:
      • Update inserts or updates the value(s) of the field.
      • Delete removes coding from the document for the field.
      • Ignore ignores the value.
  • fields: [FieldParams] imports the following data into fields in the case:
    • name: String! Is the name of the field. If the field exists, the existing field will be used. If not, the name is created with the field type indicated.
    • onetomany: Boolean defines whether the field is one to many.
    • type: FieldType! is the field type. The possible values are as follows:
      • Boolean allows you to set the value as Yes or No.
      • DateTime allows you to set the value in YYYY-MM-DD format.
      • Memo
      • Number
      • PickList
      • Text
    • action: Action! determines which of the following actions to take on the incoming data:
      • Append appends the value(s) to the field (only for one-to-many field types).
      • Delete removes coding from the document for the field.
      • InsertUpdate inserts or updates the value(s) of the field.
    • values: [String]! imports the value(s) for the field.
  • correspondence: [CorrespondenceType] imports the following people and organization values for the document:
    • type: String! determines the correspondence type. Possible values are To, From, CC, or BCC.
    • people: [String] contains a list of people values.
    • orgs: [String] contains a list of organization values.
    • action: Action! determines which of the following actions to take on the incoming field data:
      • Append appends the value(s) to the field (only for one to many field types).
      • Delete removes coding from the document for the field.
      • InsertUpdate inserts or updates the value(s) of the field.
  • pages: [PagesParams] imports the following values for the pages associated with the document:
    • pagenumber: Int! is the page number.
    • pagelabel: String is the page label of the page
    • path: String! is the location of the physical file to upload.
  • contentfiles: [ContentFileParams] imports the list of content files for the document.
    • path: String! imports the location of the physical file to upload.

Submit an import job

After adding documents to a job using the addDocumentsForImportJob mutation, you can run the import job using the submitImportJob mutation.

Sample mutation:

mutation {
  submitImportJob (
    caseId:26,
    rdxJobId:325
  )
  {
    rpfJobId
  }
}

Sample response:

{
  “data”: {
    “submitImportJob”: {
      “rpfJobId”: 11805
    }
  }
}

Connect API Explorer: Only an API user can copy their own token and key

If a user has been authorized to use the API, only that user can copy their API token and key.

A new API Access page, shown in the following figure, displays the API token and API key with links to copy the token and key. Previously, the API Access page was available in the Portal Management > User Administration section.

Note: The API Access page is visible only if a user has been authorized to use the API.

To access the API Access page, on the Portal Home page, from the user name menu, select Account Settings. On the Account Settings page, in the navigation pane, select API Access.

Account Settings API Access page

New download site for installers

Nuix has changed the download site for Nuix Discover (Ringtail) installers and documentation from the FTI e-delivery site (https://edelivery.ue.goringtail.com) to the Nuix Customer Portal (https://download.nuix.com/).

If you do not already have login credentials for the Nuix Customer Portal, please visit the Nuix Support Portal (https://nuix.service-now.com/support) and submit a ticket to request login credentials for the Nuix Customer Portal (https://download.nuix.com/).

NIST list updated - June 2019

In the Default Settings window for Ingestions, users can choose to exclude files that appear in the Reference Data Set (RDS) provided by the National Software Reference Library (NSRL), which is maintained by the National Institute of Standards and Technology (NIST). This is commonly referred to as the “NIST list.” Ingestions now uses the most recent version of this list, released in June 2019. You can view the list at the following link: https://www.nist.gov/itl/ssd/software-quality-group/nsrl-download/current-rds-hash-sets.