SaaS / Hosted Monthly Release Notes - July 2022 (10.11.003 - 10.11.004)

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

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

Link transcript dialog box showing Memo Editor functionality

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

Conditional Coding pane showing Link transcript functionality

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

Memo Editor pane showing Transcript link functionality

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

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

Hash duplicate documents have a similarity of 100.

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

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

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

Related pane showing Master duplicates

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

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

Related pane showing Individual duplicates

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

Connect API Explorer: importJobAddDocuments mutation updated for creating links

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


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

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


Results of the import job creation with needed job ID:

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


Sample import mutation using the created job ID:

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


Results of importing the link data:

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


Sample mutation for running the import job:

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

SaaS / Hosted Monthly Release Notes - June 2022 (10.11.001 - 10.11.002)

Audio: Updated language models for the audio transcription feature

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

On September 15, 2022, IBM will deprecate the previous-generation language models and support only the next-generation language models.

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

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

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

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

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

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

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

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

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

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

Portal Management > Settings: New portal options for Linux/Docker Ingestions to reduce preprocessing time

As part of the ongoing effort to enhance the processing performance of Ingestions in SaaS environments, the following two new portal options are available on the Portal Management > Settings > Portal Options page.

Note: These options apply only if you use the Linux/Docker Ingestions feature. If you configure the following two new portal options, verify that the Enable Linux/Docker Ingestions check box is selected.

  • Enable Linux/Docker Ingestions Autoscale EC2 Instances: If you select this check box, the Coordinator automatically provisions a Linux Ingestions worker when you submit an Ingestions job.
  • Ingestion AWS Lambda Function Name: Enter the name of the AWS Lambda function used to provision Linux Ingestions workers.
  • Portal Options page showing the Enable Linux and Ingestions AWS check box options

Connect API Explorer: Upgrade to case comparison operators

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

String operators:

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

Number and Date operators:

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

Sample query:

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

Sample query results:

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

Connect API Explorer: Query saved searches

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

Parameters and filters available are:

  • id
  • name
  • createdDate
  • createdByUser

Sample query:

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

Sample query results:

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

Connect API Explorer: caseCreate mutation updates

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

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

Required fields:

  • caseName
  • organizationId

Optional fields:

  • Description
  • scheduleMetricsJob

Sample mutation:

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

SaaS / Hosted Monthly Release Notes - May 2022 (10.10.005 - 10.11.000)

Enhancements to processing performance in SaaS

Have you noticed a recent performance enhancement in your latest Ingestions or Search Term Families (STF) job?

For the past few months, the Nuix Discover team has been working on an initiative to enhance RPF processing performance, including:

  • Optimized RPF tasking
  • RPF data cleanup, including automatically archiving old RPF data during upgrade
  • SQL index improvements
  • Improved pre-processing times for Ingestions jobs
  • STF optimization

Additional performance enhancements are scheduled to be rolled out in an upcoming monthly release.

SaaS / Hosted Monthly Release Notes - April 2022 (10.10.003 - 10.10.004)

Conditional Coding: Customize the layout and zoom

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

To customize the layout in the Conditional Coding pane:

  1. On the Conditional Coding pane menu, select Options.
  2. In the Options dialog box, under Layout, select one of the following options:
  3. Options Dialog box under Layout
    • Auto: With this option, which is selected by default, the application automatically adjusts the layout (top and bottom or left and right) of the field name and field values depending on the width of the pane.
    • Top and bottom: If you select this option, the application always displays the field values underneath the field name.
    • Example of the Top and Bottom option
    • Left and right: If you select this option, the application always displays the field name on the left side of the pane and the field values on the right side of the pane.
    • Example of the Left and Right option
  4. Click OK.

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

To change the zoom level:

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

Conditional Coding: New Issues - Custom field for conditional templates

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

Example of the new Issues – Custom field

Conditional Coding: New Source/Attachments field for conditional templates

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

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

Example of the new Source-Attachments field

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

Example of the Source-Attachments field location

Browse pane: New Identities section

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

Example of the new Identities section

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

Case Setup > Conditional Templates > Coding fields: Enhancements to the Binders - Custom field

As of this release, to modify the values in the Binders - Custom field on the Case Setup > Conditional Templates > Coding fields page, you can click the blue Binders - Custom link.

Example of the new Binders-Custom field

Previously, to modify the values in the Binders - Custom field, you had to delete the field and then add a new Binders - Custom field.

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

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

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

  1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, in the Add field list, select Issues - Custom.
  2. Note: You can add only one Issues - Custom field to a coding template.

  3. Click the Add button.
  4. Coding fields page showing the Add button
  5. In the Issues - Custom dialog box, select one or more issues, optionally select the Include sub-issues check box before selecting a parent issue to include all of its child issues with it in the field, and then click Save.
  6. Issues-Custom dialog box showing selection of multiple issues

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

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

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

To delete the Issues - Custom field from the template:

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

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

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

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

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

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

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

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

  4. The Source/Attachments field is then available in the Conditional Coding pane for the template, and reviewers can use the field to learn about the Source/Attachments documents that are related to the active document.
  5. Example of the Source-Attachments field on the Conditional Coding page

To delete a Source/Attachments field from the template:

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

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

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

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

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

Case cloning: Restricted user assignment setting now retained when cloning a case

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

Example of the Restricted user assignment setting on the Properties page

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

Example of retaining the Case Details settings after cloning cases

SaaS / Hosted Monthly Release Notes - March 2022 (10.10.001 - 10.10.002)

Improved Nuix Discover login experience

In previous versions, SaaS users who inadvertently navigated to the Login Service URL received an error message.

Nuix SaaS Administrators have now configured the login experience such that users who go to the Login Service URL are redirected automatically to the appropriate portal URL.

View pane: Keyword summary

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

To use the Keyword summary feature:

  1. In the View pane, in Formatted content or Unformatted content view, on the toolbar, click Keyword summary.
  2. View pane showing Formatted or Unformatted content
  3. The layout changes and the application displays collapsed sections for only those parts of the document that contain hits. The layout also includes line numbers.
  4. View pane showing collapsed sections of content

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

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

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

Conditional Coding: New Binders - Custom field for conditional templates

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

Conditional Coding pane showing the Binders - Shared and Custom sections

Translate: Italian available as a target translation language

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

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

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

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

  1. On the Case Setup > Conditional Templates > [Name of template] > Coding fields page, in the Add field list, select Binders - Custom.
  2. Click the Add field button.
  3. Coding fields page showing the Add field button
  4. In the Binders - Custom window, select one or more binders and then click Save.
  5. The Binders - Custom window for saving selected fields
  6. The Binders - Custom field is then available in the Conditional Coding pane for the template, and reviewers can code documents to the binders in this field.
  7. Conditional Coding pane showing the Binders - Shared and Custom sections

Additional notes about the first release of this feature:

  • You can add only one Binders - Custom field to a coding template.
  • To change the binders included in the Binders - Custom field, you must delete the field and add a new one. In a future release, this field will be editable.

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

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

A Clone button is now available on the toolbar.

Case Setup - Issues page showing the Clone button

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

Case Setup - Issues page showing the Clone issue icon

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

To clone a top-level issue:

  1. On the Case Setup > Issues page, select a top-level issue.
  2. Case Setup - Issues page showing the selection of the top level issue
  3. On the toolbar, click Clone.
  4. In the Clone issue window, confirm or modify the issue name.
  5. The cloned issue appears in the list.

To clone a child issue:

  1. On the Case Setup > Issues page, click the link for a top-level issue.
  2. On the Child Issues page, select a child issue or issues.
  3. Note: When you select a child issue, the application automatically selects any subissues of the child issue.

  4. On the toolbar, click Clone.
  5. In the Clone issue window, confirm or modify the issue name.
  6. Click OK.
  7. The cloned issue appears on the Case Setup > Issues > Child Issues page.

Case Setup > Issues: Move issues

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

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

To move a top-level issue:

  1. On the Case Setup > Issues page, select a top-level issue.
  2. Case Setup - Issues page showing selection of the top level issue
  3. On the toolbar, click Move.
  4. In the Move issues window, select a top-level issue or child issue destination for the issue you want to move.
  5. Move issues window showing the selected issues to be moved and their chosen destination
  6. Click OK.
  7. The issue moves to the destination you selected.

To move a child issue:

  1. On the Case Setup > Issues page, click the link for a top-level issue.
  2. On the Child Issues page, select a child issue.
  3. Note: When you select a child issue, the application automatically selects any subissues.

  4. On the toolbar, click Move.
  5. Child Issues page showing a selection of issues and the Move button
  6. In the Move issues window, select a destination:
    • A new top-level issue.
    • An existing top-level or child issue.
    • Move issues window showing the selected issues to be moved and their chosen destination
  7. Click OK.
  8. The issue moves to the destination you selected.

Case Setup > Hierarchies: Preview a hierarchy

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

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

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

Add Hierarchy - Preview page showing a preview of the hierarchy

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

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

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

SaaS / Hosted Monthly Release Notes - February 2022 (10.9.005 - 10.10.000)

Load search file tool: Search for [RT] Family MD5 HASH

You can now search for the [RT] Family MD5 HASH field, as shown in the following figure, when using the Load search file tool, which is available on the Tools menu on the Documents page.

New Search page from the Load search file tool

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.

Note: This change was implemented in Nuix Discover version 10.9.003.

Processing group

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.

Terms page showing the search terms

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.

Terms page showing the selection of a search term

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

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.

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

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

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

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

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

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

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

People Identity page showing a banner message

As of version 10.10.000, the following changes have been made, as shown in the following figure:

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

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

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.

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

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

  • Indexing: Options
  • Indexing: Noise Words
  • Indexing: Alpha Standard
  • Indexing: Alpha Extended
  • Indexing: Thesaurus
  • Indexing: Stemming Rules
  • Indexing: File Type Rules
  • Cases page showing the different indexing options in navigation

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

On the Portal Management > 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 an indexing and enrichment message banner

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

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

To view the errors for versions up until version 10.9.005, select the See legacy errors check box, as shown in the following figure.

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

Errors page indicating the See legacy errors selection

SaaS / Hosted Monthly Release Notes - December 2021 (10.9.003 - 10.9.004)

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.

Current search criteria

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 criteria for Renditions

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 criteria Threaded view

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 criteria for Renditions in all documents

Load search file tool: Not Found page now displays [RT] MD5 HASH and Page Label information

If you use the Load search file tool to search for documents or entities that contain an [RT] MD5 HASH field, if the application does not find matching documents or entities, the application now indicates that on the Not Found page in the Load Search file window (for the [RT] MD HASH field and the Page Label), as shown in the following figure.

Load search file page

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

Import page

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.

SaaS / Hosted Monthly Release Notes - November 2021 (10.9.001 - 10.9.002)

Note: The permissions set by your administrator may determine access to certain features.

Updates to the Load search file tool: Support for the MD5 hash and page label fields

When using the Load search file tool on the Tools menu on the Documents page, you can now search for documents that include a list of hash values by selecting the [RT] MD5 HASH field in the Field list.

You can now also select the Page Label field from this list.

Load search file page showing selection of Page Label

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

Load search file page

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.
    • Chat conversation example

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.

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

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 non-billable cases

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 billable cases

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

The importJobAddDocuments mutation has a new filePageNumber field, which replaces the filename field, for identifying the page number where annotations are applied. 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 would contain the numbers from 1 to 5. If the filePageNumber value is set to 2, the annotation will be applied on the second page of the PDF.

Sample mutation using the old 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 new 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 new notes object that will specify what notes will populate in the document.

Required fields:

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

Optional fields:

  • category: A category identifying the note. If the entered category does not already exist, the new value will create a new category. If no value is provided, the category will be Uncategorized.
  • userName: The name of the user who created the note. If this name matches a known user, the userId: is automatically populated with the note. Otherwise, the user performing the import is assigned to the note.
  • dateStamp: The date the note was last modified. If left blank, the date will populate 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 will appear 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
  }
}

SaaS / Hosted Monthly Release Notes - October 2021 (10.8.005 - 10.9.000)

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

Portal Management > Cases and Servers > Cases > Case Options: New case option to disable 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.

SaaS / Hosted Monthly Release Notes - September 2021 (10.8.003 - 10.8.004)

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

Note: System administrator tasks are performed by Nuix SaaS administrators.

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.

Use the following procedure 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 > 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: 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”
    }
  ) {
    rdxJobId
  }
}

Notification about browsers

On August 17, 2021, Microsoft ended support for Microsoft Internet Explorer (IE) 11. As of this date, Nuix Discover no longer supports 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 as soon as possible: Google Chrome or (Chromium-based) Microsoft Edge, both of which support the Office Online viewer feature.

When you log in to Nuix Discover, if you are using a browser other than Google Chrome or Microsoft Edge, Nuix Discover takes you to a page with a notification about supported browsers.